# MeetGeek vs Read AI (slim)

> MeetGeek scores 52.1 (D) to Read AI's 42.4 (E) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.md (~3,550 tokens) · this version ~1,830 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-read-ai.json · canonical https://www.anchorterminal.com/compare/meetgeek-vs-read-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)

MeetGeek scores 52.1 (D) on agent readiness against Read AI's 42.4 (E), and leads in 4 of 7 scored categories. Read AI leads on security & auth. Both do meeting transcripts.

- MeetGeek: D 52.1, rank #1001 of 1510 · https://www.anchorterminal.com/tools/meetgeek.min.md
- Read AI: E 42.4, rank #1282 of 1510 · https://www.anchorterminal.com/tools/read-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 27; Schema & documentation, 70 against 46. Also Runs on your own machine.
- Read AI, good for An agent working for a person or team that already records meetings with Read AI and wants transcripts, summaries and action items in context. Ahead on Security & auth, 54 against 38. Also Free to start without a card.

| Category | MeetGeek | Read AI |
| --- | --- | --- |
| Reliability (16%) | 70 | 27 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 46 |
| Agent ergonomics (13%) | 59 | 63 |
| Security & auth (14%) | 38 | 54 |
| Payments & pricing (10%) | 30 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 6 |
| Transparency & trust (7%) | 67 | 64 |

| Fact (where they differ) | MeetGeek | Read AI |
| --- | --- | --- |
| Kind | HTTP API | MCP server |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | Read AI, Inc. |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://api.read.ai/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | Streamable HTTP, HTTP |
| Auth | OAuth or key | OAuth |
| 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 Read AI's terms of service |
| Tools exposed | 8 | 4 |
| Last release | none | 2026-09-02 |
| Terms last updated | 2026-08-12 | 2026-02-26 |
| Privacy policy last updated | 2026-09-09 | 2026-06-29 |
| Customer content may train models | not found in the text | yes, with an opt-out |
| Terms restrict benchmarking | yes | not found in the text |
| Terms or service can change without notice | not found in the text | yes |
| Arbitration or class-action waiver | not found in the text | yes |

Why the edge:
- Reliability, MeetGeek +43: 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.); Read AI 27 (Graded as a hosted service on the MCP server and REST API. Read AI's terms bar robots except to compile search results, so its hosts are paused and the 8 October readings stand where kept. The status page at readai.statuspage.io wasn't re-read on 4 November. Its components and incidents had been read only from the page's data path, which this run doesn't use, so the status-page line scores 0 and the window from 6 August is unread (5). 100 requests a minute per user, per the 8 October check (15). 429 is documented as retry later with no Retry-After or backoff guidance, while create meeting agent and share meeting report are documented as safe to repeat, per the 8 October check (7, a partial value kept). No SLA found (0). Both surfaces are open beta (0). 0+5+15+7+0+0 = 27.)
- Schema & documentation, MeetGeek +24: 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.); Read AI 46 (Per the 8 October check, not re-read on 4 November (terms pause). No public OpenAPI file was found. The MCP tool schemas sit behind sign-in and were not read, and the help centre's parameter tables are prose documentation, not a machine-readable contract, so the contract line scores 0 (the tables count on typed inputs). www.read.ai/llms.txt points to the help centre's article index (10). The API reference says when to use the live endpoint over the standard one, and the MCP article lists inputs, defaults and limits for each of four tools (13). Parameters are typed in tables and access levels are enumerated, with no schema to confirm constraints (8). Each endpoint has a curl request and a sample response. Errors are a table of status codes with no body schema (10). A /v1 path prefix, no changelog (5). 0+10+13+8+10+5 = 46.)
- Security & auth, Read 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.); Read AI 54 (Per the 8 October check, not re-read on 4 November (terms pause). OAuth 2.1 with dynamic client registration, PKCE, 10-minute access tokens, rotating single-use refresh tokens and a revocation endpoint. Only two scopes, `meeting:read` and `mcp:execute`, so MCP access can't be narrowed to reading (24). A token reaches only reports its user can open, and a workspace admin can switch off access through the Downloads setting. No confirmation step is documented for sending a bot or sharing a report by email (9). Transcripts are untrusted speech and no injection guidance was found (0). Workspace audit logs in OCSF by webhook on Enterprise+ record sign-ins and integration connections, not individual calls (6). security.txt valid to 18 August 2027, SOC 2 Type 2 and a HIPAA option per the help centre, no bug bounty found (15). 24+9+0+6+15 = 54.)