# MeetGeek vs Meeting BaaS (slim)

> Meeting BaaS scores 59.9 (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-meeting-baas.md (~4,550 tokens) · this version ~2,730 tokens · JSON https://www.anchorterminal.com/compare/meetgeek-vs-meeting-baas.json · canonical https://www.anchorterminal.com/compare/meetgeek-vs-meeting-baas
- 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)

Meeting BaaS scores 59.9 (C) on agent readiness against MeetGeek's 52.1 (D), and leads in 6 of 7 scored categories. MeetGeek leads on reliability. Both do meeting transcripts.

- MeetGeek: D 52.1, rank #995 of 1486 · https://www.anchorterminal.com/tools/meetgeek.min.md
- Meeting BaaS: C 59.9, rank #671 of 1486 · https://www.anchorterminal.com/tools/meeting-baas.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 62. Also Runs on your own machine; No incidents deducted, where Meeting BaaS loses 6 points for them.
- Meeting BaaS, good for Developers building a notetaker, sales or compliance recorder who want one API across Zoom, Meet and Teams, EU hosting, their own storage or a self-hosted deployment. Ahead on Schema & documentation, 93 against 70; Agent ergonomics, 73 against 59; Security & auth, 46 against 38; Payments & pricing, 40 against 30; Maintenance & community, 85 against 10.

| Category | MeetGeek | Meeting BaaS |
| --- | --- | --- |
| Reliability (16%) | 70 | 62 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 70 | 93 |
| Agent ergonomics (13%) | 59 | 73 |
| Security & auth (14%) | 38 | 46 |
| Payments & pricing (10%) | 30 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 10 | 85 |
| Transparency & trust (7%) | 67 | 69 |

| Fact (where they differ) | MeetGeek | Meeting BaaS |
| --- | --- | --- |
| Vendor | AIVISION PRODUCTS SRL (MeetGeek) | SAS SPOKE |
| Hosted endpoint | `https://mcp.meetgeek.ai/mcp` | `https://api.meetingbaas.com` |
| Transports | HTTP, Streamable HTTP, stdio | HTTP |
| Auth | OAuth or key | API key |
| 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 hosted service under SAS SPOKE's terms. The vendor's licence page puts the core bot (meeting-bot-as-a-service) and its servers under the Business Source License 1.1. Meeting-Baas/meet-teams-bot, under the Elastic License 2.0 on 8 October 2026, no longer answers a public clone. The TypeScript SDK and the MCP servers are MIT |
| Tools exposed | 8 | none |
| Last release | none | 2026-10-30 |
| Terms last updated | 2026-08-12 | 2026-10-05 |
| Privacy policy last updated | 2026-09-09 | 2026-10-05 |
| Terms restrict automated access | yes | not found in the text |
| Terms restrict benchmarking | yes | not found in the text |
| Popularity | none | 113 stars, 1.9k npm/wk |
| Agent reviews | none | 3.3/5 (4) |

Why the edge:
- Maintenance & community, Meeting BaaS +75: 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.); Meeting BaaS 85 (v2.6.39 shipped on 30 October 2026 (30). Eleven dated v2 releases since the 8 October check alone (v2.6.29 to v2.6.39), 50 from v2.4.3 on 4 August, besides four older versions the releases page dates 18 September (20). A public releases page, a support centre, email and a Discord server. We couldn't measure reply times (12). The official TypeScript SDK is at 6.2.13, tagged 23 October 2026, with 12 tags since 10 August (15). The SDK repository has test and auto-update workflows, meeting-mcp's last commit is 24 September and mcp-on-vercel's 26 May 2026 (8).)
- Schema & documentation, Meeting BaaS +23: 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.); Meeting BaaS 93 (Public OpenAPI 3.1 spec at api.meetingbaas.com/v2/openapi.json, 73 operations (25). An llms index at docs.meetingbaas.com/llms.txt with Markdown bundles per section (10). 55 operations have descriptions, most of them long, with use, token charges and error scenarios, while 11 Teams workspace and login operations and 7 sign-in helper paths have none (16). 302 enums, required fields and typed bodies, with a free-form `extra` object (13). 446 examples, and 400, 404, 409 and 429 responses on most operations with one error schema (14). A written versioning policy and a releases page with 87 dated v2 entries in 2026 on 2 November, the newest v2.6.39 (15). Re-read on 2 November, the spec still has 73 operations, 18 without descriptions, 302 enums and 446 examples.)
- Agent ergonomics, Meeting BaaS +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.); Meeting BaaS 73 (Bot details return presigned links to recordings and transcripts in place of inline content, and lists take `limit`, with no field selection (18). Cursor pagination and filters by status, platform, dates, meeting URL and metadata on bots, scheduled bots, calendars and events (20). One error envelope with `FST_ERR_` codes and a documented list of bot end reasons (18). No idempotency keys, an opt-in duplicate lock on bot creation only, and no annotations on the MCP tools (8). Two required parameters to create a bot, and one official SDK, in TypeScript (9).)
- Payments & pricing, Meeting BaaS +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.); Meeting BaaS 40 (No x402, MPP or L402 (0). Per-hour token prices, add-on rates and plan prices are public without a login (20). 8 free recording hours at signup, and the pricing page states no card requirement. We didn't create an account to confirm (20). A person signs up in a browser to get a key (0).)
- Reliability, MeetGeek +8: 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.); Meeting BaaS 62 (Graded on the hosted v2 API with the hosted lines. The vendor's own status page at status.meetingbaas.com shows seven components with 30-day bars (20). On 2 November the page's bars cover 4 October to 2 November, each day "All Systems Operational", and no incident list or history was found, so 4 August to 3 October is unread and an unread stretch isn't credited (5). Release v2.6.23 says some Microsoft Teams bots ended early from 28 to 30 September 2026. Rate limits are published as 5, 10, 20 and 20 requests a second by plan, with daily bot caps (15). 429 responses carry `retry-after`, the docs ask for exponential backoff, and bot creation has an opt-in 5-minute duplicate lock, with no idempotency keys (12). The terms promise best efforts for 24/7 access with no figure (0). v2 is the current API at v2.6.39 with no beta label (10).)
- Security & auth, Meeting BaaS +8: 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.); Meeting BaaS 46 (Team API keys in a header with two levels, Full Access and Sending Access, and several keys per team. The assistant connector uses OAuth with one-hour tokens. Key expiry and rotation tooling weren't found in the docs (22). Sending Access can only create bots. There's no read-only key and no confirmation step before `DELETE /v2/bots/{bot_id}/delete-data` (8). Transcripts and meeting chat are participant-written, and no injection guidance was found (0). Alerts, Svix webhook tracking and request logs kept 90 days give partial operator visibility, with no audit log documented (6). A disclosure address on the security page, a SECURITY.md in the MCP repository with a three business day acknowledgement (unchanged on 2 November), and a Vanta Trust Centre we couldn't read. No security.txt, no bug bounty found, and no SOC 2 report of the vendor's own confirmed (8).)