# MeetGeek vs Recall.ai (slim)

> Recall.ai scores 59.7 (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/meetgeek-vs-recall-ai.md (~4,700 tokens) · this version ~2,930 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-recall-ai.json · canonical https://www.anchorterminal.com/compare/meetgeek-vs-recall-ai
- 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)

Recall.ai scores 59.7 (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.

- MeetGeek: D 52.1, rank #1001 of 1510 · https://www.anchorterminal.com/tools/meetgeek.min.md
- Recall.ai: C 59.7, rank #684 of 1510 · https://www.anchorterminal.com/tools/recall-ai.min.md
- 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 50. Also Runs on your own machine.
- Recall.ai, good for Developers building a notetaker or meeting agent who want one API across Zoom, Google Meet, Teams and Webex and will handle summaries, consent and per-customer access themselves. Ahead on Schema & documentation, 80 against 70; Agent ergonomics, 71 against 59; Security & auth, 54 against 38; Payments & pricing, 35 against 30; Maintenance & community, 63 against 10.

| Category | MeetGeek | Recall.ai |
| --- | --- | --- |
| Reliability (16%) | 70 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 80 |
| Agent ergonomics (13%) | 59 | 71 |
| Security & auth (14%) | 38 | 54 |
| Payments & pricing (10%) | 30 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 63 |
| Transparency & trust (7%) | 67 | 67 |

| Fact (where they differ) | MeetGeek | Recall.ai |
| --- | --- | --- |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | Hyperdoc Inc. |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://us-west-2.recall.ai` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, Streamable HTTP |
| Pricing | Freemium | Pay per use |
| Licence | Proprietary service under MeetGeek's Terms of Service. The self-hosted MCP server repository has no licence field in its package.json | Proprietary service under Recall.ai's terms of use. Sample apps on GitHub, some MIT and most with no licence file |
| Tools exposed | 8 | 45 |
| Last release | none | 2026-10-08 |
| Terms last updated | 2026-08-12 | 2026-10-01 |
| Privacy policy last updated | 2026-09-09 | 2023-02-01 |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 91k npm/wk |
| Agent reviews | none | 3.5/5 (4) |

Why the edge:
- Maintenance & community, Recall.ai +53: 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.); Recall.ai 63 (Desktop Recording SDK 2.0.36 reached npm on 8 October 2026, and the Create Bot reference was updated on 23 September (30, 27 days before 4 November). The SDK changelog has nine dated entries between 20 July and 25 September 2026. The API has no changelog of its own, so 15 of 20. Support by email and dashboard chat on every plan and a shared Slack channel on contract plans, with no public forum or issue tracker for the API (8). The Desktop SDK on npm is current. No REST client library, and the MCP server wasn't found in the official MCP registry (5). The SDK publishes nightly builds. We couldn't see its CI (5). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Reliability, MeetGeek +20: 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.); Recall.ai 50 (Graded on the hosted lines for the REST API. No public status page was found. The site and docs link none, status.recall.ai doesn't resolve, and service status is exposed only through MCP tools that need a login (0). No readable incident history (5). Rate limits are published per endpoint and per workspace, such as 120 requests a minute for Create Bot, 60 for list endpoints and 300 for retrieve endpoints (15). 429 and 507 carry `Retry-After`, 409 asks for exponential backoff, and `Idempotency-Key` covers every POST, PUT and PATCH for one hour (15). The pricing page lists uptime guarantees on Enterprise only, with no published figure (5). The bot API is generally available. GoTo Meeting support is beta (10). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Security & auth, Recall.ai +16: MeetGeek 38 (Plain bearer API keys per region with no scopes or rotation guidance found. The cloud MCP uses an OAuth sign-in through auth.meetgeek.ai with Google or Microsoft, with the requested permissions not documented (20 of 30). No read-only key. The API can delete meetings and send a bot to a meeting with no confirmation step (4 of 20). Transcripts and summaries are participant speech, and no prompt-injection guidance was found (0). No audit log of API or MCP use found (0 of 15). Annual SOC 2 Type II audit, yearly penetration tests, a responsible disclosure address and a security portal, with no security.txt (404) or bug bounty (14 of 20). 20+4+0+0+14 = 38.); Recall.ai 54 (REST API keys are revocable but don't expire and carry no scopes, so one key reaches the whole workspace. The MCP server takes OAuth with PKCE and dynamic client registration or MCP API keys, both limited by 22 scopes that can't change after creation (23). MCP is read-only by default, with separate write and developer scopes. The REST API has no read-only key and no confirmation step, and deleting a recording or removing a bot is permanent (11). Transcripts and meeting chat are participant-written, and no prompt-injection guidance was found (0). The Explorer dashboard and MCP tools show per-bot and workspace logs and webhook deliveries. No audit log of user or key actions was found (8). The site links a SOC 2 Type 2 report and an ISO 27001 certificate in a Vanta trust centre we couldn't render. security.txt returns 404, and no bug bounty or disclosure policy was found (12). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Agent ergonomics, Recall.ai +12: 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.); Recall.ai 71 (Media and transcripts come back as download URLs, so responses stay small, but no field selection was found and the docs say a bot response contains a lot of data. The MCP server lists 45 tools and hides those outside the granted scopes (13). Cursor pagination with `next` and `previous`, and filters by status, platform, meeting URL, time and custom metadata. No page-size parameter was found (16). Errors carry a `code` and `detail`, with a 400 reference and bot sub codes for failures (17). `Idempotency-Key` on POST, PUT and PATCH, and deduplication keys for calendar bots. MCP tool annotations weren't readable without a login (17). Create Bot needs only `meeting_url`. No official REST client library was found, and `recallai` on PyPI is a 2022 placeholder (8). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Schema & documentation, Recall.ai +10: 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.); Recall.ai 80 (Every reference page embeds an OpenAPI 3.0.3 definition for its operation, with security schemes and `x-throttles`. No single downloadable spec file was found (22). llms.txt indexes 273 lines of guides and reference pages, each with a Markdown twin (10). Create Bot explains scheduled and ad-hoc bots and when to use each, and the MCP page gives a description and use case for each of 45 tools (17). The Create Bot definition has 145 schemas, 189 enums and one required field. Third-party transcription settings and `metadata` pass through as open objects (13). The errors page lists HTTP codes, 400 error codes and bot sub codes, but Create Bot documents only 201, 400 and 507 responses, and the 400 has no body schema (11). The path is versioned as v1 with workspace-level versions 1.10 and 1.11 and release notes for 1.11. No running API changelog was found (7). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)
- Payments & pricing, Recall.ai +5: MeetGeek 30 (No x402, MPP or L402 (0). Plan prices are public but inconsistent, $15.99 and $27 a user a month on the plan cards and $9.99 and $17 in the page's calculator, with nothing priced per call (10). The free Basic plan includes the API and MCP with 3 hours of transcription a month, free forever (20). A person signs up in a browser and copies a key or approves an OAuth screen (0). 0+10+20+0 = 30.); Recall.ai 35 (No x402, MPP or L402. The API's 402 is a credit-balance error (0). Per-unit prices are public, at $0.50 an hour of recording, $0.15 an hour of built-in transcription and $0.000069 per recording-hour per stored hour after seven days (20). The first five hours of recording are free, and the billing docs describe adding a payment method as a later step. We didn't walk through signup to confirm no card is asked for (15). A person signs up in a browser and creates the first key in the dashboard (0). Per the 8 October check, not re-read on 4 November, because Recall.ai's terms bar automated access to the non-API parts of the service.)