# MeetStream vs tl;dv (slim)

> MeetStream scores 57.3 (C) to tl;dv's 51.2 (D) for meeting transcripts. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meetstream-vs-tldv.md (~4,700 tokens) · this version ~2,980 tokens · JSON https://www.anchorterminal.com/compare/meetstream-vs-tldv.json · canonical https://www.anchorterminal.com/compare/meetstream-vs-tldv
- 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 tl;dv's 51.2 (D), and leads in 4 of 7 scored categories. tl;dv leads on reliability, security & auth and transparency & trust. Both do meeting transcripts.

- MeetStream: C 57.3, rank #803 of 1510 · https://www.anchorterminal.com/tools/meetstream.min.md
- tl;dv: D 51.2, rank #1037 of 1510 · https://www.anchorterminal.com/tools/tldv.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 Schema & documentation, 83 against 66; Agent ergonomics, 88 against 73; Payments & pricing, 40 against 15; Maintenance & community, 82 against 28. Also Free to start without a card.
- tl;dv, good for Teams already recording with tl;dv who want an agent to search and summarise their meeting library or push transcripts to other systems by webhook. Ahead on Reliability, 50 against 45; Security & auth, 49 against 42; Transparency & trust, 65 against 57. Also Runs on your own machine; No incidents deducted, where MeetStream loses 4 points for them.

| Category | MeetStream | tl;dv |
| --- | --- | --- |
| Reliability (16%) | 45 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 83 | 66 |
| Agent ergonomics (13%) | 88 | 73 |
| Security & auth (14%) | 42 | 49 |
| Payments & pricing (10%) | 40 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 82 | 28 |
| Transparency & trust (7%) | 57 | 65 |

| Fact (where they differ) | MeetStream | tl;dv |
| --- | --- | --- |
| Vendor | MeetStream Corp. | tldx Solutions GmbH |
| Hosted endpoint | `https://mcp.meetstream.ai/mcp` | `https://pasta.tldv.io` |
| Transports | HTTP, websocket, Streamable HTTP | HTTP, Streamable HTTP, stdio |
| Pricing | Pay per use | Paid |
| 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 tldx's Terms of Service. The local MCP server repository is public but carries no licence file |
| Tools exposed | 19 | 5 |
| Read-only variant documented | no | yes |
| MCP registry | `io.github.meetstream-ai/meetstream-mcp` | not listed |
| Last release | 2026-10-27 | 2026-09-29 |
| Terms last updated | 2026-08-07 | no date given |
| Privacy policy last updated | 2026-08-07 | no date given |
| Terms restrict benchmarking | not found in the text | yes |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 14 stars |

Why the edge:
- Maintenance & community, MeetStream +54: 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.); tl;dv 28 (The API docs carried no dates on 8 October and were not re-read on 4 November. The newest dated change is still the README commit of 29 September 2026 describing the hosted MCP server, 36 days before this check, with code commits last made on 12 December 2025, per a clone on 4 November (20). No dated releases or changelog entries in the 90 days from 6 August 2026 (0). No public changelog. Support is by email and in-app chat. On 8 October five pull requests were open with no reply and a licence question from 22 October 2025 was unanswered. GitHub's pages answered 403 on 4 November, so this is not re-read (5). No official SDK. Presence in the official MCP registry was read on 8 October through its API, which this check no longer calls, so the line rests on the SDK reading (0). The local server has a GitLab CI file and depends on @modelcontextprotocol/sdk ^1.8.0, and the README says it is not updated regularly (3). 20+0+5+0+3 = 28.)
- Payments & pricing, MeetStream +25: 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.); tl;dv 15 (No x402, MPP or L402 (0). Per the 8 October check, plans are public on a pricing page that renders in the browser, and the help centre gives paid plans as starting at $18 a month. Nothing is priced per call (10). A Free plan exists, and the app's pricing text says no credit card is required, but the Free plan excludes the API, webhooks and MCP, so partial credit (5). A person signs up in a browser, pays for a plan and creates a key or approves an OAuth screen (0). 0+10+5+0 = 15.)
- Schema & documentation, MeetStream +17: 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.); tl;dv 66 (Per the 8 October check, not re-read on 4 November because tl;dv's terms bar crawling its websites. A public OpenAPI 3.0.0 description is embedded in doc.tldv.io with a download button, covering 12 operations and two webhook payloads. Hosted MCP tool schemas need an OAuth session, which we did not have (25). tldv.io/llms.txt exists but indexes marketing pages and blog posts, and no Markdown API docs were found (3). The API reference explains plan gating, ownership and the upload flow. The local MCP tool descriptions are one or two sentences with no guidance on when not to use a tool (10). Enums, patterns, length limits and required fields are set on inputs, and `metadata` is a constrained flat object (12). Request and response samples per operation and two documented error formats with examples. 429 and 403 causes are thinly described (11). The version sits in the path, but no changelog was found (5). 25+3+10+12+11+5 = 66.)
- Agent ergonomics, MeetStream +15: 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.); tl;dv 73 (Per the 8 October check of doc.tldv.io and the help centre, not re-read on 4 November. The hosted MCP server has five read-only tools and the local one four (25). The meeting list takes `query`, `from`, `to`, `onlyParticipated`, `meetingType`, `page` and `limit`. A transcript comes back whole, with no way to size it or select a time range (15). Errors carry a `message` with per-property constraints, or a `name` and `message`, and the docs say when to fix and retry (15). No idempotency keys on import. `dryRun` on import and a retry-safe upload complete call are documented, and both MCP servers are read-only. MCP annotations were unchecked (10). List calls need no parameters and single-meeting calls need one id. No official SDK was found (8). 25+15+15+10+8 = 73.)
- Transparency & trust, tl;dv +8: 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.); tl;dv 65 (Closed service with published Terms of Service, effective 18 May 2026 and unchanged on 4 November. The local MCP repository is public with no licence file (15). Per the 8 October check, not re-read on 4 November, the privacy policy of 9 September 2026 gives retention per data type (Free recordings three months, paid until account deletion, logs 10 days) and states customer content is not used to train models, which agrees with the security page. The DPA was not found at a public URL (22). No deprecation policy. The highlights endpoint is marked deprecated with no removal date, and the help centre says endpoint changes will be announced in advance (5). The privacy policy names sub-processors by category, among them Google Cloud, Hetzner, Wasabi, Anthropic, AssemblyAI and ElevenLabs, and states EU hosting with AI processing in the EU or US by account setting (16). 15+22+5+16 = 58.)
- Security & auth, tl;dv +7: 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.); tl;dv 49 (The hosted MCP server uses OAuth with PKCE S256, one scope and five-minute access tokens per the README, revocable from the account. The REST API uses one unscoped key per user in a header, with no rotation or expiry documented (22). Both MCP servers are read-only, admins can block MCP through integration policies, and access follows the user's library permissions. The API key cannot be limited to read-only and can import media (14). Transcripts and notes are text spoken by meeting participants, and no prompt-injection guidance was found (0). No audit log or per-call record for API or MCP use was found (0). Per the 8 October check of the security page and trust centre, not re-read on 4 November because tl;dv's terms bar crawling its websites. SOC 2 Type II, a vulnerability report address with a stated 24-hour response, and a Vanta trust centre. No security.txt and no bug bounty found. The README says the API and MCP endpoint are in penetration test scope (13). 22+14+0+0+13 = 49.)