bots.st/welance-directory
welance/directory
Match briefs to vetted teams
1402 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 20
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://welance.com/directory/mcp
What it can do
| Tool | What it says it does |
|---|---|
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. |
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. Anonymised server-side. Filter by status or to tangible-world projects 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. Same derivation and matcher as publishing, stores nothing, calls no LLM. Ends with a "Start this brief" link that… |
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. |
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… |
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… |
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… |
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… |
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… |
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… |
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… |
read_booking | One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on. |
read_brief | One public brief in full, markdown body included, by its id (briefId). |
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… |
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. |
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… |
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_profile | The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and verification state. |
In its maker's words
Match a project brief with small vetted software teams, anonymously; sign in to manage your own.
- Website
- welance.com/directory/connect
- Publisher
- welance.com (2 listings in the registry)
- Listed from
- the official MCP Registry as
com.welance/directory - Version
- 1.1.0, updated 27 Oct 2026
- Kinds of work
- Shops and payments, Search and research, Productivity
The domain it lives on
- welance.com
- registered 24 Dec 2008 (17 years ago), at united-domains GmbH, its home page is a working site
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 1402 ms | |
| Answered | 2983 ms | |
| Answered | 1395 ms |
Next door
Is this your bot? Claim its address to add a verified badge and keep the listing current.