Circleback vs MeetGeek

Circleback 78

@circleback/cli 1.2.1 published on 3 November 2026 and a release entry on 2 November (30). Dated entries in the 90 days from 8 August, among them the API on 20 August, importing through the API on 9 September, writes through MCP, CLI and API on 7 October and folders in the API on 30 October, with CLI releases 0.9.0 to 1.2.1 since 6 October (20). A public releases page and a support address, with no public issue tracker (8 of 15). In the official MCP registry as ai.circleback/circleback (15). The CLI is MIT with tests and a typecheck step in its scripts and a postinstall that only prints a welcome line. Its repository isn't public (5 of 10). 30+20+8+15+5 = 78.

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.

Circleback 61

OAuth with dynamic client registration and two scopes on MCP, and API keys that are read-only or read and write, shown once (28 of 30). Read-only keys and a read-only MCP scope, and only an owner can delete a meeting. No confirmation step on the API for shares or deletes (14 of 20). Transcripts, notes and emails are participant-written text, and no prompt-injection guidance was found (0). A usage dashboard for workspace admins and meeting access requests, with no audit log of API or MCP calls found (4 of 15). SOC 2 Type II, EU-U.S. Data Privacy Framework certification, HIPAA, an external penetration test report on the security portal and a valid security.txt. No bug bounty found (15 of 20). 28+14+0+4+15 = 61.

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.

Circleback 72

28 MCP tools (15 for 11 to 30), plus 5 for the read-only scope that leaves write tools failing. The API lists return pages with filters (20 of 25). Cursor pagination through a Link header and filters by attendee, tag, folder, ownership and status (20). Errors carry a message and a code such as RATE_LIMITED (16 of 20). No idempotency key, and MCP annotations couldn't be read without a sign-in. Read-only keys and scope keep writes off (8 of 20). Few required parameters. The only official client is the Node CLI, with --json output (8 of 15). 20+20+16+8+8 = 72.

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.

Circleback 81

Each reference page embeds the OpenAPI 3.2 operation for its endpoint, but no single spec file is linked, and MCP input schemas need a sign-in (20 of 25). llms.txt and a Markdown copy of each docs page (10). Operation descriptions state what is returned and who may act, such as only the owner deleting a meeting, and the update call explains replace semantics (16 of 20). Typed parameters with enums and defaults, such as ownership All, Mine or Shared (13 of 15). curl examples, a JSON error envelope with error and code, and 400 and 429 responses per operation (12 of 15). Paths carry no version, and a public releases page dates each entry (10 of 15). 20+10+16+13+12+10 = 81.

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.

Circleback 77

Graded on the hosted REST API and MCP server with the hosted lines. incident.io status page at status.circleback.ai with four components, none of them the API (20). Its history and RSS feed, read on 6 November, list no incident from August to November and no item at all, so the page isn't shown to post incidents and the quiet window isn't credited as clean, as for tldv (20). Limits published per plan, 3 a second and 20 a minute on Free and 20 and 300 on paid plans (15). 429 carries Retry-After and every response carries RateLimit-Limit, -Remaining and -Reset. No idempotency key or safe-retry guidance for writes (12 of 15). No SLA found in the Terms or on the pricing page (0). The API has no beta label (10). 20+20+15+12+0+10 = 77.

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.