# MeetGeek vs Zoom Realtime Media Streams (RTMS) (slim)

> Zoom Realtime Media Streams scores 58.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-zoom-rtms.md (~3,700 tokens) · this version ~1,930 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms.json · canonical https://www.anchorterminal.com/compare/meetgeek-vs-zoom-rtms
- 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)

Zoom Realtime Media Streams (RTMS) scores 58.3 (C) on agent readiness against MeetGeek's 52.1 (D), and leads in 4 of 7 scored categories. MeetGeek leads on payments & pricing. Both do meeting transcripts.

- MeetGeek: D 52.1, rank #1001 of 1510 · https://www.anchorterminal.com/tools/meetgeek.min.md
- Zoom Realtime Media Streams (RTMS): C 58.3, rank #757 of 1510 · https://www.anchorterminal.com/tools/zoom-rtms.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 Payments & pricing, 30 against 0. Also Runs on your own machine.
- Zoom Realtime Media Streams (RTMS), good for Apps that need live Zoom media or transcripts without a bot, including in-meeting agents. Ahead on Security & auth, 63 against 38; Maintenance & community, 73 against 10; Transparency & trust, 73 against 67.

| Category | MeetGeek | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Reliability (16%) | 70 | 67 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 71 |
| Agent ergonomics (13%) | 59 | 59 |
| Security & auth (14%) | 38 | 63 |
| Payments & pricing (10%) | 30 | 0 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 73 |
| Transparency & trust (7%) | 67 | 73 |

| Fact (where they differ) | MeetGeek | Zoom Realtime Media Streams (RTMS) |
| --- | --- | --- |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | Zoom Communications, Inc. |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://api.zoom.us/v2` |
| Transports | HTTP, Streamable HTTP, stdio | websocket, HTTP |
| Auth | OAuth or key | OAuth |
| 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 the Zoom API Licence and Terms of Use. The `@zoom/rtms` SDK is MIT on npm |
| Tools exposed | 8 | none |
| Last release | none | 2026-10-30 |
| Terms last updated | 2026-08-12 | 2025-07-16 |
| Privacy policy last updated | 2026-09-09 | 2026-09-17 |
| 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:
- Maintenance & community, Zoom Realtime Media Streams (RTMS) +63: 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.); Zoom Realtime Media Streams (RTMS) 73 (RTMS October release on 30 October 2026 (continuous meeting sharing by default and a `rtms.request_status` webhook) (30). Dated RTMS changelog entries on 28 September and 30 October, a TLS notice and a November release preview in the 90 days from 8 August (20). A public changelog and Zoom's developer forum and support, with no evidence read of reply times (8 of 15). The official `@zoom/rtms` SDK is at 1.1.0 from 16 April 2026, behind the protocol changes since (10 of 15). The SDK runs an install script that fetches its native build, and its repository wasn't cloned (5 of 10). 30+20+8+10+5 = 73.)
- Payments & pricing, MeetGeek +30: 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.); Zoom Realtime Media Streams (RTMS) 0 (No x402, MPP or L402 (0). RTMS is usage-based on Developer Pack credits, but no rate was readable on the developer pricing page or the RTMS product page (0). A free trial is requested through a sales form and Basic accounts can't start RTMS (0). A person creates the app, buys credits and submits the app for review (0). 0+0+0+0 = 0.)
- Security & auth, Zoom Realtime Media Streams (RTMS) +25: 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.); Zoom Realtime Media Streams (RTMS) 63 (OAuth 2.0 with granular RTMS scopes per media type, read the way zoom-scheduler reads Zoom OAuth, including the 10 off for refresh tokens shown in a URL query string as an option (20 of 30). Least privilege is strong. Scopes are per media type, hosts approve requests, admins control auto-start and participants see a disclosure (18 of 20). Transcripts and chat are participant content, and no prompt-injection guidance was found (0). Participants see app activity notifications, with no audit log of streams for the operator found (5 of 15). Zoom's security.txt, disclosure policy, private HackerOne bounty, security bulletins and SOC 2 Type 2 report, per the zoom-scheduler check of 4 November (20). 20+18+0+5+20 = 63.)
- Transparency & trust, Zoom Realtime Media Streams (RTMS) +6: 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.); Zoom Realtime Media Streams (RTMS) 73 (Closed service under the Zoom API Licence and Terms of Use of 16 July 2025, as for zoom-scheduler (15 of 30). The Privacy Statement (17 September 2026) and Terms of Service say communications-like customer content isn't used to train AI models, with no fixed retention periods, per the zoom-scheduler check; RTMS streams to the customer's own app, which holds the data (18 of 30). Advance, dated notices in the RTMS changelog, such as TLS 1.2 from 15 November 2026 and a V2 preview, beside API terms that let Zoom deprecate without prior notice (14 of 20). The sub-processor list (2 October 2026) names third parties and affiliates with locations, per the zoom-scheduler check (18 of 20). 15+18+14+18 = 65.)