welance/directory

com.welance/directorywelance.comstreamable-httpv1.1.0Scanned 54 minutes ago

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

20 tools: 3 do something that can't be undone, 8 change things and 9 only read.

Reads private data · 2
Reads text others write · 1
Can send data out · 3
1 finding

Anlyon alternative

11 of these tools change something. Run those as governed actions.

Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.

Anlyon does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.

Import an OpenAPI spec →

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

20 tools

Can't be undone 3Sends, pays, publishes or merges: once done, it cannot be taken back.Claude Code: ask

propose_brief_publishPropose publishing a brief to the board.Can send data outNo findings
Why it is in this group
- The name "propose_brief_publish" says "publish": a word for a change that another call does not undo.
What it can reach
- outboundThe name "propose_brief_publish" says "publish": it sends or publishes something to other people.
Description, as the server wrote it
Propose publishing a brief to the board. The server gate (live score) decides; the confirm card states that a one-time link is emailed and that publishing does not sign anyone in. The whole proposal must fit 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose publishing a brief
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_pitch_sendPropose SENDING an anonymous pitch for one of my teams (an explicit confirm; the brief owner sees it).Can send data outNo findings
Why it is in this group
- The name "propose_pitch_send" says "send": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "propose_pitch_send" says "send": it sends or publishes something to other people.
Description, as the server wrote it
Propose SENDING an anonymous pitch for one of my teams (an explicit confirm; the brief owner sees it). Pitch slots per brief are limited (10). Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose sending a pitch
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_team_invitePropose inviting a person to one of my teams by name and email (they get an email).Can send data outNo findings
Why it is in this group
- The name "propose_team_invite" says "invite": a word for sending, and what is sent cannot be taken back.
What it can reach
- outboundThe name "propose_team_invite" says "invite": it sends or publishes something to other people.
Description, as the server wrote it
Propose inviting a person to one of my teams by name and email (they get an email). Skill ratings are theirs to set later. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose inviting someone to a team
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

Changes things 8Creates or changes something that can be changed back.Claude Code: ask

