Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fathom (lab)

REMOTE · FATHOM-LAB-DOOR.FLY.DEV

Find places and groups around an interest in a town, each with a source; propose what is missing.

63 Trust /100

Last scanned (9 hours ago)

Scores higher than 44% of remote servers

Reachable. Last reached 5 Nov 2026.

Category Maps and Location

Recent critical change

Authorization (2 Nov 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security57
Transport & Reachability100
Schema Quality & AI Usability71
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 3201 tokens (~71/item across 45 items; 43 tools + 2 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
  • Stability check failed: schema churn in the 4 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 21 additions. See how to fix → Fail
Tool Coverage75
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 25% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 45 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 4 Nov 26 +1
    • Tool “invite_links_create” rewrote its description, which is the text the model reads security
  • 3 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • New tool “activities_answer”, which the server declares destructive security
    • New tool “activities_lock_choice”, which the server declares destructive security
    • New tool “activities_update”, which the server declares destructive security
    • New tool “experiences_apply”, which the server declares destructive security
    • Tool “activities_get_choice” rewrote its description, which is the text the model reads security
    • Tool “activities_list_join_requests” rewrote its description, which is the text the model reads security
    • Tool “activities_participation” rewrote its description, which is the text the model reads security
    • Tool “activities_request_to_join” rewrote its description, which is the text the model reads security
    • Tool “activities_set_details” rewrote its description, which is the text the model reads security
    • Tool “affiliations_declare” rewrote its description, which is the text the model reads security
    • Tool “capabilities_search” rewrote its description, which is the text the model reads security
    • Tool “experiences_preview” rewrote its description, which is the text the model reads security
    • Tool “experiences_validate” rewrote its description, which is the text the model reads security
    • Tool “extensions_list” rewrote its description, which is the text the model reads security
    • Tool “extensions_propose” rewrote its description, which is the text the model reads security
    • Tool “extensions_report_gap” rewrote its description, which is the text the model reads security
    • Tool “extensions_withdraw” rewrote its description, which is the text the model reads security
    • Tool “fathom_builder_start” rewrote its description, which is the text the model reads security
    • Tool “fathom_find” rewrote its description, which is the text the model reads security
    • Tool “fathom_forget” rewrote its description, which is the text the model reads security
    • Tool “fathom_propose” rewrote its description, which is the text the model reads security
    • Tool “fathom_remember” rewrote its description, which is the text the model reads security
    • Tool “fathom_status” rewrote its description, which is the text the model reads security
    • Tool “genesis_items” rewrote its description, which is the text the model reads security
    • Tool “knowledge_lens” rewrote its description, which is the text the model reads security
    • Tool “places_verdicts” rewrote its description, which is the text the model reads security
    • Tool “platform_describe” rewrote its description, which is the text the model reads security
    • Tool “propose_type” rewrote its description, which is the text the model reads security
    • Tool “spaces_get” rewrote its description, which is the text the model reads security
    • Tool “type_status” rewrote its description, which is the text the model reads security
    • Tool “views_checks” rewrote its description, which is the text the model reads security
    • Tool “views_list” rewrote its description, which is the text the model reads security
    • Tool “views_propose” rewrote its description, which is the text the model reads security
    • Tool coverage: 31% → 25% ▼ functional
    • Schema quality: fail → pass ▲ functional
    • New tool “activities_add” functional
    • New tool “activities_offer_choice” functional
    • New tool “activities_tick_choice” functional
    • New tool “fathom_help” functional
    • New tool “fathom_space” functional
    • New tool “fathom_space_context” functional
    • New tool “fathom_space_join” functional
    • New tool “invite_links_create” functional
    • New tool “spaces_create_draft” functional
    • “fathom_find” added an optional parameter “question” cosmetic
    • “extensions_propose” reworded the description of “fields” cosmetic
    • “extensions_propose” reworded the description of “id” cosmetic
    • “extensions_propose” reworded the description of “kind” cosmetic
    • “extensions_propose” reworded the description of “purpose” cosmetic
    • “fathom_propose” reworded the description of “kind” cosmetic
    • “fathom_propose” reworded the description of “source” cosmetic
    • “fathom_propose” reworded the description of “when” cosmetic
    • “fathom_propose” reworded the description of “yes” cosmetic
    • “fathom_remember” reworded the description of “keep” cosmetic
  • 2 Nov 26 +3
    • Authorization: unverified → fail ▼ critical
    • Stability: unverified → fail ▼ security
    • A breaking change shipped without a version bump: still 0.1.0 ▼ security
    • New tool “activities_set_details”, which the server declares destructive security
    • New tool “fathom_forget”, which the server declares destructive security
    • Tool “extensions_list” rewrote its description, which is the text the model reads security
    • Tool “extensions_propose” rewrote its description, which is the text the model reads security
    • Tool “genesis_items” rewrote its description, which is the text the model reads security
    • Tool “knowledge_lens” rewrote its description, which is the text the model reads security
    • Tool “extensions_withdraw” is now declared destructive security
    • Schema quality: pass → fail ▼ functional
    • “extensions_propose” changed the type of “version”: number → integer ▼ functional
    • Tool coverage: 0% → 31% ▲ functional
    • Destructive annotations: All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. functional
    • New tool “activities_request_to_join” functional
    • New tool “fathom_builder_start” functional
    • New tool “fathom_find” functional
    • New tool “fathom_propose” functional
    • New tool “fathom_remember” functional
    • New tool “fathom_status” functional
    • “extensions_propose” added an optional parameter “kind” cosmetic
    • “extensions_propose” reworded the description of “extension” cosmetic
    • “extensions_propose” reworded the description of “fields” cosmetic
    • “extensions_propose” reworded the description of “id” cosmetic
    • “extensions_propose” reworded the description of “purpose” cosmetic
    • “extensions_propose” reworded the description of “title” cosmetic
    • “extensions_propose” reworded the description of “version” cosmetic
  • 1 Nov 26 59

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Probed https://fathom-lab-door.fly.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.fly.dev CN=YE1,O=Let's Encrypt,C=US 20 Oct 2026 18 Jan 2027 ECDSA 256 ECDSA-SHA384 5e6e25e6df778e81cd07b85fc9f12d4df7d
SANs: *.fly.dev
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fathom-lab-door.fly.dev. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
dev. present 60074 8 Verified
fly.dev. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fathom-lab-door.fly.dev/mcp Verified 200
http (plaintext) http://fathom-lab-door.fly.dev/mcp HTTPS enforced 301 https://fathom-lab-door.fly.dev/mcp
MCP tools · 43 exposed · ~3,106 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
activities_add ~155

Add a synthetic activity to a Space as its owner. Only a person can mark one real.

NameTypeReqDescription
bringarray––
concernRolestring––
descriptionstring––
findingstring––
firstTimestring––
groundRulesarray––
levelstring––
offerWindowHoursinteger––
offerWindowMsinteger––
placesinteger––
provenancestringyes–
spaceIdstringyes–
titlestringyes–
tokenstring––
whenstringyes–
wherestringyes–
whoForstring––

No output schema declared.

No examples provided.

activities_answer ~82

Refused for AIs: a person's answer to an activity is theirs alone, given on the people page. Tell your person what activities_participation shows; never answer for them.

NameTypeReqDescription
activityIdstringyes–
answerstringyes–
othersinteger––
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

activities_get_choice ~41

Read an activity's current choices and ticks.

NameTypeReqDescription
activityIdstringyes–
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

activities_list_join_requests ~42

List join requests for the owner or requester.

NameTypeReqDescription
activityIdstringyes–
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

activities_lock_choice ~49

Lock one option of an open activity choice.

NameTypeReqDescription
activityIdstringyes–
optionIdstringyes–
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

activities_offer_choice ~99

Let the group choose a time, place, or approved ability field, as the Space owner. Text labels come only from a person on the people page.

NameTypeReqDescription
activityIdstringyes–
extensionIdstring––
fieldstring––
kindstringyes–
optionsarray––
spaceIdstringyes–
tokenstring––
versionnumber––

No output schema declared.

No examples provided.

activities_participation ~79

Read the person's activity answer, places and offers. ifOthersCount ("N would come if others say they're in") is a count of people who are not coming. Never add it to coming or tell anyone they will have company.

NameTypeReqDescription
activityIdstringyes–
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

activities_request_to_join ~134

Ask to join an activity for your person, only after they said they want to. It asks to join the activity, all its dates, not one evening. Give your person the undoUrl: it is their own page for this request, and Withdraw is there. Keep it for them; the status URL alone can't take the request back.

NameTypeReqDescription
activityIdstringyesThe activity id, from /ask or spaces_get.
namestring–Optional first name or nickname; no email, phone or link.
spaceIdstringyesThe group id, from /ask or spaces_list_public.

No output schema declared.

No examples provided.

activities_set_details ~60

Attach validated extension values to an activity.

NameTypeReqDescription
activityIdstringyes–
extensionIdstringyes–
spaceIdstringyes–
tokenstring––
values–yes–
versionnumberyes–

No output schema declared.

No examples provided.

activities_tick_choice ~77

Tick activity choices only when your person says what works.

NameTypeReqDescription
activityIdstringyes–
optionIdsarrayyesThe option ids that work for your person (from fathom_space or activities_get_choice).
spaceIdstringyes–
tokenstringyesYour person's own token from fathom_space_join.

No output schema declared.

No examples provided.

activities_update ~132

Change an activity as its Space owner. Plain text only; an AI may not mark it real.

NameTypeReqDescription
activityIdstringyes–
bringarray––
concernRolestring––
descriptionstring––
findingstring––
firstTimestring––
groundRulesarray––
provenancestring––
spaceIdstringyes–
titlestring––
tokenstring––
whenstring––
wherestring––
whoForstring––

No output schema declared.

No examples provided.

affiliations_declare ~87

Say how interests relate (serves, kind-of, part-of, alias-of). It lands as recommended: never used or shown to members until the steward approves it. Terms are plain text, never a person.

NameTypeReqDescription
labelstring––
objectstringyes–
relationstringyes–
subjectstringyes–
tokenstring––

No output schema declared.

No examples provided.

capabilities_search ~29

Search the available synthetic capability catalog.

NameTypeReqDescription
querystringyes–
tokenstring––

No output schema declared.

No examples provided.

experiences_apply ~36

Apply an owner-approved trusted experience manifest.

NameTypeReqDescription
manifest–yes–
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

experiences_preview ~30

Preview the current trusted experience manifest.

NameTypeReqDescription
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

experiences_validate ~27

Validate a declarative experience manifest.

NameTypeReqDescription
manifest–yes–
tokenstring––

No output schema declared.

No examples provided.

extensions_list ~23

List approved extensions and your own proposals.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

extensions_propose ~201

Propose a strict data-only ability; it stays pending until a steward reviews it. The id must not name a town: abilities work in every town; where they apply is data.

NameTypeReqDescription
closesGapstring––
extension––The whole definition as one object { id, version, kind, title, purpose, fields }; or send those fields flat instead.
fieldsarray–At most 8 fields.
idstring–An id such as commons.golf-round.
kindstring–'commons' for a group's own use; 'commercial' for a business offer.
purposestring–One sentence: what it helps a group know, at most 300 characters.
titlestring–What it is called, at most 40 characters.
tokenstring––
versioninteger–1 for a new ability; a changed one is the next version.

No output schema declared.

No examples provided.

extensions_report_gap ~52

Report a missing capability and why it matters.

NameTypeReqDescription
amendsstring––
attempted–yes–
needstringyes–
tokenstring––
whystringyes–

No output schema declared.

No examples provided.

extensions_withdraw ~39

Withdraw your proposed extension before steward review.

NameTypeReqDescription
extensionIdstringyes–
tokenstring––
versionnumberyes–

No output schema declared.

No examples provided.

fathom_builder_start ~21

Start a builder sandbox with a synthetic Space and activity.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

fathom_find ~122

Find public places and synthetic groups for an interest in a town. Read-only. Pass your person's memory link as memory to put what fits them first.

NameTypeReqDescription
intereststringyesThe interest, for example pottery or klatring.
memorystring–Optional: your person's own memory link, exactly as they have it.
pageinteger–Optional: page of ten places, from 1.
questionstring–Optional: the person's question in their own words.
townstringyesThe town, for example Oslo.

No output schema declared.

No examples provided.

fathom_forget ~58

Forget a memory for good when your person asks, using their own link exactly as they have it.

NameTypeReqDescription
linkstringyesYour person's own memory link, for example https://…/memories/mem-…?key=…

No output schema declared.

No examples provided.

fathom_help ~33

Read the full current guidance for a Fathom tool.

NameTypeReqDescription
toolstringyesThe tool name to explain.

No output schema declared.

No examples provided.

fathom_propose ~357

Only after your person said yes to this exact proposal. Propose a missing place or community, or (kind offer) your person's own spare capacity. A place needs a source: any https page about it that you read, your person gave you, or Fathom listed. It returns an undoUrl; give your person the undoUrl: it is their own page for the proposal, and Withdraw is there. It stays pending until a steward reviews it, and is never shown as fact before that. An offer never says who: no email, phone, link or address.

NameTypeReqDescription
intereststringyesThe interest it serves, for example pottery.
kindstringyesA person's own spare capacity, only with their yes.
namestringyesIts name; for an offer, what is offered, for example a spare kiln shelf.
newTownstring–Only when your person confirmed a real town the lab does not cover yet.
notestring–Optional: one line on why it fits.
said_asstring–Optional: the word your person used for the interest, when it differs (for example klatring); the interest is stored as the matched one.
sourcestring–Any https page about it that you read, your person gave you, or Fathom listed; required for a place, optional for a community.
townstringyesThe town it is in, for example Oslo.
whenstring–Only for an offer: optional short words on when, for example Thursday evenings.
yesstring–Required for an offer (kind offer), and sent only after your person said yes to this exact offer.

No output schema declared.

No examples provided.

fathom_remember ~99

Keep how your person likes to meet, choices only, only after your person said yes to being remembered (send keep: "yes"). Give them the private link it returns.

NameTypeReqDescription
daysstring–Optional: weekdays or weekends.
keepstringyesSend yes only after your person said yes to being remembered.
levelstring–Optional: beginner or experienced.
timestring–Optional: daytime or evenings.

No output schema declared.

No examples provided.

fathom_space ~48

Read a private Space as its members see it.

NameTypeReqDescription
spaceIdstringyes–
tokenstringyesA builder token, or a person's own token from fathom_space_join.

No output schema declared.

No examples provided.

fathom_space_context ~101

Add one fact to a Space you built: with the https page that states it, or synthetic: "yes" when made up for the plan.

NameTypeReqDescription
factstringyesOne fact, plain text.
sourcestring–The https page that states the fact.
spaceIdstringyes–
syntheticstring–yes when the fact is made up for this plan.
tokenstringyesYour builder token.

No output schema declared.

No examples provided.

fathom_space_join ~102

Join a builder's private Space for your person through their invite link, only after your person said yes to joining. Returns their own token for activities_tick_choice and fathom_space.

NameTypeReqDescription
invitestringyesThe whole invitation link (…/join/…), or its token.
namestringyesThe first name or nickname your person wants the others to see.
yesstringyesSend yes only after your person said yes to joining.

No output schema declared.

No examples provided.

fathom_status ~81

Read a proposal, join request, or your person's own memory by its link, given exactly as your person has it. Read-only.

NameTypeReqDescription
linkstringyesThe status link, for example https://…/proposals/prop-1 or https://…/joins/join-1, or just its id; or your person's own memory link.

No output schema declared.

No examples provided.

genesis_items ~64

Read the places and activities a genesis run found, from position since. Relay the attribution lines and the unclaimed line exactly as returned, and keep each place's source link next to its name.

NameTypeReqDescription
run–––
since–––
tokenstring––

No output schema declared.

No examples provided.

invite_links_create ~73

Create a private invite link for a Space. An open invite link can't protect names Fathom was never given: leave invited people's names out of the purpose and activity text, so that each person's name shows to others only after their own yes.

NameTypeReqDescription
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

knowledge_lens ~86

Answer 'where can I … in <town>' with sourced places. Relay the attribution lines and the unclaimed line exactly as returned. When you pass a place on to your person, keep its source link next to its name, so they can see where it comes from.

NameTypeReqDescription
interest–––
limit–––
tokenstring––
town–––

No output schema declared.

No examples provided.

places_verdicts ~25

Read the person's own private place answers.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

platform_describe ~27

Describe Fathom and its safe synthetic lab boundary.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

propose_type ~92

Propose a data-only kind or predicate the knowledge layer lacks; it answers "use X" when one exists. Examples that are people, and kinds named for a person or role, are refused.

NameTypeReqDescription
definition–––
differs_from–––
examples–––
identity_rule–––
name–––
parent–––
tokenstring––
use–––

No output schema declared.

No examples provided.

spaces_create_draft ~48

Create a synthetic draft Space for the delegated principal.

NameTypeReqDescription
purposestringyes–
tokenstring––
townstring––
visibilitystringyes–

No output schema declared.

No examples provided.

spaces_get ~33

Read a Space when its visibility rules allow it.

NameTypeReqDescription
spaceIdstringyes–
tokenstring––

No output schema declared.

No examples provided.

spaces_list_public ~25

List public synthetic Spaces visible to the caller.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

type_status ~35

Read a kind or predicate's status and evidence.

NameTypeReqDescription
class–––
name–––
tokenstring––

No output schema declared.

No examples provided.

views_checks ~47

Run the steward checks for a view trial.

NameTypeReqDescription
spaceIdstring––
tokenstring––
versionintegeryes–
viewIdstringyes–

No output schema declared.

No examples provided.

views_list ~23

List approved and your own proposed views.

NameTypeReqDescription
tokenstring––

No output schema declared.

No examples provided.

views_propose ~32

Propose a bounded synthetic-place view for steward review.

NameTypeReqDescription
tokenstring––
view–yes–

No output schema declared.

No examples provided.

Install

How do I install the Fathom (lab) MCP server?

Fathom (lab) is a hosted endpoint at https://fathom-lab-door.fly.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · fathom-lab-door.fly.dev

# add to Claude Code
claude mcp add --transport http dev-fly-fathom-lab-door-fathom 'https://fathom-lab-door.fly.dev/mcp'
Common questions

What is the Fathom (lab) MCP server?

Fathom (lab) is an MCP server listed in the public MCP registry as dev.fly.fathom-lab-door/fathom. Find places and groups around an interest in a town, each with a source; propose what is missing. This page covers its hosted endpoint (https://fathom-lab-door.fly.dev/mcp).

Is the Fathom (lab) MCP server safe to use?

Fathom (lab) scores 63 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Fathom (lab) MCP server expose?

Fathom (lab) exposes 43 tools: fathom_find, activities_request_to_join, fathom_status, fathom_propose, fathom_remember, and 38 more. Their descriptions and schemas cost roughly 3,106 tokens of context every time the server is loaded.

Does the Fathom (lab) MCP server require authentication?

No. We connected to Fathom (lab) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Fathom (lab) MCP server still maintained?

Fathom (lab) is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.