# Fathom (npm · @mindstone/mcp-server-fathom)

Fathom AI meeting transcription MCP server for Model Context Protocol hosts

- Trust score: 67/100 (medium)
- Change this week: +41
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-06

## Components

- npm · `@mindstone/mcp-server-fathom`: 67/100 (this document), [markdown](https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom.md), [page](https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom)

## Channel facts

- Registry: `npm`
- Package: `@mindstone/mcp-server-fathom`
- Version: `0.2.3`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-06.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Known CVEs were checked across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Dependency health was assessed across the 95 of 99 dependencies we could resolve, so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (FSL-1.1-MIT) isn't a recognized OSI-approved license.
  - Actively maintained (last published 79 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 72/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add mindstone-mcp-server-fathom -- npx -y @mindstone/mcp-server-fathom
```

### Codex

```bash
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
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mindstone-mcp-server-fathom --command npx --arg -y --arg @mindstone/mcp-server-fathom
```

### Hermes

```yaml
mcp_servers:
  mindstone-mcp-server-fathom:
    command: "npx"
    args: ["-y", "@mindstone/mcp-server-fathom"]
```

### Other

```json
{
  "mcpServers": {
    "mindstone-mcp-server-fathom": {
      "command": "npx",
      "args": [
        "-y",
        "@mindstone/mcp-server-fathom"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-06 (score 67, +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.

### 2026-08-04 (score 66, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-08-03 (score 62, +28)

- [security regression] Provenance: unverified → fail
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Install scripts: unverified → pass
- [security] Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window).
- [functional regression] License: unverified → fail
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional] Licence: FSL-1.1-MIT

### 2026-08-02 (score 34, +29)

- [security improvement] Malware scan: unverified → pass
- [functional improvement] Tool coverage: unverified → 100

### 2026-08-01 (score 5, −14)

- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-07-31 (score 19, −7)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 26, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-27 (score 44)

First indexed and scored.

## MCP tools (7)

### `configure_fathom_api_key` (~88 tokens)

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").

Input parameters:

- `api_key` (string, required): The Fathom API key

### `list_fathom_meetings` (~358 tokens)

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.

Input parameters:

- `calendar_invitees_domains` (array): Filter by attendee email domains
- `created_after` (string): ISO date string — only return meetings created after this date
- `created_before` (string): ISO date string — only return meetings created before this date
- `limit` (number): Maximum number of results per page
- `meeting_type` (string): Filter by meeting type
- `recorded_by` (array): Filter by email addresses of recorders
- `teams` (array): Filter by team names (e.g., ["Sales", "Engineering"])

### `get_fathom_meeting` (~167 tokens)

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.

Input parameters:

- `recording_id` (integer, required): The recording ID of the meeting (from list_fathom_meetings)

### `get_fathom_transcript` (~267 tokens)

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.

Input parameters:

- `format` (string): Output format: "text" (default) or "json"
- `max_entries` (integer): Maximum number of transcript entries to return
- `recording_id` (integer, required): The recording ID of the meeting (from list_fathom_meetings)
- `search_query` (string): Case-insensitive search query — returns only matching entries plus context
- `start_entry` (integer): Skip first N entries (0-indexed)

### `get_fathom_meeting_participants` (~144 tokens)

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.

Input parameters:

- `recording_id` (integer, required): The recording ID of the meeting (from list_fathom_meetings)

### `list_fathom_teams` (~84 tokens)

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.

### `list_fathom_team_members` (~78 tokens)

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.

Input parameters:

- `team` (string, required): Team name to list members for (from list_fathom_teams)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom#diagnostics

## Score history

- 2026-08-06: 67
- 2026-08-05: 66
- 2026-08-04: 66
- 2026-08-03: 62
- 2026-08-02: 34
- 2026-08-01: 5
- 2026-07-31: 19
- 2026-07-30: 26
- 2026-07-28: 44
- 2026-07-27: 44

## Links

- npm package: https://www.npmjs.com/package/@mindstone/mcp-server-fathom
- Socket report: https://socket.dev/npm/package/@mindstone/mcp-server-fathom
- Repository: https://github.com/mindstone/mcp-servers
- Changelog RSS feed: https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom.xml
- Changelog JSON feed: https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom.json
- HTML version of this page: https://verifymcp.io/servers/mindstone-mcp-server-fathom/mindstone-mcp-server-fathom