INDIVIDUAL MCP TOOL

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.

welance.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://welance.com/directory/mcp

No auth detected

Connect to this endpoint to inspect the live schema for propose_pitch_send and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Potential side effects detected · medium confidence · heuristic, not a guarantee.

A tool name or description contains a write-action term.
A tool name or description suggests sending messages.

Parent server

welance.com

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.

Related tools

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.
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.
preview_teams — Two anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board.
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.
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.
read_profile — The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and verification state.
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.
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.