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

NPM · @MINDSTONE/MCP-SERVER-FATHOM · SCANNED AUG 6

Fathom AI meeting transcription MCP server for Model Context Protocol hosts

+41 this week 67 Trust /100
Trust breakdown (6 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score →

Supply Chain Security87
  • No malware found by supply-chain analysis.Pass
  • Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability72
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1186 tokens (~169/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management33
  • Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Install

Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.

npm · @mindstone/mcp-server-fathom

# add to Claude Code
claude mcp add mindstone-mcp-server-fathom -- npx -y @mindstone/mcp-server-fathom
# add to Codex CLI
codex mcp add mindstone-mcp-server-fathom -- npx -y @mindstone/mcp-server-fathom
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mindstone-mcp-server-fathom": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@mindstone/mcp-server-fathom"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add mindstone-mcp-server-fathom --command npx --arg -y --arg @mindstone/mcp-server-fathom
# ~/.hermes/config.yaml
mcp_servers:
  mindstone-mcp-server-fathom:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-fathom"]
// mcp.json
{
  "mcpServers": {
    "mindstone-mcp-server-fathom": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-fathom"
      ]
    }
  }
}
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.

  • 6 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Aug 26 +4
    • Stability: unverified → 0.27 functional
  • 3 Aug 26 +28
    • Provenance: unverified → fail security
    • Known CVEs: unverified → partial security
    • Install scripts: unverified → pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • License: unverified → fail functional
    • Schema quality: unverified → excellent functional
    • Dependency health: unverified → partial functional
    • Maintenance: unverified → pass functional
    • MCP protocol: unverified → pass functional
    • Licence: FSL-1.1-MIT functional
  • 2 Aug 26 +29
    • Malware scan: unverified → pass security
    • Tool coverage: unverified → 100 functional
  • 1 Aug 26 −14
    • Tool coverage: 100 → unverified functional
    • First check of Schema quality: unverified functional
  • 31 Jul 26 −7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 −18
    • Malware scan: pass → unverified security
  • 27 Jul 26 44

    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 6 Aug 2026 · Analysed npm/@mindstone/[email protected]

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm
Dependencies 95 packages
Packages resolved 95
Deprecated 95
Stale 29
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

MCP tools — 7 exposed · ~1,186 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.

Tool Tokens
configure_fathom_api_key ~88

Configure the Fathom API key. Call this tool when the user provides their Fathom API key. Get your API key from https://fathom.video/customize#api-access-header — click "Add +", select "Generate API Key", name it (e.g., "MCP Server").

NameTypeReqDescription
api_keystringyesThe Fathom API key

No output schema declared.

No examples provided.

get_fathom_meeting ~167

Get details for a single Fathom meeting by its recording_id. Finds the meeting in your recent history and fetches its AI-generated summary. Returns: - Meeting title, scheduled times, duration - Recording URL and shareable link - Calendar invitees with names/emails - AI-generated summary (if available) Note: Searches through up to 10 pages of recent meetings. For older meetings, use list_fathom_meetings with created_after/created_before date filters first. For transcript content, use get_fathom_transcript separately. Rate limit: May use 1-11 API calls depending on meeting position in history.

NameTypeReqDescription
recording_idintegeryesThe recording ID of the meeting (from list_fathom_meetings)

No output schema declared.

No examples provided.

get_fathom_meeting_participants ~144

Get the list of participants for a Fathom meeting by its recording_id. Returns an array of calendar invitees including their name, email, email domain, and whether they are an external attendee. Note: Searches through up to 10 pages of recent meetings to find the meeting if it is not in the first page. For older meetings, use list_fathom_meetings with created_after/created_before date filters first. Rate limit: May use 1-11 API calls depending on meeting position in history.

NameTypeReqDescription
recording_idintegeryesThe recording ID of the meeting (from list_fathom_meetings)

No output schema declared.

No examples provided.

get_fathom_transcript ~267

Get the transcript for a Fathom meeting by its recording_id. Output formats (use 'format' parameter): - "text" (default): Human-readable format: "[HH:MM:SS] Speaker Name: What they said" - "json": Compact JSON array with full metadata (speaker object, timestamps, text) Filtering options to reduce output size: - search_query: Case-insensitive search — returns only matching lines plus context - max_entries: Limit number of transcript entries returned - start_entry: Skip first N entries (for pagination) For large transcripts, use search_query to find relevant sections rather than fetching everything. Rate limit: Counts as 1 API call (Fathom allows ~60/minute). Use list_fathom_meetings first to find the recording_id.

NameTypeReqDescription
formatstringOutput format: "text" (default) or "json"
max_entriesintegerMaximum number of transcript entries to return
recording_idintegeryesThe recording ID of the meeting (from list_fathom_meetings)
search_querystringCase-insensitive search query — returns only matching entries plus context
start_entryintegerSkip first N entries (0-indexed)

No output schema declared.

No examples provided.

list_fathom_meetings ~358

List meetings from Fathom with server-side filtering. Returns meeting metadata including: - recording_id: Primary identifier for get_fathom_meeting and get_fathom_transcript - title, scheduled_start_time, duration - calendar_invitees: Array of attendees with name/email - teams: Teams the meeting belongs to Server-side filters (use these to narrow results efficiently): - teams: Filter by team names - recorded_by: Filter by recorder email addresses - calendar_invitees_domains: Filter by attendee email domains (e.g., find all meetings with acme.com) - meeting_type: 'internal' (same org) or 'external' (with outsiders) - created_after/created_before: Date range filters (ISO format) NOTE: Fathom does NOT have server-side keyword search. To find meetings by keyword, list meetings with filters then examine results yourself, or use get_fathom_transcript to search transcript content. Pagination: Returns up to 'limit' results (default 25). hasMore=true indicates more pages exist. Rate limit: Fathom allows ~60 API calls/minute.

NameTypeReqDescription
calendar_invitees_domainsarrayFilter by attendee email domains
created_afterstringISO date string — only return meetings created after this date
created_beforestringISO date string — only return meetings created before this date
limitnumberMaximum number of results per page
meeting_typestringFilter by meeting type
recorded_byarrayFilter by email addresses of recorders
teamsarrayFilter by team names (e.g., ["Sales", "Engineering"])

No output schema declared.

No examples provided.

list_fathom_team_members ~78

List members of a specific team in Fathom. Returns team members with: - User ID and email - Name and role - Join date Use list_fathom_teams first to get available team names.

NameTypeReqDescription
teamstringyesTeam name to list members for (from list_fathom_teams)

No output schema declared.

No examples provided.

list_fathom_teams ~84

List all teams accessible to the user in Fathom. Returns teams with: - name: Team name (use for filtering meetings or listing members) - created_at: When the team was created (if available) Use this to find team names for filtering meetings with list_fathom_meetings or listing team members with list_fathom_team_members.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.