Skip to content

welance/directory MCP server

com.welance/directorywelance.comstreamable-httpv1.1.0Scanned

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.

Tools: 0 delete, 3 irreversible, 8 write, 9 read.
  • Reads private data · 2
  • Reads text others write · 1
  • Can send data out · 3
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

3 tools here do something that can't be undone. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the welance/directory MCP server can do

The welance/directory MCP server is published by welance.com, a domain the MCP Registry verified. It has 20 tools. It can do things that cannot be undone, such as sending, paying or publishing (propose_brief_publish, propose_team_invite and propose_pitch_send) and create or change data (8 tools: directory_capabilities, match_brief, brief_rules, propose_brief_draft and 4 more), but cannot delete data. 9 tools only read.

2 tools read private data (read_profile and read_invoices); 1 tool brings in text other people can write (read_invoices); 3 tools can send data out of your system (propose_brief_publish, propose_team_invite and propose_pitch_send). On its own it has all three parts of a prompt-injection exfiltration path: private data, text others write, and a way out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 9, 2026, version 1.1.0.

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 3Claude Code: ask
  • propose_brief_publishA proposal to publish a brief (title, markdown, optional language) 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
    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.

    Annotations the server declares

    • title: Propose publishing a brief
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_pitch_sendA 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.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
    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.

    Annotations the server declares

    • title: Propose sending a pitch
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_team_inviteA proposal to invite a person to one of the signed-in person's teams (teamKey) by name and email, with an optional role.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
    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.

    Annotations the server declares

    • title: Propose inviting someone to a team
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Changes things 8Claude Code: ask
  • brief_rulesThe rule catalogue a brief is scored against before teams see it: ids, labels, weights and the acceptance threshold that decides whether a brief publishes.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 that decides whether a brief 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 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…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 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.

    Annotations the server declares

    • title: Propose meeting times
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_booking_acceptAs the team on a booking (bookingId): a proposal to accept one of the client's offered slots (slotId).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 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.

    Annotations the server declares

    • title: Propose accepting a meeting time
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_brief_draftA proposed update to the person's local brief draft: title, markdown, and/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
    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.

    Annotations the server declares

    • title: Propose a brief draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_pitch_draftAn anonymous pitch draft for one of the person's teams (teamKey) on an open brief (briefId).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
    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.

    Annotations the server declares

    • title: Propose a pitch draft
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • propose_profile_updateProposed field changes to one entity.No findings

    Why it is in this group

    • The name "propose_profile_update" says "update": a word for a change.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Propose profile changes
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
Only reads 9Show 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: 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.

    Annotations the server declares

    • title: A protected preview of the team board
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_bookingOne booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.No findings

    Why it is in this group

    • The name "read_booking" says "read": a word for reading.
    Description, as the server wrote it
    One booking by its id (bookingId): the proposed slots, its state, and which side the signed-in person is on.

    Annotations the server declares

    • title: One booking
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_briefOne public brief in full, markdown body included, by its id (briefId).No findings

    Why it is in this group

    • The name "read_brief" says "read": a word for reading.
    Description, as the server wrote it
    One public brief in full, markdown body included, by its id (briefId).

    Annotations the server declares

    • title: One brief
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_invoicesThe signed-in person's past invoices with their PDF and document links (pdfUrl / documentUrl).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 "document": it reads documents.
    • untrusted-inputThe description's first sentence says "url": it reads web pages, which anyone can write.
    Description, as the server wrote it
    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).

    Annotations the server declares

    • title: My invoices
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_my_pitchesThe 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 brief…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
    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.

    Annotations the server declares

    • title: My briefs, pitches and bookings
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_my_teamsThe 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 te…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
    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.

    Annotations the server declares

    • title: My teams
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_pitchable_briefsFor 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.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 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.

    Annotations the server declares

    • title: Briefs my teams can pitch on
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • read_profileThe signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and 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 "directory": it reads files.
    Description, as the server wrote it
    The signed-in person's own directory profile: job role, years of experience, languages, rated skills, hourly rate and 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.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out3
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
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.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 18, 2026, 16:23 UTC, unchanged since Oct 27, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
11
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
https://welance.com/.well-known/oauth-protected-resource/directory/mcp
Authorization servers
https://welancians.eu.auth0.com/
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
no
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 11 tools that change things (3 irreversible, 8 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://welance.com/directory/mcp: tools/list returned 20 tools to an anonymous client, including propose_brief_publish (irreversible), propose_team_invite (irreversible), propose_pitch_send (irreversible), directory_capabilities (write), match_brief (write) and 6 more

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

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

  1. Tools17 changed.~17 changedView diff

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

Pin

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://radar.anlyon.com/api/v1/servers/com.welance/directory/verify?hash=0e2b120d61d2591b88ebf76cf454ddad5608c78fbae46c3a8e5eadc1bad233f6" | jq -e '.changed == false'

Pinned hash 0e2b120d61d2, from Nov 9, 2026, 16:18 UTC.

Watch

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

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

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

Badge

Anlyon Radar badge for com.welance/directory
[![Anlyon Radar](https://radar.anlyon.com/badge/com.welance/directory.svg)](https://radar.anlyon.com/servers/com.welance/directory)

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

welance/directory MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the welance/directory MCP server safe?

No scan can promise that. What its definitions show: 20 tools, 11 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the welance/directory MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the welance/directory MCP server do things that cannot be undone?

Yes. 3 tools can send, pay, publish or merge: propose_brief_publish, propose_team_invite and propose_pitch_send.

What tools does the welance/directory MCP server have?

20 tools: 3 irreversible, 8 write, 9 read. propose_brief_publish, propose_team_invite, propose_pitch_send, directory_capabilities, match_brief, brief_rules, propose_brief_draft, propose_profile_update and 12 more.

Does the welance/directory MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the welance/directory MCP server send data to outside services?

3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): propose_brief_publish, propose_team_invite and propose_pitch_send.

Has the welance/directory MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 9, 2026. Every change is on this page and in its Atom feed.