welance/directory
Match a project brief with small vetted software teams, anonymously; sign in to manage your own.
What it does
welance/directory is an MCP server, a connector that lets an AI assistant use it as a tool. It is hosted: an assistant connects to it over the internet, nothing to install.
No capability identified yet from its description.
Facts come from the Official MCP Registry, as declared by the publisher. Capabilities are matched automatically (low confidence). None of this is a test of the tool.
At a glance
How to connect
As declared in the Official MCP Registry · hosted endpoint tested by Electra Index 2h ago (live check)Hosted endpoint
https://welance.com/directory/mcpstreamable-http
In Claude Code: claude mcp add --transport http welance-directory https://welance.com/directory/mcp
MCP settings (Claude Desktop, Cursor and other MCP clients)
{
"mcpServers": {
"welance-directory": {
"url": "https://welance.com/directory/mcp"
}
}
}Live check
Electra Index connected to the hosted endpoint 2h agoONLINE welance/directory answered an MCP connection on 27 Oct 2026 and introduced itself as welance-directory 1.1.0 (MCP protocol 2025-06-18).
20 tools offered to AI assistants
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 tlist_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.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 onlymatch_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,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); eacread_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.read_brief· One public brief in full, markdown body included, by its id (briefId).read_booking· One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.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.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
Show 8 more
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 hpropose_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 limitedpropose_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 (jpropose_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. Notpropose_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/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 happenspropose_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 thepropose_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
What "online" means: the server answered an MCP connection at the time of the check. It is not a guarantee of security, quality or continuous uptime. How we test: we open an MCP session and ask for the tool list, as an AI assistant would. We never run a tool and never send a key. Checked every few days. Method
Is this your server? Monitoring Pro: a check every 30 minutes and an email within the hour when it stops answering. Launch offer: $39.99 once, for life.
Facts & evidence
Each fact shows where it was seen and when.| Fact | Value | Evidence | Source | Last confirmed |
|---|---|---|---|---|
| Hosted endpoint | https://welance.com/directory/mcp | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Local install (package) | no | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Remote access (hosted) | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Website | https://welance.com/directory/connect | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Registry status | active | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| Version | 1.1.0 | DECLARED | SRC-001 Official MCP Registry | 2h ago |
| MCP server | yes | DECLARED | SRC-001 Official MCP Registry | 2h ago |
Change history
- NEW27 Oct 2026first seen in the index
Is this page accurate?
Flag it and our robot re-checks the official source. Reports never change a score.Is welance/directory still online?
Free alerts · no accountDo you run welance/directory? Know when it stops answering
For publishers · optionalIts hosted endpoint can be monitored. Monitoring Pro connects every 30 minutes like an AI assistant, emails you within the hour when it stops answering, keeps a 90-day availability history and adds your answer rate to your badge.
Monitoring never changes a score or a rank.
Questions about welance/directory
How do I connect welance/directory?
Use the hosted endpoint https://welance.com/directory/mcp in your assistant's MCP settings. The exact settings are in "How to connect" above, as declared in the Official MCP Registry.
What tools does welance/directory offer?
When Electra Index connected on 27 Oct 2026, it listed 20 tools: directory_capabilities, list_open_briefs, preview_teams, match_brief, brief_rules, read_profile, read_my_teams, read_my_pitches and more. The full list is in "Live check" above.
Is welance/directory online?
Yes. Its hosted endpoint answered an MCP connection from Electra Index 2h ago.