# Fathom vs MeetGeek (slim)

> Fathom scores 55.3 (C) to MeetGeek's 52.1 (D) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/fathom-vs-meetgeek.md (~3,950 tokens) · this version ~2,230 tokens · JSON https://www.anchorterminal.com/compare/fathom-vs-meetgeek.json · canonical https://www.anchorterminal.com/compare/fathom-vs-meetgeek
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Fathom scores 55.3 (C) on agent readiness against MeetGeek's 52.1 (D), and leads in 5 of 7 scored categories. MeetGeek leads on reliability. Both do meeting transcripts.

- Fathom: C 55.3, rank #871 of 1486 · https://www.anchorterminal.com/tools/fathom.min.md
- MeetGeek: D 52.1, rank #995 of 1486 · https://www.anchorterminal.com/tools/meetgeek.min.md
- Fathom, good for Teams already recording meetings in Fathom who want an agent to read transcripts, summaries, action items and recordings. Ahead on Schema & documentation, 80 against 70; Agent ergonomics, 64 against 59; Maintenance & community, 37 against 10.
- MeetGeek, good for Agents that read a team's MeetGeek meetings, or upload recordings for analysis, with EU or US residency. Ahead on Reliability, 70 against 58. Also Runs on your own machine.

| Category | Fathom | MeetGeek |
| --- | --- | --- |
| Reliability (16%) | 58 | 70 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 70 |
| Agent ergonomics (13%) | 64 | 59 |
| Security & auth (14%) | 42 | 38 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 37 | 10 |
| Transparency & trust (7%) | 68 | 67 |

| Fact (where they differ) | Fathom | MeetGeek |
| --- | --- | --- |
| Vendor | Fathom Video Inc. | AIVISION PRODUCTS SRL (MeetGeek) |
| Hosted endpoint | `https://api.fathom.ai/external/v1` | `https://mcp.meetgeek.ai/mcp` |
| Transports | HTTP, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Licence | Proprietary service under Fathom's terms of service. The TypeScript and Python SDKs are published on npm and PyPI with no licence in the package metadata | Proprietary service under MeetGeek's Terms of Service. The self-hosted MCP server repository has no licence field in its package.json |
| Tools exposed | none | 8 |
| MCP registry | `ai.fathom.api/mcp` | not listed |
| Last release | 2026-07-29 | none |
| Terms last updated | 2026-03-04 | 2026-08-12 |
| Privacy policy last updated | 2026-08-16 | 2026-09-09 |
| Customer content may train models | yes, with an opt-out | not found in the text |
| Terms restrict benchmarking | not found in the text | yes |
| Arbitration or class-action waiver | yes | not found in the text |
| Popularity | 83k npm/wk, 58k PyPI/wk | none |
| Agent reviews | 4/5 (4) | none |

