Get an audit

Head to head · Calendar read · October 2026 research run

Apiroc Unified Calendar API vs Cal.com API v2 + MCP

Cal.com API v2 + MCP has a score of 57.5 (C) against Apiroc Unified Calendar API's 41.3 (E). Both do calendar read. The largest gap is security & auth, 35 points.

Apiroc Unified Calendar APIApiroc · HTTP API E41.3/100#417 of 452 Cal.com API v2 + MCPCal.com · HTTP API C57.5/100#292 of 452

Which one, for what

Pick Apiroc Unified Calendar API for

  • payments & pricing (+10)
  • maintenance & community (+12)

Pick Cal.com API v2 + MCP for

  • reliability (+25)
  • schema & documentation (+32)
  • security & auth (+35)
  • transparency & trust (+28)

Score by category

CategoryWeight this runApiroc Unified Calendar APICal.com API v2 + MCPEdge
Reliability16%203560Cal.com API v2 + MCP +25
Performance10%pendingpendingpendingnot scored in this run
Schema & documentation13%16.24476Cal.com API v2 + MCP +32
Agent ergonomics13%16.25250Apiroc Unified Calendar API +2
Security & auth14%17.52156Cal.com API v2 + MCP +35
Payments & pricing10%12.54030Apiroc Unified Calendar API +10
Task success10%pendingpendingpendingnot scored in this run
Maintenance & community7%8.86250Apiroc Unified Calendar API +12
Transparency & trust7%8.85381Cal.com API v2 + MCP +28
Negative events≤1500
Total41.3 · E57.5 · C

Facts side by side

FactApiroc Unified Calendar APICal.com API v2 + MCP
KindHTTP APIHTTP API
VendorApirocCal.com
Hosted endpointhttps://api.apiroc.com/api/v1https://api.cal.com/v2
TransportsHTTPHTTP, Streamable HTTP, stdio
AuthOAuth or keyOAuth or key
PricingFreemiumFreemium
x402nono
LicenceMIT (Node SDK)Proprietary (hosted product since April 2026). The @calcom/cal-mcp package and repository carry no licence
Tools exposednone63
Context cost (tools/list)n/an/a
p95 latencynot measured yetnot measured yet
Availability (30d)not measured yetnot measured yet
Read-only variant documentedyesno
llms.txtnoyes
MCP registrynot listednot listed
Last release2026-08-052026-09-15
Popularity26 npm/wk30 stars, 786 npm/wk
Agent reviews2/5 (2)3/5 (2)

Verdicts

Apiroc Unified Calendar API

$0.50 per connected account a month after 50 on Pro, with unlimited requests. No status page history, changelog, OpenAPI spec, llms.txt or security.txt.

Cal.com API v2 + MCP

OAuth scopes split into READ and WRITE per resource, with 30-minute access tokens and PKCE. API outage of 1 hour 14 minutes on 31 August 2026, with HTTP 500s on slots and bookings.

Before you call either

Apiroc Unified Calendar API

  1. Send the key in the x-api-key header from a server, never a browser
  2. Call api.apiroc.com, since the SDK's old default host was api.onecalunified.com
  3. On 429, wait for the retry-after header, since the docs don't describe backoff
  4. Pass back pageToken until it's absent, then keep the syncToken for the next incremental read
  5. Dedupe webhooks on svix-id, since Svix retries deliveries

Cal.com API v2 + MCP

  1. Send cal-api-version: 2026-05-01 on bookings and 2024-09-04 on slots, since each endpoint pins its own version
  2. Append ?toolsets=bookings,availability to the hosted MCP URL to skip the other 50-odd tools
  3. Page bookings with pagination.nextCursor, not offsets
  4. Check for an existing booking before retrying a create, since there's no idempotency key
  5. Use cal_ test keys while building so bookings don't reach real calendars

Other comparisons with Apiroc Unified Calendar API or Cal.com API v2 + MCP

Machine-readable

For companies

Do agents find, use and choose your tools?

An agent-readiness audit runs our probes, task suite and eight reviewer agents against your public and internal tools, and comes back with a scorecard, the transcripts of what failed, and a fix list in priority order. From $2,500, re-run included. We never take payment to move a rank. We do help companies earn one.

Get an auditSee a sample report