brief_rulesThe rule catalogue a brief is scored against before teams see it: ids, labels, weights and the acceptance threshold.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
The rule catalogue a brief is scored against before teams see it: ids, labels, weights and the acceptance threshold. Use it to help the human write a brief that publishes.
Annotations the server declares
- title: The public scoring rules
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
directory_capabilitiesWhat 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 + V…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- title: What welance/directory is
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
match_briefMatch 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.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it
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.
Annotations the server declares
- title: Shortlist teams for a draft brief
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
propose_bookingAs the CLIENT of a pitch on my brief, propose a 30-minute call with at least 3 concrete slots: weekdays, on the hour, 09–18 CET, 3–10 business days ahead (ISO 8601).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
As the CLIENT of a pitch on my brief, propose a 30-minute call with at least 3 concrete slots: weekdays, on the hour, 09–18 CET, 3–10 business days ahead (ISO 8601). Proposing holds €30 from my 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 answer carries the review link).
Annotations the server declares
- title: Propose meeting times
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_booking_acceptAs the TEAM, propose accepting one of the client's offered slots for a booking (accepting charges €30 from each side; if the client doesn't show, the team's €30 becomes a credit; i…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
As the TEAM, propose accepting one of the client's offered slots for a booking (accepting charges €30 from each side; if the client doesn't show, the team's €30 becomes a credit; if the team doesn't show, it isn't returned). Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose accepting a meeting time
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_brief_draftPropose an update to the person's LOCAL brief draft (title, markdown, or per-rule answers).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Propose an update to the person's LOCAL brief draft (title, markdown, or per-rule answers). Applied to the editor only on tap; nothing is published. The whole proposal must fit 64,000 UTF-8 bytes. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose a brief draft
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_pitch_draftPropose an anonymous pitch draft for one of my teams on an open brief.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it
Propose an anonymous pitch draft for one of my teams on an open brief. "Use draft" fills the existing pitch editor; nothing is sent. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose a pitch draft
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
propose_profile_updatePropose field changes to MY person profile (entity "person": job_role, years_experience, langs, skills, hourly_rate) or to a colleague on my team (entity "member" + teamKey + membe…1 finding
Why it is in this group
- The name "propose_profile_update" says "update": a word for a change.
Findings
- Info
  The description is 2,058 characters long, over the 2,000 this check looks for.
  Matched text
  description ends: "...person confirms it on welance.com/directory (the answer carries the review link)."
  What this check looks for
Description, as the server wrote it
Propose field changes to MY person profile (entity "person": job_role, years_experience, langs, skills, hourly_rate) or to a colleague on my team (entity "member" + teamKey + memberKey from read_team_roster: job_role, years_experience, langs, hourly_rate — a confirmed colleague only; their skills are theirs to rate) or to one of my teams (entity "team" + teamKey: intro, based, remote, availability, langs, shipped, hourly) Supported operations — use the one that matches the request: SKILLS (person): add or re-rate = changes[{field:"skills", value:[{name, rating}]}] (an existing name gets the new rating); remove = removeSkills:[names exactly as read_profile lists them]. Removing is supported: never say you cannot. LANGUAGES (person, member, team): addLangs / removeLangs with two-letter codes, or a changes langs value = the complete new list (not both). SCALARS: job_role, years_experience, hourly_rate (EUR/h, 10–2000), intro, based, remote, availability, hourly (team override; null = back to the members' blend), website, description: changes[{field, value}]. A value the person stated is supplied: propose it immediately with inferred=false. Team shipped: value = the entries to ADD, each {title, url, desc} — url may be the public link the person gave, desc one line; existing entries are kept automatically. removeShipped = titles or links of entries to REMOVE. Team hourly: only when the person explicitly asks to override the rate blended from members' rates; team size is never a field (it is the confirmed member count). or to an organisation I own or administer (entity "organisation" + organisationId: website, description — descriptive only, it verifies nothing). Each field becomes a separate card the person approves. skills value: [{name, rating 1-10}] — the rating must be the person's own choice (ask with ask_choice). Never propose hourly rate, availability, languages or skill ratings as inferred. Stores a proposal only. Nothing happens until the person confirms it on welance.com/directory (the answer carries the review link).
Annotations the server declares
- title: Propose profile changes
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false

Only reads 9Looks things up and changes nothing.Show 9 read-only tools

list_open_briefsThe public briefs: open ones looking for a team, ones in vetting, and the archive of delivered projects with budget, sector and delivery team.No findings
Why it is in this group
- The name "list_open_briefs" says "list": a word for reading.
Description, as the server wrote it
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.
Annotations the server declares
- title: Open briefs and delivered projects
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
preview_teamsTwo anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board.No findings
Why it is in this group
- The name "preview_teams" says "preview": a word for reading.
Description, as the server wrote it
Two anonymous, vetted teams as specimens (rotating daily) and the size of the supply — never the whole board. The board is brief-first: to see the teams that fit a project, send a draft brief to match_brief. Names and members are revealed only after a mutual €30-per-side handshake.
Annotations the server declares
- title: A protected preview of the team board
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_bookingRead one booking (slots, state, my side) by its id.No findings
Why it is in this group
- The name "read_booking" says "read": a word for reading.
Description, as the server wrote it
Read one booking (slots, state, my side) by its id.
Annotations the server declares
- title: One booking
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_briefRead one public brief in full (markdown body included).No findings
Why it is in this group
- The name "read_brief" says "read": a word for reading.
Description, as the server wrote it
Read one public brief in full (markdown body included).
Annotations the server declares
- title: One brief
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_invoicesList my past invoices with their Stripe pdfUrl / documentUrl links.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "read_invoices" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "list" and "document": it reads documents.
- untrusted-inputThe description's first sentence says "list" and "url": it reads web pages, which anyone can write.
Description, as the server wrote it
List my past invoices with their Stripe pdfUrl / documentUrl links. By default ALL my billing identities (personal VAT + companies I own or administer), each invoice tagged with its identity {kind, id, label, vatMasked}. Narrow with identity = "personal" or "org:<organisationId>" (ids from read_my_organisations), or identities = several of those; from/to (YYYY-MM-DD, inclusive) narrow by date, e.g. last quarter. To open the page: propose_navigate section "billing", param = "all", "personal" or "org:<organisationId>".
Annotations the server declares
- title: My invoices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_my_pitchesMy pitches and bookings on both sides: my teams' applications (with handshake and booking state) and the anonymous pitches received on my own briefs.No findings
Why it is in this group
- The name "read_my_pitches" says "read": a word for reading.
Description, as the server wrote it
My pitches and bookings on both sides: my teams' applications (with handshake and booking state) and the anonymous pitches received on my own briefs.
Annotations the server declares
- title: My briefs, pitches and bookings
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_my_teamsList my teams with key (teamKey), name, the facts the system DERIVES (members = confirmed people, rate = blended from members unless a team override, languages from members unless …No findings
Why it is in this group
- The name "read_my_teams" says "read": a word for reading.
Description, as the server wrote it
List my teams with key (teamKey), name, the facts the system DERIVES (members = confirmed people, rate = blended from members unless a team override, languages from members unless set) — never ask the person for these — their profile (based, remote, availability, shipped), open/matching brief counts, and a checklist of what pitching and the public board require, met or missing.
Annotations the server declares
- title: My teams
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_pitchable_briefsFor each of my teams, the open briefs it can still pitch on (not yet pitched, slots left, language match).No findings
Why it is in this group
- The name "read_pitchable_briefs" says "read": a word for reading.
Description, as the server wrote it
For each of my teams, the open briefs it can still pitch on (not yet pitched, slots left, language match).
Annotations the server declares
- title: Briefs my teams can pitch on
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
read_profileRead my own Directory profile: role, years, languages, rated skills, hourly rate, verification state.Reads private dataNo findings
Why it is in this group
- The name "read_profile" says "read": a word for reading.
What it can reach
- private-dataThe description's first sentence says "read" and "directory": it reads files.
Description, as the server wrote it
Read my own Directory profile: role, years, languages, rated skills, hourly rate, verification state.
Annotations the server declares
- title: My profile
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

6 paths in this server alone from private data, through text someone else wrote, to a way out. Denying 1 untrusted-input tool breaks every one.

Reads private data2: Reads files, mail, messages, databases, secrets, calendars or repositories.; read_invoices
read_profile
Reads text others write1: Brings in text someone else can write: web pages, inbound email, messages, issues and comments.; read_invoices
Can send data out3: Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.; propose_brief_publish
propose_pitch_send
propose_team_invite

deny to break every path

{
  "permissions": {
    "deny": [
      "mcp__directory__read_invoices"
    ]
  }
}

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Findings

Matches of fixed checks, with the text they matched.

1 info

Infopropose_profile_update
The description is 2,058 characters long, over the 2,000 this check looks for.
Matched text
description ends: "...person confirms it on welance.com/directory (the answer carries the review link)."
What this check looks for

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

All changes to this server

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http directory https://welance.com/directory/mcp

claude mcp add --transport http directory https://welance.com/directory/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json

{
  "permissions": {
    "allow": [
      "mcp__directory__list_open_briefs",
      "mcp__directory__preview_teams",
      "mcp__directory__read_profile",
      "mcp__directory__read_my_teams",
      "mcp__directory__read_my_pitches",
      "mcp__directory__read_brief",
      "mcp__directory__read_booking",
      "mcp__directory__read_pitchable_briefs",
      "mcp__directory__read_invoices"
    ],
    "ask": [
      "mcp__directory__directory_capabilities",
      "mcp__directory__match_brief",
      "mcp__directory__brief_rules",
      "mcp__directory__propose_brief_draft",
      "mcp__directory__propose_brief_publish",
      "mcp__directory__propose_profile_update",
      "mcp__directory__propose_team_invite",
      "mcp__directory__propose_pitch_draft",
      "mcp__directory__propose_pitch_send",
      "mcp__directory__propose_booking",
      "mcp__directory__propose_booking_accept"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as directory. Review it before you use it.

Capability tags behind 5 rules

mcp__directory__read_profile private-data
mcp__directory__read_invoices private-data, untrusted-input
mcp__directory__propose_brief_publish outbound
mcp__directory__propose_team_invite outbound
mcp__directory__propose_pitch_send outbound

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://anlyon.dev/api/v1/servers/com.welance/directory/verify?hash=407fbc5291c7945deb21ed242b3df8678d98715e9298ddb006e9f66f295ba74b" | jq -e '.changed == false'

Pinned hash 407fbc5291c7, from Oct 27, 2026, 16:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://anlyon.dev/servers/com.welance/directory/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

[![anlyon.dev](https://anlyon.dev/badge/com.welance/directory.svg)](https://anlyon.dev/servers/com.welance/directory)

Source: MCP Registry. Synced Oct 27, 2026, 16:17 UTC.