# MeetGeek vs tl;dv (slim)

> MeetGeek and tl;dv score within a point of each other for meeting transcripts, 52.1 and 51.2 out of 100. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/meetgeek-vs-tldv.md (~4,300 tokens) · this version ~2,580 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-tldv.json · canonical https://www.anchorterminal.com/compare/meetgeek-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)

MeetGeek and tl;dv score within a point of each other on agent readiness, 52.1 (D) and 51.2 (D). tl;dv leads on agent ergonomics, security & auth and maintenance & community. Both do meeting transcripts.

- MeetGeek: D 52.1, rank #1001 of 1510 · https://www.anchorterminal.com/tools/meetgeek.min.md
- tl;dv: D 51.2, rank #1037 of 1510 · https://www.anchorterminal.com/tools/tldv.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; Payments & pricing, 30 against 15.
- 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 Agent ergonomics, 73 against 59; Security & auth, 49 against 38; Maintenance & community, 28 against 10.

| Category | MeetGeek | tl;dv |
| --- | --- | --- |
| Reliability (16%) | 70 | 50 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 66 |
| Agent ergonomics (13%) | 59 | 73 |
| Security & auth (14%) | 38 | 49 |
| Payments & pricing (10%) | 30 | 15 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 28 |
| Transparency & trust (7%) | 67 | 65 |

| Fact (where they differ) | MeetGeek | tl;dv |
| --- | --- | --- |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | tldx Solutions GmbH |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://pasta.tldv.io` |
| Pricing | Freemium | Paid |
| 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 tldx's Terms of Service. The local MCP server repository is public but carries no licence file |
| Tools exposed | 8 | 5 |
| Read-only variant documented | no | yes |
| Last release | none | 2026-09-29 |
| Terms last updated | 2026-08-12 | no date given |
| Privacy policy last updated | 2026-09-09 | no date given |
| Terms or service can change without notice | not found in the text | yes |
| Popularity | none | 14 stars |

Why the edge:
- 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.); tl;dv 50 (Graded on the hosted REST API and the hosted MCP server, with the hosted lines. Instatus page at tldv.instatus.com with eight components, among them Public API and Webhooks & integrations, each at 100.0% for the 90 days to 4 November 2026 (20). Its incident feed still has no entry after 17 November 2022 (21 entries from 21 July 2021), so the page isn't shown to post incidents and the quiet window isn't credited as a clean record, as for kiwi-mcp and together-fine-tuning (20). No request rate limit is published, per the 8 October check of doc.tldv.io, not re-read on 4 November because tl;dv's terms bar crawling its websites. The docs give page size and result caps and mention a daily import quota without a number (0). 429 is documented only on the beta upload, with no Retry-After or backoff guidance. The upload complete call is documented as safe to retry, and webhooks retry after a 10-second wait, per the 8 October check (5). No SLA in the terms of 18 May 2026, re-read on 4 November, which disclaim availability warranties (0). The REST API is labelled v1alpha1 with changes expected. The hosted MCP server carries no beta label, so half credit (5). 20+20+0+5+0+5 = 50.)
- Maintenance & community, tl;dv +18: 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.); 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, MeetGeek +15: 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.); 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.)
- Agent ergonomics, tl;dv +14: 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.); 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.)
- Security & auth, tl;dv +11: 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.); 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.)