mcpbeat Sign in

welance/directory MCP Server

answering

welance/directory is answering right now. Last checked 4 min ago. It exposes 20 tools.

Match a project brief with small vetted software teams, anonymously; sign in to manage your own.

Uptime history 6 days of history
6 days agonow
100.0%
Uptime 24h
91 of 91 checks
20
Tools
read from the server
204 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check welance/directory every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add directory --transport http https://welance.com/directory/mcp
Settings → Connectors → Add custom connector, then paste this address
https://welance.com/directory/mcp
~/.codex/config.toml
[mcp_servers.directory]
url = "https://welance.com/directory/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "directory": {
      "url": "https://welance.com/directory/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "directory": {
      "type": "http",
      "url": "https://welance.com/directory/mcp"
    }
  }
}

Available tools 20

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

propose
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. Confirming holds €30 from the client's side for up to 7 days; nothing is charged until both sides accept a time. A no-show's €30 is not returned; the side that showed gets a credit. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
propose_booking_accept
As the team on a booking (bookingId): a proposal to accept one of the client's offered slots (slotId). Accepting charges €30 from each side; if the client does not show, the team's €30 becomes a credit; if the team does not show, its €30 is not returned. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
propose_brief_draft
A proposed update to the person's local brief draft: title, markdown, and/or per-rule answers. Accepting it fills the brief editor; nothing is published. The whole proposal is limited to 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
propose_brief_publish
A proposal to publish a brief (title, markdown, optional language) to the board. On confirmation the server's live score gate decides whether it publishes; publishing emails a one-time link and signs no one in. The whole proposal is limited to 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
propose_pitch_draft
An anonymous pitch draft for one of the person's teams (teamKey) on an open brief (briefId). Accepting it fills the existing pitch editor; nothing is sent. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
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. Each brief accepts a limited number of pitches (10). Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
propose_profile_update
Proposed field changes to one entity. entity "person": the signed-in person's own profile (job_role, years_experience, langs, skills, hourly_rate). entity "member" + teamKey + memberKey: a confirmed colleague on one of the person's teams (job_role, years_experience, langs, hourly_rate; skills are rated only by their owner). entity "team" + teamKey: intro, based, remote, availability, langs, shipped, hourly. entity "organisation" + organisationId: website, description of an organisation the person owns or administers (descriptive only; it verifies nothing). Skills: changes[{field:"skills", value:[{name, rating 1–10}]}] adds or re-rates (an existing name takes the new rating); removeSkills lists skill names to remove. Languages: addLangs / removeLangs take two-letter codes; alternatively a langs change carries the complete new list (not both). Scalars: changes[{field, value}]; hourly_rate is EUR/h, 10–2000; team hourly overrides the rate blended from members' rates, and null restores the blend; team size is not a field (it is the confirmed member count). Team shipped: value lists entries to add, each {title, url, desc}; existing entries are kept; removeShipped lists titles or links to remove. inferred=true marks a value derived from evidence rather than stated by the person; hourly rate, availability, languages and skill ratings are rejected when inferred. Each changed field becomes a separate card the person approves. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
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. Once confirmed, the invitee receives an email; their skill ratings are theirs to set later. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory; the result includes the review link.
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_brief
One public brief in full, markdown body included, by its id (briefId).
booking
read_booking
One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.
directory
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.
invoices
read_invoices
The signed-in person's past invoices with their PDF and document links (pdfUrl / documentUrl). Without filters it covers every billing identity of the person (personal VAT plus companies they own or administer); each invoice is tagged with its identity {kind, id, label, vatMasked}. identity ("all", "personal" or "org:<organisationId>") or identities (several of "personal" / "org:<organisationId>") narrow by identity; from/to (YYYY-MM-DD, inclusive) narrow by date; limit caps the count (1–50).
match
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. Same derivation and matcher as publishing, stores nothing, calls no LLM. Ends with a "Start this brief" link that opens the guided flow prefilled.
open
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. Anonymised server-side. Filter by status or to tangible-world projects only.
pitchable
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.
pitches
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.
preview
preview_teams
Two anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board. The board is brief-first: the teams that fit a project are listed only against a draft brief. Names and members are revealed only after a mutual €30-per-side handshake.
profile
read_profile
The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and verification state.
teams
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.

Endpoints

URLTransportStateLatencyChecked
https://welance.com/directory/mcp streamable-http answering 158 ms 4 min ago

Alternatives to welance/directory

same job, measured the same way
DiscordServers
by discordservers

Search Discord server listings, and manage your own servers once you sign in.

answering
uivoid
by uivoid

Manage uivoid projects, tools, keys, hosted databases and teams from your agent.

answering
Genchi
by genchi

Spot projects predicted to miss their deadlines, from an anonymous team confidence vote in Slack.

answering
Ankr Management MCP
by w3tech

Manage an Ankr RPC account: API keys, usage, allowlists, billing, teams. Sign in with OAuth.

answering
Hilbana
by hilbana

Project tracker for teams working with AI agents: issues, cycles, docs and shared agent memory.

answering
Teamwork
by teamwork

The Teamwork.com official MCP server helps teams efficiently manage client projects with AI.

214 tools answering
Approval Studio
by approval

Approval Studio is an online proofing software for creative teams and everyone working with designs

answering
NodeLane Act
by wy2926

Use Reddit, Zhihu, X and WhatsApp through your signed-in browser with compact, on-demand MCP tools.

local only

welance/directory — questions

Answers built from our own checks of this server.

What can welance/directory do?
It exposes 20 tools, read directly from the server on our last check. Among them: brief_rules, directory_capabilities, list_open_briefs, match_brief, preview_teams, propose_booking and 14 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is welance/directory mostly used for?
Its tools cluster around propose and brief. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is welance/directory working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 204 ms. The bar chart above shows every period we have measured.
How do I connect welance/directory?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does welance/directory need an API key?
No. welance/directory completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 20 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is welance/directory?
It answers our handshake in 204 ms on average, which is faster than 69% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.