# MeetStream vs Recall.ai (slim)

> Recall.ai scores 59.7 (C) to MeetStream's 57.3 (C) for meeting bots. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meetstream-vs-recall-ai.md (~4,750 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/meetstream-vs-recall-ai.json · canonical https://www.anchorterminal.com/compare/meetstream-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 MeetStream's 57.3 (C), and leads in 3 of 7 scored categories. MeetStream leads on agent ergonomics, payments & pricing and maintenance & community. Both do meeting bots.

- MeetStream: C 57.3, rank #803 of 1510 · https://www.anchorterminal.com/tools/meetstream.min.md
- Recall.ai: C 59.7, rank #684 of 1510 · https://www.anchorterminal.com/tools/recall-ai.min.md
- MeetStream, good for Developers building their own notetaker or in-meeting voice agent on Zoom, Meet and Teams at per-hour pricing. Ahead on Agent ergonomics, 88 against 71; Payments & pricing, 40 against 35; Maintenance & community, 82 against 63. Also Free to start without a card.
- 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 Reliability, 50 against 45; Security & auth, 54 against 42; Transparency & trust, 67 against 57. Also No incidents deducted, where MeetStream loses 4 points for them.

| Category | MeetStream | Recall.ai |
| --- | --- | --- |
| Reliability (16%) | 45 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 80 |
| Agent ergonomics (13%) | 88 | 71 |
| Security & auth (14%) | 42 | 54 |
| Payments & pricing (10%) | 40 | 35 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 63 |
| Transparency & trust (7%) | 57 | 67 |

| Fact (where they differ) | MeetStream | Recall.ai |
| --- | --- | --- |
| Vendor | MeetStream Corp. | Hyperdoc Inc. |
| Hosted endpoint | `https://mcp.meetstream.ai/mcp` | `https://us-west-2.recall.ai` |
| Transports | HTTP, websocket, Streamable HTTP | HTTP, Streamable HTTP |
| Price for meeting bots | $0.35 per session-hour | $0.0083 per minute of call |
| Licence | Proprietary service under MeetStream's Terms of Use. The SDKs `@meetstream/sdk` and `meetstream-sdk` and the Go MCP server are published separately | Proprietary service under Recall.ai's terms of use. Sample apps on GitHub, some MIT and most with no licence file |
| Tools exposed | 19 | 45 |
| MCP registry | `io.github.meetstream-ai/meetstream-mcp` | not listed |
| Last release | 2026-10-27 | 2026-10-08 |
| Terms last updated | 2026-08-07 | 2026-10-01 |
| Privacy policy last updated | 2026-08-07 | 2023-02-01 |
| Terms restrict benchmarking | not found in the text | yes |
| 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, MeetStream +19: 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.); 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.)
- Agent ergonomics, MeetStream +17: 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.); 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.)
- Security & auth, Recall.ai +12: MeetStream 42 (A key grants full access to its workspace's bots and data, and workspaces separate keys. MCP sign-in is OAuth, which mints a key per connection. No scopes or read-only keys found (15 of 30). `delete_bot_data` needs `confirm: true` and is marked destructive, and `remove_bot` keeps recordings, with no read-only mode (10 of 20). Transcripts, chat and audio come from meeting participants, and no prompt-injection guidance was found (0). A dashboard bot detail page and signed webhooks, with no audit log of API calls found (5 of 15). ISO 27001 certified (630036), SOC 2 Type 2 under audit, HIPAA with a BAA, a trust centre and HMAC-signed webhooks. No security.txt (404) or bug bounty found (12 of 20). 15+10+0+5+12 = 42.); 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.)
- Transparency & trust, Recall.ai +10: 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.); Recall.ai 67 (Closed service with terms of use dated 1 October 2026 naming Hyperdoc Inc. (15). Retention is documented per data type, with a DPA, deletion that includes backups, a zero data retention mode and a statement that customer data isn't used to train models. The privacy policy dates from 1 February 2023 and says data is stored in the United States, which doesn't mention the EU and Tokyo regions the docs describe (24). The release notes say API versions 1.10 and 1.11 will both be supported forever. No deprecation policy or dated notices were found (6). The docs name Svix (EU, 90 days) and Datadog (US and EU, 7 days) with what they hold, and four regions with data residency. The full sub-processor list is in the trust centre, which didn't render for us (15). 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, Recall.ai +5: 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.); 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.)
- Payments & pricing, MeetStream +5: 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.); 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.)