# MeetGeek vs MeetStream (slim)

> MeetStream scores 57.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/meetgeek-vs-meetstream.md (~4,250 tokens) · this version ~2,530 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-meetstream.json · canonical https://www.anchorterminal.com/compare/meetgeek-vs-meetstream
- 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)

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

- MeetGeek: D 52.1, rank #1001 of 1510 · https://www.anchorterminal.com/tools/meetgeek.min.md
- MeetStream: C 57.3, rank #803 of 1510 · https://www.anchorterminal.com/tools/meetstream.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 45; Transparency & trust, 67 against 57. Also Runs on your own machine; No incidents deducted, where MeetStream loses 4 points for them.
- MeetStream, good for Developers building their own notetaker or in-meeting voice agent on Zoom, Meet and Teams at per-hour pricing. Ahead on Schema & documentation, 83 against 70; Agent ergonomics, 88 against 59; Payments & pricing, 40 against 30; Maintenance & community, 82 against 10. Also Free to start without a card.

| Category | MeetGeek | MeetStream |
| --- | --- | --- |
| Reliability (16%) | 70 | 45 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 83 |
| Agent ergonomics (13%) | 59 | 88 |
| Security & auth (14%) | 38 | 42 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 82 |
| Transparency & trust (7%) | 67 | 57 |

| Fact (where they differ) | MeetGeek | MeetStream |
| --- | --- | --- |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | MeetStream Corp. |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://mcp.meetstream.ai/mcp` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP, websocket, 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 MeetStream's Terms of Use. The SDKs `@meetstream/sdk` and `meetstream-sdk` and the Go MCP server are published separately |
| Tools exposed | 8 | 19 |
| MCP registry | not listed | `io.github.meetstream-ai/meetstream-mcp` |
| Last release | none | 2026-10-27 |
| Terms last updated | 2026-08-12 | 2026-08-07 |
| Privacy policy last updated | 2026-09-09 | 2026-08-07 |
| Terms restrict benchmarking | yes | not found in the text |

Why the edge:
- Maintenance & community, MeetStream +72: 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.); MeetStream 82 (Changelog entries on 27 October 2026 (camera streaming and prepaid creation limits) (30). Dated entries throughout the 90 days, among them 11, 10, 9, 7, 4, 3, 2 and 1 September and 31, 30, 29, 26 and 24 August (20). A public changelog, support@meetstream.ai and Slack support, with no evidence read of reply times (10 of 15). In the official MCP registry as io.github.meetstream-ai/meetstream-mcp 0.3.0, and official SDKs 1.0.0 since 26 August 2026 (15). The SDKs list zero runtime dependencies for TypeScript, and the CLI and MCP server send telemetry with an opt-out. The repositories weren't cloned (7 of 10). 30+20+10+15+7 = 82.)
- Agent ergonomics, MeetStream +29: 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.); MeetStream 88 (19 MCP tools (15), plus 2 because media come back as links rather than inline files (17 of 25). Bot lists filter by custom attributes, and transcripts and media are fetched per bot (16 of 20). Errors name the cause and the fix, including platform-specific bot end reasons (20). Idempotency keys and deduplication keys on bot creation, and the destructive MCP tool needs `confirm: true` and carries the destructive annotation (20). Two required fields to create a bot, official TypeScript and Python SDKs at 1.x and a CLI (15). 17+16+20+20+15 = 88.)
- Reliability, MeetGeek +25: 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.); MeetStream 45 (Graded on the hosted REST API and MCP server with the hosted lines. No public status page was found, linked or at status.meetstream.ai (0), so no incident history could be read (5). Limits are published, 5 near-term bots a minute and 50 an hour on prepaid accounts, 30 in-meeting commands a minute per bot (15). 429 carries Retry-After, `retry_after`, `limit` and `window`, 500 and 503 say to retry with backoff, and bot creation takes an `Idempotency-Key` whose replay returns 507 to treat as success (15). No SLA found in the Terms or on the pricing page (0). Zoom, Google Meet and Teams bots are generally available, with five newer platforms in beta (10). 0+5+15+15+0+10 = 45.)
- Schema & documentation, MeetStream +13: 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.); MeetStream 83 (No OpenAPI file was found linked from the docs or llms.txt. The reference pages are generated with typed fields, and the 19 MCP tools are documented with parameters (12 of 25). llms.txt per section, a Markdown copy of every page and a docs MCP server (10). Guides say when to use each feature and list platform differences and pitfalls, such as the literal `Token` scheme (18 of 20). Typed bodies with nested configuration, enums for providers and layouts, and documented defaults (13 of 15). Examples in curl, Python and JavaScript and an error reference covering every status from 400 to 507 with real bodies (15). `/api/v1` paths and a dated changelog that flags breaking changes (15). 12+10+18+13+15+15 = 83.)
- Payments & pricing, MeetStream +10: 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.); MeetStream 40 (No x402, MPP or L402 (0). Per-hour prices are public, $0.35 per bot hour, $0.10 for transcription and $0.05 per GB a month of storage past 30 days (20). $5 free credit with no card required (20). Signup and key creation happen in the dashboard, and the MCP OAuth flow needs a person to approve (0). 0+20+20+0 = 40.)
- Transparency & trust, MeetGeek +10: MeetGeek 67 (Closed service with clear terms of 12 August 2026 naming the contracting entity for each instance (15 of 30). The Terms and the Privacy Policy (9 September 2026) agree that customer content isn't used to train models without a written opt-in, give retention per data type with deletion windows (30 days, then 35 days from backups), and refer to a DPA (26 of 30). No deprecation policy, though the Terms promise notice by email or in the app before changes take effect (5 of 20). EU and US instances with data in the chosen region, and a sub-processor list linked from the security page, not read (15 of 20). 15+26+5+15 = 61.); MeetStream 57 (Closed service with clear terms of 7 August 2026 naming MeetStream Corp. (15 of 30). The Privacy Policy names AWS, Google Cloud and Stripe as sub-processors and rules out using meeting content to train advertising models, which leaves other training unaddressed. Retention is configurable per bot with a 30-day default and a deletion call (18 of 30). Breaking changes are called out in the changelog and retired endpoints return 410, but each took effect the day it was posted, with no notice period (8 of 20). Sub-processors named, data locations not stated (10 of 20). 15+18+8+10 = 51.)