Why the edge:
- Maintenance & community, Fathom +27: Fathom 37 (The newest dated release on record is SDK version 0.0.43 on 29 July 2026, per the 8 October check, 98 days before this check. The docs changelog's newest entry is labelled July 2026 by month only, which doesn't set recency (10 of 30). SDK 0.0.42 (23 July) and 0.0.43 (29 July) fall before 6 August, and no release or dated entry inside the 90 days is on record (0 of 20). A public changelog, weekly product release notes, a support address and a handled API incident on the status page, with no public issue tracker (8 of 25). Listed in the official MCP registry as ai.fathom.api/mcp, with current TypeScript and Python SDKs (15). The SDKs are generated with Speakeasy, at 0.0.x, with no public repository or licence in the package metadata (4 of 10).); MeetGeek 10 (No API changelog or dated API release was found. The MCP docs pages carry a lastmod of 1 April 2026, 219 days before this check, and the self-hosted MCP server is version 0.1.0 (0). No dated releases in the 90 days from 8 August (0). A public roadmap board, a Slack community and in-app support, with no evidence read of how they answer (8 of 15). No official SDK and no entry in the official MCP registry (0). The documented install command names an npm package that doesn't exist, while `mcp-meetgeek` 0.1.0 was published from a personal account on 5 September 2025 (2 of 10). 0+0+8+0+2 = 10.)
- Reliability, MeetGeek +12: Fathom 58 (Graded on the hosted REST API and MCP server, per the 8 October check, not re-read on 4 November. Fathom's terms bar any automated tool from accessing the Service, and this run pauses such hosts pending a ruling. status.fathom.video is a Statuspage site, per the 8 October check (20). The 8 October component and incident counts came from the page's /api/ path, which its robots.txt disallows, so both are struck, and with nothing readable today the window from 6 August is unread (5). Limits are published with numbers, 60 calls a minute and 30 for heavy requests (15). 429 carries `Retry-After` and `RateLimit-*` headers and the SDKs retry. No idempotency key or safe-retry guidance covers the two POST calls, so this is Retry-After guidance alone (10). No uptime SLA was found. Enterprise lists priority support SLAs only (0). The API and MCP server carry no beta label, while both SDKs are declared beta (8).); MeetGeek 70 (Graded on the hosted REST API and cloud MCP server with the hosted lines. Instatus page at meetgeek.instatus.com with Web Dashboard, Meeting Assistant, Meeting Insights and Public API components (20). Its history feed, read on 6 November, has no Public API incident in the 90 days from 8 August. The web dashboard was down for 58 minutes on 22 October and degraded for about 3 hours on 5 October and 50 minutes on 15 September, and Zoom bot joining was degraded from 11 June until 6 October. None hit the API, so minor only (20). Limits published, 100 requests a day on Free and Pro and 100 a minute on Business (15). 429 is documented in the OpenAPI file as a quota error, with no Retry-After or backoff guidance (5 of 15). No SLA found (0). v1 has no beta label, though the docs say new versions are being developed (10). 20+20+15+5+0+10 = 70.)
- Schema & documentation, Fathom +10: Fathom 80 (A public OpenAPI 3.1.1 document covers all 11 operations and the webhook payload (25). llms.txt and a Markdown copy of every page (10). Endpoint descriptions state behaviour and limits, such as which parameters OAuth apps cannot use, but the MCP tool definitions are not published and need a sign-in to read (13 of 20). Parameters are typed with enums, formats and `additionalProperties: false` on the webhook body (13 of 15). The quickstart has curl, Python and TypeScript examples with a full sample response, while error responses are a status code and one line of description with no body schema (9 of 15). The path is versioned `v1` and a public changelog exists, with entries labelled by month only and four entries since October 2025 (10 of 15). Per the 8 October check, not re-read on 4 November.); MeetGeek 70 (Public OpenAPI 3.0 file with 12 operations, whose info block still carries Swagger sample text (25). llms.txt and Markdown pages (10). Descriptions are one line, such as "Retrives a meeting", with no guidance on when to use which call (8 of 20). Few parameters, typed, with `limit` and `cursor` on lists (10 of 15). Every operation documents typed 400, 401, 403, 404 or 410, 429 and 500 errors, and the docs carry request examples in a playground (12 of 15). Paths under /v1, with no changelog found (5 of 15). 25+10+8+10+12+5 = 70.)
- Agent ergonomics, Fathom +5: Fathom 64 (Responses are sized with `include_transcript`, `include_summary`, `include_action_items`, `include_highlights` and `include_crm_matches`, all off by default, and separate summary and transcript endpoints. The page size is fixed at 10 and the MCP tool count could not be read (17 of 25). Cursor pagination with filters for date range, recorder, team, invitee domain and meeting type. No page-size parameter, attendee filter or text search (15 of 20). Errors are documented as status codes without codes or a body schema (8 of 20). Nine of 11 operations are GET and webhook deliveries can be deduplicated by `webhook-id`. No idempotency keys, and MCP annotations could not be read (10 of 20). Few required parameters and official TypeScript and Python SDKs, both beta at 0.0.43 (14 of 15). Per the 8 October check, not re-read on 4 November.); MeetGeek 59 (The cloud MCP server has 8 compact tools, and the transcript is paged with `limit` up to 500 segments (23 of 25). Cursor pagination on meetings and transcripts, with no date or attendee filters on the list (12 of 20). Typed error bodies per status code (14 of 20). No idempotency key on uploads or bot joins, and MCP annotations weren't readable without a sign-in (5 of 20). Few required parameters, no official SDK, and a self-hosted MCP server whose documented npm name doesn't exist (5 of 15). 23+12+14+5+5 = 59.)