Developer Tools

welance.com

A directory and matching service for vetted software teams that publishes open briefs, previews anonymous teams, and scores briefs against publication rules.

2 endpoints27 known toolsFirst detected October 28, 2026Last detected October 28, 2026

ENDPOINT 1

https://welance.com/directory/mcp

No auth detected

MCP server metadata

Name: welance-directory
Version: 1.1.0

Capabilities

tools

Server instructions

welance/directory, connected to one person (OAuth). Free: there are no plans and no credits. Public tools work without signing in; the read_* tools read the signed-in person's own directory (profile, teams, briefs, pitches, bookings, invoices) and the propose_* tools STORE a proposal the person reviews and confirms on welance.com/directory. Nothing is published, sent, invited, booked or paid by this connection: the only paid step is the €30 + VAT per-side meeting handshake, which the person completes on the website. Always end with the review link a tool returns. Teams stay anonymous until a mutual handshake.

Known tools 20

directory_capabilities

What the directory is, who it is for (small vetted software teams for digital projects, especially ones rooted in the physical world), how pricing works (0% of the project; €30 + VAT from each side only to meet, charged once both accept a time), and the rule that the human stays the principal.

Inferred read-only

list_open_briefs

The public briefs: open ones looking for a team, ones in vetting, and the archive of delivered projects with budget, sector and delivery team.

Inferred read-only

preview_teams

Two anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board.

Inferred read-only

match_brief

Match a draft brief (80–20000 characters) against the real, eligible anonymous teams: only teams the brief matches come back, with reasons and the defaults inferred from the brief.

Inferred read-only

brief_rules

The rule catalogue a brief is scored against before teams see it: ids, labels, weights and the acceptance threshold that decides whether a brief publishes.

Inferred read-only

read_profile

The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and verification state.

Inferred read-only

read_my_teams

The signed-in person's teams: key (teamKey), name, and the facts the system derives rather than stores (members = confirmed people; rate = blended from members' rates unless the team sets an override; languages from members unless set); each team's profile (based, remote, availability, shipped work), open and matching brief counts, and a checklist of what pitching and the public board require, each marked met or missing.

Inferred read-only

read_my_pitches

The signed-in person's pitches and bookings on both sides: applications sent by their teams (with handshake and booking state) and the anonymous pitches received on their own briefs.

Inferred read-only

read_brief

One public brief in full, markdown body included, by its id (briefId).

Inferred read-only

read_booking

One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.

Inferred read-only

read_pitchable_briefs

For each of the signed-in person's teams, the open briefs that team can still pitch on: not yet pitched, pitch slots left, and a language match.

Inferred read-only

read_invoices

The signed-in person's past invoices with their PDF and document links (pdfUrl / documentUrl).

Inferred read-only

propose_brief_draft

A proposed update to the person's local brief draft: title, markdown, and/or per-rule answers.

Potential side effects

propose_brief_publish

A proposal to publish a brief (title, markdown, optional language) to the board.

Potential side effects

propose_profile_update

Proposed field changes to one entity.

Inferred read-only

propose_team_invite

A proposal to invite a person to one of the signed-in person's teams (teamKey) by name and email, with an optional role.

Potential side effects

propose_pitch_draft

An anonymous pitch draft for one of the person's teams (teamKey) on an open brief (briefId).

Inferred read-only

propose_pitch_send

A proposal to send an anonymous pitch for one of the person's teams (teamKey) on an open brief (briefId); once confirmed, the brief owner sees it.

Potential side effects

propose_booking

As the client of a pitch on the person's own brief (appId): a proposed 30-minute call with at least 3 concrete slots (ISO 8601; weekdays, on the hour, 09–18 CET, 3–10 business days ahead) and an optional note.

Inferred read-only

propose_booking_accept

As the team on a booking (bookingId): a proposal to accept one of the client's offered slots (slotId).

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.welance-directory]
url = "https://welance.com/directory/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "welance-directory": {
      "type": "http",
      "url": "https://welance.com/directory/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: welance-directory
Remote MCP URL: https://welance.com/directory/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "welance-directory": {
      "url": "https://welance.com/directory/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "welance-directory": {
      "type": "http",
      "url": "https://welance.com/directory/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "welance-directory",
  "transport": "streamable-http",
  "url": "https://welance.com/directory/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

ENDPOINT 2

https://briefs.welance.com/mcp

No auth detected

MCP server metadata

Name: perfect-brief

Capabilities

promptsresourcestools

Server instructions

Perfect Brief: an open bar for digital product briefs, free, with your own model. Read the rules (get_rules), judge the brief with your own model using get_judge_prompt, then send your JSON verdicts to aggregate_verdicts: the bar's own code computes score, gate and decision. Fix the gate first. Never state a score you did not get from aggregate_verdicts, and say it is client-judged and advisory: only the welance/directory's own scoring can publish. Privacy: https://briefs.welance.com/privacy.html. Terms: https://briefs.welance.com/terms.html.

Known tools 7

get_rules

Read the bar before judging anything.

Inferred read-only

get_brief_template

A brief template built from the live rules, with the inputs each section needs.

Inferred read-only

get_judge_prompt

The judge prompt and verdict JSON Schema, for YOUR model to answer.

Inferred read-only

get_improvement_prompt

A working order for improving a brief with your own model, gate first.

Inferred read-only

check_brief

Deterministic checks only — semantic coverage is INCOMPLETE.

Inferred read-only

aggregate_verdicts

Turn your model's verdicts into the bar's score, gate and decision.

Inferred read-only

bar_status

Which ruleset version is live, and what this free surface can do.

Inferred read-only

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.perfect-brief]
url = "https://briefs.welance.com/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "perfect-brief": {
      "type": "http",
      "url": "https://briefs.welance.com/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: perfect-brief
Remote MCP URL: https://briefs.welance.com/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "perfect-brief": {
      "url": "https://briefs.welance.com/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "perfect-brief": {
      "type": "http",
      "url": "https://briefs.welance.com/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "perfect-brief",
  "transport": "streamable-http",
  "url": "https://briefs.welance.com/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.