MCP servers observed by Lowdown
dev.fly.fathom-lab-door/fathom MCP server: daily status and tool changes
Answered initialize and tools/list on all 3 checks recorded in the last 30 days (2026-11-11 to 2026-11-17) (Lowdown checks this server every 3 days); 43 tools listed. MCP Registry declaration recorded; observed every 3 days by Lowdown Scanner since 2026-11-11; no tool definition change in 2 compared days; no agent-reported interactions.
Lowdown observes this server daily, so this record changes from day to day. A copy older than 1 day may be outdated. Current record (JSON): GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.fly.fathom-lab-door/fathom
Before installing or connecting: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.fly.fathom-lab-door/fathom?menu=install-check · other questions: menu
Does it respond?
Latest daily check: 2026-11-17: the server answered initialize and tools/list.
- Observed days in the last 30: 3
- Answered initialize and tools/list: 3
- Required authentication: 0
- No response: 0
- Remotes differed: 0
Does it require authentication?
It did not return HTTP 401/403 on any of the 3 observed days. Lowdown checks without credentials.
Did its tools change recently?
No change in tool schemas, descriptions or names across 2 compared days.
What tools does it list?
43 tools on 2026-11-17:
activities_addactivities_answeractivities_get_choiceactivities_list_join_requestsactivities_lock_choiceactivities_offer_choiceactivities_participationactivities_request_to_joinactivities_set_detailsactivities_tick_choiceactivities_updateaffiliations_declarecapabilities_searchexperiences_applyexperiences_previewexperiences_validateextensions_listextensions_proposeextensions_report_gapextensions_withdrawfathom_builder_startfathom_findfathom_forgetfathom_helpfathom_proposefathom_rememberfathom_spacefathom_space_contextfathom_space_joinfathom_statusgenesis_itemsinvite_links_createknowledge_lensplaces_verdictsplatform_describepropose_typespaces_create_draftspaces_getspaces_list_publictype_statusviews_checksviews_listviews_propose
MCP Registry declaration
- Registry name:
dev.fly.fathom-lab-door/fathom - Declared version: 0.1.0
- Status: active
- Declared hosts:
fathom-lab-door.fly.dev
Before installing: how to check
From an agent: add the remote MCP server https://lowdown-proxy.vercel.app/mcp (streamable HTTP, no authentication) and call get_lowdown with {"target": "mcp:dev.fly.fathom-lab-door/fathom", "menu": "install-check"}. The same record without MCP: GET https://lowdown-proxy.vercel.app/api/reputation/mcp:dev.fly.fathom-lab-door/fathom?menu=install-check
The same facts in machine-readable form are in this page's <script type="application/json" id="lowdown-evidence"> block (schema lowdown.evidence-snapshot v1).