{ "data": { "a": { "slug": "cronitor-mcp", "name": "Cronitor MCP server", "vendor": "Cronitor", "vendorUrl": "https://cronitor.io", "kind": "mcp", "category": "observability", "summary": "Cronitor's hosted MCP server lets an agent create and manage cron job, heartbeat and uptime monitors, issues, status pages, alert integrations and metrics in a Cronitor account, over OAuth or an API key.", "url": "https://www.anchorterminal.com/tools/cronitor-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json", "dns": "cronitor-mcp.grade.anchorterminal.com", "transports": [ "streamable-http" ], "remoteUrl": "https://cronitor.io/mcp", "packages": [], "auth": "oauth", "authNotes": "OAuth through protected-resource metadata, with sign-in and consent in a browser; the token carries the user's role, capped at the SDK Integration key's permissions, with no scope selection. An API key in a header works for headless clients, with the key's granular read or write scopes.", "pricing": "freemium", "pricingNotes": "Free forever for 5 monitors. Business is $2 a monitor and $5 a user a month after a 14-day trial (checked 2026-11-07).", "priceSummary": "Freemium", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07).", "endpoints": [] }, "toolCount": 71, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-07" }, "docsUrl": "https://cronitor.io/docs/mcp-server", "llmsTxt": "https://cronitor.io/llms.txt", "registryName": "io.cronitor/cronitor", "capabilities": [ "observability.incidents", "observability.metrics", "events.schedule", "agent.tools" ], "tags": [ "official", "hosted", "mcp", "remote-mcp", "oauth", "api-key", "freemium", "free-tier", "status-page", "llms-txt", "mcp-registry" ], "graded": true, "anchor": { "graded": true, "score": 59.1, "grade": "C", "agentReady": false, "rank": 718, "ranked": true, "rankOf": 1510, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 37 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-07" }, "negative": 0, "verdict": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.", "bestFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "strengths": [ "Strict input schemas (additionalProperties false) with enums and required combinations", "Summary modes with paging keep list output small", "JSON-RPC error codes with retry_after_seconds and required_scope", "Clear guidance on secrets in event messages and output", "Free plan for 5 monitors" ], "weaknesses": [ "71 tools, a heavy context load", "No public changelog", "Terms and privacy closed to crawlers, so unread", "No audit log of agent calls found" ], "agentNotes": [ "Start with list_monitors and list_issues in summary mode", "Ask the user before expanding event messages, command output or request bodies", "On a rate-limit error, wait retry_after_seconds", "Over the plan's monitor limit, new monitors are saved but disabled" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "C", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 59.1 } ], "editorialScores": { "ergonomics": 73, "maintenance": 55, "payments": 40, "reliability": 55, "schema": 80, "security": 58, "transparency": 25 }, "provenanceScore": 48, "checked": { "categories": { "ergonomics": "2026-11-07", "maintenance": "2026-11-07", "payments": "2026-11-07", "reliability": "2026-11-07", "schema": "2026-11-07", "security": "2026-11-07", "transparency": "2026-11-07" }, "last": "2026-11-07", "oldest": "2026-11-07", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add cronitor --transport http https://cronitor.io/mcp", "config": { "mcpServers": { "cronitor": { "url": "https://cronitor.io/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/cronitor-mcp" }, "area": "developer", "provenance": { "legalEntity": "Cronitor", "domain": "cronitor.io", "domainRegistered": "", "domainNote": "Not looked up: RDAP isn't requested under the 1 November 2026 rules.", "endpointOnVendorDomain": true, "terms": "", "privacy": "", "statusPage": "https://status.cronitor.io", "changelog": "", "securityTxt": "none", "checked": "2026-11-07", "notes": [ "robots.txt disallows the terms and privacy pages, so the legal entity wasn't read.", "security.txt answered 404." ], "score": 48 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/cronitor-mcp.json", "live": { "slug": "cronitor-mcp", "probe": { "target": "https://cronitor.io/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T01:01:26.14186466Z", "lastOk": true, "lastStatus": 401, "lastMs": 584, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 627, "p95ms24h": 717, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-07", "probes": 53, "ok": 53 }, { "date": "2026-11-08", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.cronitor.io", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:31:11.053343459Z" }, "updatedAt": "2026-11-08T01:01:26.14186466Z" } }, "answer": "incident.io API scores 68.9 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 6 of 7 scored categories. Cronitor MCP server leads on payments \u0026 pricing.", "b": { "slug": "incident-io", "name": "incident.io API", "vendor": "Pineapple Technology Ltd. (incident.io)", "vendorUrl": "https://incident.io", "kind": "http-api", "category": "observability", "summary": "incident.io is an incident response, on-call, alerting and status page service. Agents reach it through a REST API at api.incident.io with an OpenAPI description and seven SDKs, a hosted MCP server and the `inc` CLI.", "url": "https://www.anchorterminal.com/tools/incident-io", "markdownUrl": "https://www.anchorterminal.com/tools/incident-io.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/incident-io.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/incident-io.json", "dns": "incident-io.grade.anchorterminal.com", "repo": "https://github.com/incident-io/sdk-ts", "license": "Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT", "transports": [ "http" ], "remoteUrl": "https://mcp.incident.io/mcp", "packages": [ { "registry": "npm", "name": "@incident-io/sdk" }, { "registry": "pypi", "name": "incident-io" } ], "auth": "mixed", "authNotes": "The REST API takes an API key as a Bearer token. An admin creates an organisation key in Settings and picks its permissions, 13 of which can be limited to named teams. A user key has its owner's current role. Keys are shown once and do not expire. The MCP server takes the same keys, or OAuth with PKCE for a person, which an admin must enable and which lasts 28 days. Access is self-serve on a paid plan, with no app review.", "pricing": "paid", "pricingNotes": "API, webhooks and MCP are not included in the free Basic plan. Team is $19 per user a month for incident response ($15 with the annual discount) plus $10 for on-call. Pro is $25 plus $20 for on-call, billed yearly through sales. Enterprise is quoted. API calls are not metered. The terms define a 14-day trial, which the docs say sales sets up for Pro and Enterprise. No sandbox below Enterprise (checked 2026-10-09).", "priceSummary": "$19 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the API reference, the OpenAPI description or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": null, "npmWeekly": 1318, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.incident.io/api-reference/introduction", "llmsTxt": "https://docs.incident.io/llms.txt", "openapi": "https://api.incident.io/v1/openapiV3.json", "capabilities": [ "observability.incidents", "work.oncall" ], "tags": [ "hosted", "rest", "openapi", "llms-txt", "mcp", "api-key", "oauth", "incidents", "on-call", "status-pages", "cli", "typescript", "python", "go", "status-page", "sla", "soc2" ], "lastRelease": "2026-10-31", "graded": true, "anchor": { "graded": true, "score": 68.9, "grade": "B", "agentReady": false, "rank": 266, "ranked": true, "rankOf": 1510, "categoryRank": 2, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 75, "maintenance": 83, "payments": 10, "reliability": 90, "schema": 88, "security": 64, "transparency": 77 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "high", "date": "2026-11-01" }, "negative": -2, "negativeNotes": [ "2026-04-09, 2026-06-26 and 2026-09-30: the API changelog records the request property `time_to_ack_seconds` removed from `POST /v2/escalation_paths`, the request property `version` removed from `POST /v2/alert_routes`, and the response property `layer_id` removed from `GET /v2/schedules`, each with no earlier deprecation entry in a changelog that starts on 5 January 2026. The docs say existing endpoints get no breaking changes. Whether customers were told another way was not established, so the deduction is 2 (https://docs.incident.io/api-reference/changelog)." ], "verdict": "The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only.", "bestFor": "Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.", "strengths": [ "OpenAPI 3.0.3 description with 284 operations, per-resource description files, llms.txt and Markdown twins of every docs page", "API keys carry chosen permissions, 13 of the 36 scopable to named teams, and user keys take the owner's role", "Default limit of 1,200 requests a minute per key, `X-RateLimit-*` headers on every response and `Retry-After` on 429", "`idempotency_key` is required on seven create calls, among them incidents, escalations and status page incidents", "API changelog generated from the description file, with 53 dated entries between 3 August and 30 October 2026" ], "weaknesses": [ "The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month", "Audit logs are Enterprise only and reach the customer by CSV export or log stream, with no API to read them", "Alert event and heartbeat endpoints accept the alert source token in a `token` query parameter", "The changelog records three removals from live endpoints in 2026 with no earlier deprecation entry", "The security FAQ says no data leaves Europe, while the sub-processor list of 27 July 2026 names 17 processors in the United States" ], "agentNotes": [ "Send `Authorization: Bearer \u003ckey\u003e` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles", "Send a fresh `idempotency_key` with every create call for incidents, incident updates, timeline items, escalations and status page incidents. A repeated key returns the first result", "Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page", "Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429", "Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 3.5, "history": [ { "basis": "public evidence", "confidence": "high", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.9 } ], "editorialScores": { "ergonomics": 75, "maintenance": 83, "payments": 10, "reliability": 90, "schema": 88, "security": 64, "transparency": 72 }, "provenanceScore": 81, "checked": { "categories": { "ergonomics": "2026-11-01", "maintenance": "2026-11-01", "payments": "2026-11-01", "reliability": "2026-11-01", "schema": "2026-11-01", "security": "2026-11-01", "transparency": "2026-11-01" }, "last": "2026-11-01", "lastMoved": "2026-10-27", "oldest": "2026-11-01", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "npm install @incident-io/sdk", "http": "curl --request GET https://api.incident.io/v1/identity --header 'Authorization: Bearer \u003cYOUR_API_KEY\u003e'", "claudeCode": "claude mcp add incident-io --transport http https://mcp.incident.io/mcp" }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/incident-io" }, "area": "developer", "unitPrices": [ { "item": "Team plan, incident response", "unit": "seat-month", "usd": 19, "note": "$15 with the annual discount. On-call adds $10" }, { "item": "Pro plan, incident response", "unit": "seat-month", "usd": 25, "note": "billed yearly through sales. On-call adds $20" }, { "item": "On-call only", "unit": "seat-month", "usd": 20, "note": "sold through sales" } ], "provenance": { "legalEntity": "Pineapple Technology Ltd.", "domain": "incident.io", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://incident.io/legal/terms", "privacy": "https://incident.io/legal/privacy", "statusPage": "https://status.incident.io", "changelog": "https://docs.incident.io/api-reference/changelog", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The site footer and the legal pages carry the copyright of Pineapple Technology Ltd. The terms are governed by the laws of England and Wales. No company number was found on the pages read.", "The Terms and Conditions are effective 1 August 2026 and are served at incident.io/legal and incident.io/legal/terms. Orders before that date fall under legacy terms.", "The API answers at api.incident.io and the MCP server at mcp.incident.io.", "incident.io/.well-known/security.txt names security@incident.io and the vulnerability disclosure policy, and expires on 15 July 2027.", "rdap.org answered 404 for incident.io, so the registration date is not recorded." ], "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/incident-io.json", "live": { "slug": "incident-io", "probe": { "target": "https://mcp.incident.io/mcp", "method": "get", "lastAt": "2026-11-08T00:55:45.574467803Z", "lastOk": true, "lastStatus": 401, "lastMs": 35, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 99.99, "p50ms24h": 39, "p95ms24h": 110, "samples24h": 244, "samples30d": 7271, "days": [ { "date": "2026-10-09", "probes": 85, "ok": 85 }, { "date": "2026-10-10", "probes": 247, "ok": 247 }, { "date": "2026-10-11", "probes": 247, "ok": 247 }, { "date": "2026-10-12", "probes": 247, "ok": 247 }, { "date": "2026-10-13", "probes": 248, "ok": 248 }, { "date": "2026-10-14", "probes": 249, "ok": 249 }, { "date": "2026-10-15", "probes": 253, "ok": 252 }, { "date": "2026-10-16", "probes": 252, "ok": 252 }, { "date": "2026-10-17", "probes": 253, "ok": 253 }, { "date": "2026-10-18", "probes": 256, "ok": 256 }, { "date": "2026-10-19", "probes": 255, "ok": 255 }, { "date": "2026-10-20", "probes": 252, "ok": 252 }, { "date": "2026-10-21", "probes": 253, "ok": 253 }, { "date": "2026-10-22", "probes": 253, "ok": 253 }, { "date": "2026-10-23", "probes": 248, "ok": 248 }, { "date": "2026-10-24", "probes": 251, "ok": 251 }, { "date": "2026-10-25", "probes": 250, "ok": 250 }, { "date": "2026-10-26", "probes": 252, "ok": 252 }, { "date": "2026-10-27", "probes": 249, "ok": 249 }, { "date": "2026-10-28", "probes": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.incident.io", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:54:52.119189077Z" }, "versions": [ { "registry": "github", "name": "incident-io/sdk-ts", "version": "v2.46.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:34:25.067764437Z" }, { "registry": "npm", "name": "@incident-io/sdk", "version": "2.46.0", "seenAt": "2026-11-06T23:34:24.581393412Z" }, { "registry": "pypi", "name": "incident-io", "version": "2.44.0", "released": "2026-11-05", "seenAt": "2026-11-06T23:34:24.80182364Z" } ], "githubStars": 30, "npmWeekly": 2100, "pypiWeekly": 1300, "securityTxt": { "url": "https://incident.io/.well-known/security.txt", "state": "valid", "expires": "2027-07-15T12:00:00Z", "checkedAt": "2026-11-07T16:00:53.267941714Z" }, "llmsTxt": { "url": "https://docs.incident.io/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:32:44.783436068Z" }, "domain": { "domain": "incident.io", "checkedAt": "2026-11-01T14:07:48.376564034Z" }, "pages": [ { "url": "https://docs.incident.io/api-reference/changelog", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:06:38.016580237Z", "changedAt": "2026-11-06T13:29:01.036842834Z", "fingerprint": "2cec48253582" }, { "url": "https://incident.io/legal/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:11:27.373930639Z", "changedAt": "2026-11-03T07:51:42.100888416Z", "fingerprint": "757e9a065481" }, { "url": "https://incident.io/legal/terms", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:11:29.41240598Z", "changedAt": "2026-11-03T07:51:44.324802404Z", "fingerprint": "674cd6dffe94" } ], "github": { "repo": "incident-io/sdk-ts", "checkedAt": "2026-11-02T08:56:00.298728069Z", "stars": 30, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-01T23:36:41Z", "openIssues": 0, "openPRs": 1, "issuesOpened90d": 1, "issuesClosed90d": 1, "prsMerged90d": 2, "ci": { "branch": "master", "runs": 6, "success": 6, "failure": 0, "other": 0, "latest": "success", "latestAt": "2026-09-30T17:23:19Z" }, "replies": { "sampled": 1, "unanswered": 0, "medianDays": 0.2 } }, "updatedAt": "2026-11-08T00:55:45.574467803Z" } }, "edges": [ { "by": 40, "category": "transparency", "leads": "incident-io", "name": "Transparency \u0026 trust", "reasons": { "a": "robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.", "b": "Closed service under published Terms and Conditions effective 1 August 2026, with the SDKs, CLI and skills plugin under MIT (17). Privacy policy, DPA, sub-processor list and an AI data handling page are public. The terms limit training on customer content to the customer's own benefit. The security FAQ's statement that no data leaves Europe disagrees with a sub-processor list naming 17 processors in the United States, and retention is stated in general terms (20). Deprecated endpoints carry a removal date in their descriptions and the docs give integrators three months, but the changelog shows removals with no earlier entry (17). 20 sub-processors with locations and purposes, hosting regions named, 15 days' notice of changes in the DPA (18)." }, "scores": { "a": 37, "b": 77 } }, { "by": 35, "category": "reliability", "leads": "incident-io", "name": "Reliability", "reasons": { "a": "Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.", "b": "Scored as a hosted API. status.incident.io lists components with history, API and MCP among them (20). The feed, re-read on 1 November 2026, has four incidents in the 90 days from 3 August, each on one component. Opsgenie webhook delays on 3 August, alert listing in the public API and dashboard on 18 August until a rollback (no duration given), Microsoft Teams latency from 13:00 to 15:08 UTC on 20 August and Slack Enterprise Grid login errors for a subset of customers on 2 October. All partial, nothing since 2 October (20). Limits are published with numbers, 1,200 requests a minute per key and lower figures for eight endpoints (15). 429 carries `Retry-After`, the body recommends exponential backoff, and seven create calls require an `idempotency_key` (15). The SLA commits to 99.9 per cent a month on Pro and Enterprise (10). The API carries no beta label (10)." }, "scores": { "a": 55, "b": 90 } }, { "by": 30, "category": "payments", "leads": "cronitor-mcp", "name": "Payments \u0026 pricing", "reasons": { "a": "No machine payment protocol (0). Per-monitor and per-user prices public (20). Free plan for 5 monitors, no card mentioned (20). A person signs up or signs in through a browser (0). 0 + 20 + 20 + 0 = 40.", "b": "No x402, MPP or L402 (0). Plan prices per seat are public, Team at $19 and Pro at $25 a user a month, with no per-call price (10). The Basic plan is free, but the pricing page marks API, webhooks and MCP as not included, and the docs route trials through sales (0). A person signs up, pays and creates a key in the dashboard (0)." }, "scores": { "a": 40, "b": 10 } }, { "by": 28, "category": "maintenance", "leads": "incident-io", "name": "Maintenance \u0026 community", "reasons": { "a": "Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.", "b": "The API changelog's newest entry is 30 October 2026 (30). 53 dated entries between 3 August and 30 October 2026 (20). A public changelog, support by email and a Slack community, with reply times not checked (10). Seven official SDKs generated from the description file, TypeScript 2.40.0 and Python 2.39.0 both tagged 31 October 2026, and both READMEs say a schema check stops any break from shipping as a minor version (15). The SDK and CLI repositories have test workflows, and the two SDKs read were first tagged in September 2026 and reached a second major version within two weeks (8)." }, "scores": { "a": 55, "b": 83 } }, { "by": 8, "category": "schema", "leads": "incident-io", "name": "Schema \u0026 documentation", "reasons": { "a": "Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.", "b": "OpenAPI 3.0.3 description, public at api.incident.io/v1/openapiV3.json per the docs and read from docs.incident.io/openapi/latest.json, 284 operations and 777 schemas (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a description, but the median is 65 characters and few say when not to use a call. List incidents is the exception, with worked filter examples (12). 262 enums, required fields marked and two free-form objects in the whole file (13). 4,014 example values and thirteen error statuses on every operation, though the shared error example pairs an unrelated code and message (13). Versions sit in the path per resource and the changelog is generated from the description file (15)." }, "scores": { "a": 80, "b": 88 } }, { "by": 6, "category": "security", "leads": "incident-io", "name": "Security \u0026 auth", "reasons": { "a": "OAuth bounded by role with no scope choice, or scoped API keys (22 of 30). Read-only users get only read tools; write tools follow the role (14 of 20). The docs warn that event messages, command output and request bodies can hold customer data or secrets, and tell the agent to ask before expanding them; secrets are redacted (12 of 15). No audit log of MCP calls found (0). The security page covers encryption and relies on AWS's certifications; no security.txt (404) and no disclosure policy found (10 of 20). 22 + 14 + 12 + 0 + 10 = 58.", "b": "Organisation keys carry chosen permissions, 13 of 36 scopable to teams, can be rotated and are shown once. User keys take the owner's role and die with the account. 30 for that, less the checklist's 10 because alert event and heartbeat endpoints accept the alert source token in a `token` query parameter. The API key itself travels only in the header (20). A `viewer` permission gives read-only keys and the MCP status page tool only drafts, but no confirmation step guards destructive API calls (15). Alert payloads and incident text are untrusted content. The docs cover redaction of sensitive data, and no injection guidance for API consumers was found (4). Audit logs are Enterprise only, kept one year, exported or streamed, and API actions are attributed to the key (10). security.txt valid to July 2027, a disclosure policy with a five-working-day reply, SOC 2 Type I and II claimed, yearly penetration tests, no paid bounty (15)." }, "scores": { "a": 58, "b": 64 } } ], "facts": [ { "a": "MCP server", "b": "HTTP API", "name": "Kind" }, { "a": "Cronitor", "b": "Pineapple Technology Ltd. (incident.io)", "name": "Vendor" }, { "a": "https://cronitor.io/mcp", "b": "https://mcp.incident.io/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "not published", "b": "$19 per seat per month", "name": "Price for incidents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT", "name": "Licence" }, { "a": "71", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.cronitor/cronitor", "b": "not listed", "name": "MCP registry" }, { "a": "none", "b": "2026-10-31", "name": "Last release" }, { "a": "no document linked", "b": "2026-08-01", "name": "Terms last updated" }, { "a": "no document linked", "b": "2024-02-15", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "yes", "name": "Customer content may train models" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "1.3k npm/wk", "name": "Popularity" }, { "a": "none", "b": "3.5/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "incident.io API scores 68.9 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 6 of 7 scored categories. Cronitor MCP server leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Cronitor MCP server or incident.io API?" }, { "answer": "Cronitor MCP server uses an OAuth sign-in. incident.io API takes an API key or an OAuth sign-in.", "question": "Do Cronitor MCP server and incident.io API need an API key?" }, { "answer": "Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and incident.io API at https://mcp.incident.io/mcp.", "question": "Can an agent call Cronitor MCP server and incident.io API without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 10" ], "also": null, "goodFor": "Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.", "slug": "cronitor-mcp", "watchFor": "71 tools, a heavy context load" }, { "aheadOn": [ "Reliability, 90 against 55", "Schema \u0026 documentation, 88 against 80", "Security \u0026 auth, 64 against 58", "Maintenance \u0026 community, 83 against 55", "Transparency \u0026 trust, 77 against 37" ], "also": null, "goodFor": "Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.", "slug": "incident-io", "watchFor": "The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month" } ], "history": { "cronitor-mcp": null, "incident-io": [ { "causes": [ "method" ], "date": "2026-10-27", "delta": 0, "from": 68.9, "fromGrade": "B", "to": 68.9, "toGrade": "B" } ] }, "job": { "capability": "observability.incidents", "name": "Incidents" }, "others": [ { "json": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.json", "title": "Axiom MCP Server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-incident-io.json", "title": "Axiom MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/axiom-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.json", "title": "Better Stack vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io.json", "title": "Better Stack vs incident.io API", "url": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.json", "title": "Causely MCP server vs Cronitor MCP server", "url": "https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp" }, { "json": "https://www.anchorterminal.com/compare/causely-vs-incident-io.json", "title": "Causely MCP server vs incident.io API", "url": "https://www.anchorterminal.com/compare/causely-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json", "title": "Cronitor MCP server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.json", "title": "Cronitor MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json", "title": "Cronitor MCP server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.json", "title": "Cronitor MCP server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json", "title": "Cronitor MCP server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.json", "title": "Datadog MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.json", "title": "Grafana MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic.json", "title": "incident.io API vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.json", "title": "incident.io API vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.json", "title": "incident.io API vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.json", "title": "Cronitor MCP server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp" } ], "panel": null, "scores": [ { "by": 35, "cronitor-mcp": 55, "edge": "incident-io", "incident-io": 90, "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 8, "cronitor-mcp": 80, "edge": "incident-io", "incident-io": 88, "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 2, "cronitor-mcp": 73, "edge": "incident-io", "incident-io": 75, "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 6, "cronitor-mcp": 58, "edge": "incident-io", "incident-io": 64, "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 30, "cronitor-mcp": 40, "edge": "cronitor-mcp", "incident-io": 10, "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 28, "cronitor-mcp": 55, "edge": "incident-io", "incident-io": 83, "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 40, "cronitor-mcp": 37, "edge": "incident-io", "incident-io": 77, "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "incident.io API scores 68.9 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 6 of 7 scored categories. Cronitor MCP server leads on payments \u0026 pricing. Both do incidents.", "tasks": null, "tutorials": [], "verdicts": { "cronitor-mcp": "Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.", "incident-io": "The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io", "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.min.md" }, "markdown": "incident.io API scores 68.9 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 6 of 7 scored categories. Cronitor MCP server leads on payments \u0026 pricing. Both do incidents.\n\n- Cronitor MCP server: grade C, 59.1/100, rank #718 of 1510. Markdown https://www.anchorterminal.com/tools/cronitor-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json\n- incident.io API: grade B, 68.9/100, rank #266 of 1510. Markdown https://www.anchorterminal.com/tools/incident-io.md · JSON https://www.anchorterminal.com/api/v1/tools/incident-io.json\n- Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md\n- All 59 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\n\n### Cronitor MCP server (C)\n\nGood for: Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 10\n\nWatch for: 71 tools, a heavy context load\n\n### incident.io API (B)\n\nGood for: Agents that declare and update incidents, page people, read on-call schedules and post status page incidents in an organisation that already pays for incident.io.\n\nAhead on:\n- Reliability, 90 against 55\n- Schema \u0026 documentation, 88 against 80\n- Security \u0026 auth, 64 against 58\n- Maintenance \u0026 community, 83 against 55\n- Transparency \u0026 trust, 77 against 37\n\nWatch for: The pricing page marks API, webhooks and MCP as not included in the free Basic plan. Team starts at $19 per user a month\n\n\n## Why the edge\n\n### Transparency \u0026 trust: incident.io API +40\n\n- Cronitor MCP server (37): robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.\n- incident.io API (77): Closed service under published Terms and Conditions effective 1 August 2026, with the SDKs, CLI and skills plugin under MIT (17). Privacy policy, DPA, sub-processor list and an AI data handling page are public. The terms limit training on customer content to the customer's own benefit. The security FAQ's statement that no data leaves Europe disagrees with a sub-processor list naming 17 processors in the United States, and retention is stated in general terms (20). Deprecated endpoints carry a removal date in their descriptions and the docs give integrators three months, but the changelog shows removals with no earlier entry (17). 20 sub-processors with locations and purposes, hosting regions named, 15 days' notice of changes in the DPA (18).\n\n### Reliability: incident.io API +35\n\n- Cronitor MCP server (55): Status page at status.cronitor.io with components for the APIs and telemetry regions (20). No history was readable (history.rss 404, uptime 'No data available') (5). Rate limits are returned with limit and window in the error data, but no numbers are published (5 of 15). Rate-limit errors carry retry_after_seconds, bulk deletes validate every key first, and the docs say which repeated calls are safe (15). No SLA found (0). Not labelled beta (10). 20 + 5 + 5 + 15 + 0 + 10 = 55.\n- incident.io API (90): Scored as a hosted API. status.incident.io lists components with history, API and MCP among them (20). The feed, re-read on 1 November 2026, has four incidents in the 90 days from 3 August, each on one component. Opsgenie webhook delays on 3 August, alert listing in the public API and dashboard on 18 August until a rollback (no duration given), Microsoft Teams latency from 13:00 to 15:08 UTC on 20 August and Slack Enterprise Grid login errors for a subset of customers on 2 October. All partial, nothing since 2 October (20). Limits are published with numbers, 1,200 requests a minute per key and lower figures for eight endpoints (15). 429 carries `Retry-After`, the body recommends exponential backoff, and seven create calls require an `idempotency_key` (15). The SLA commits to 99.9 per cent a month on Pro and Enterprise (10). The API carries no beta label (10).\n\n### Payments \u0026 pricing: Cronitor MCP server +30\n\n- Cronitor MCP server (40): No machine payment protocol (0). Per-monitor and per-user prices public (20). Free plan for 5 monitors, no card mentioned (20). A person signs up or signs in through a browser (0). 0 + 20 + 20 + 0 = 40.\n- incident.io API (10): No x402, MPP or L402 (0). Plan prices per seat are public, Team at $19 and Pro at $25 a user a month, with no per-call price (10). The Basic plan is free, but the pricing page marks API, webhooks and MCP as not included, and the docs route trials through sales (0). A person signs up, pays and creates a key in the dashboard (0).\n\n### Maintenance \u0026 community: incident.io API +28\n\n- Cronitor MCP server (55): Registry entry io.cronitor/cronitor updated 3 November 2026 (30). No dated changelog found to count (0). Support page and docs; no public changelog (10 of 15). Official registry entry under its own namespace, and official SDKs (15). No package to read (0). 30 + 0 + 10 + 15 + 0 = 55. Registry presence read from Anchor Terminal's own daily import of the official MCP registry (/api/v1/registry.json, 6 November 2026), not the registry's API.\n- incident.io API (83): The API changelog's newest entry is 30 October 2026 (30). 53 dated entries between 3 August and 30 October 2026 (20). A public changelog, support by email and a Slack community, with reply times not checked (10). Seven official SDKs generated from the description file, TypeScript 2.40.0 and Python 2.39.0 both tagged 31 October 2026, and both READMEs say a schema check stops any break from shipping as a minor version (15). The SDK and CLI repositories have test workflows, and the two SDKs read were first tagged in September 2026 and reached a second major version within two weeks (8).\n\n### Schema \u0026 documentation: incident.io API +8\n\n- Cronitor MCP server (80): Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.\n- incident.io API (88): OpenAPI 3.0.3 description, public at api.incident.io/v1/openapiV3.json per the docs and read from docs.incident.io/openapi/latest.json, 284 operations and 777 schemas (25). llms.txt and a Markdown twin of every docs page (10). Every operation has a description, but the median is 65 characters and few say when not to use a call. List incidents is the exception, with worked filter examples (12). 262 enums, required fields marked and two free-form objects in the whole file (13). 4,014 example values and thirteen error statuses on every operation, though the shared error example pairs an unrelated code and message (13). Versions sit in the path per resource and the changelog is generated from the description file (15).\n\n### Security \u0026 auth: incident.io API +6\n\n- Cronitor MCP server (58): OAuth bounded by role with no scope choice, or scoped API keys (22 of 30). Read-only users get only read tools; write tools follow the role (14 of 20). The docs warn that event messages, command output and request bodies can hold customer data or secrets, and tell the agent to ask before expanding them; secrets are redacted (12 of 15). No audit log of MCP calls found (0). The security page covers encryption and relies on AWS's certifications; no security.txt (404) and no disclosure policy found (10 of 20). 22 + 14 + 12 + 0 + 10 = 58.\n- incident.io API (64): Organisation keys carry chosen permissions, 13 of 36 scopable to teams, can be rotated and are shown once. User keys take the owner's role and die with the account. 30 for that, less the checklist's 10 because alert event and heartbeat endpoints accept the alert source token in a `token` query parameter. The API key itself travels only in the header (20). A `viewer` permission gives read-only keys and the MCP status page tool only drafts, but no confirmation step guards destructive API calls (15). Alert payloads and incident text are untrusted content. The docs cover redaction of sensitive data, and no injection guidance for API consumers was found (4). Audit logs are Enterprise only, kept one year, exported or streamed, and API actions are attributed to the key (10). security.txt valid to July 2027, a disclosure policy with a five-working-day reply, SOC 2 Type I and II claimed, yearly penetration tests, no paid bounty (15).\n\n## Score by category\n\n| Category | Weight | Cronitor MCP server | incident.io API | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 90 | incident.io API +35 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 88 | incident.io API +8 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 75 | incident.io API +2 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 64 | incident.io API +6 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 10 | Cronitor MCP server +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 55 | 83 | incident.io API +28 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 77 | incident.io API +40 |\n| Negative events | ≤15 | 0 | -2 | |\n| **Total** | | **59.1 · C** | **68.9 · B** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | incident.io API |\n| --- | --- | --- |\n| Kind | MCP server | HTTP API |\n| Vendor | Cronitor | Pineapple Technology Ltd. (incident.io) |\n| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.incident.io/mcp` |\n| Transports | Streamable HTTP | HTTP |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Paid |\n| Price for incidents | not published | $19 per seat per month |\n| x402 | no | no |\n| Licence | none | Proprietary service under incident.io's Terms and Conditions. The SDKs, the `inc` CLI and the skills plugin on GitHub are MIT |\n| Tools exposed | 71 | none |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.cronitor/cronitor` | not listed |\n| Last release | none | 2026-10-31 |\n| Terms last updated | no document linked | 2026-08-01 |\n| Privacy policy last updated | no document linked | 2024-02-15 |\n| Customer content may train models | not read yet | yes |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | yes |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 1.3k npm/wk |\n| Agent reviews | none | 3.5/5 (4) |\n\n## How the scores have moved\n\n### Cronitor MCP server\n\nNo score change since it was listed.\n\n### incident.io API\n\n- no change on 27 October 2026: checklist\n\n## Verdicts\n\n**Cronitor MCP server.** Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.\n\n**incident.io API.** The REST API has a public OpenAPI description with 284 operations, numeric rate limits, `Retry-After` on 429 and required idempotency keys on seven create calls. API and MCP access need the Team plan or higher, so the free Basic plan cannot be used by an agent, and audit logs are Enterprise only.\n\n## Before you call either\n\n### Cronitor MCP server\n\n1. Start with list_monitors and list_issues in summary mode\n2. Ask the user before expanding event messages, command output or request bodies\n3. On a rate-limit error, wait retry_after_seconds\n4. Over the plan's monitor limit, new monitors are saved but disabled\n\n### incident.io API\n\n1. Send `Authorization: Bearer \u003ckey\u003e` to https://api.incident.io and call `GET /v1/identity` first to read the key's roles\n2. Send a fresh `idempotency_key` with every create call for incidents, incident updates, timeline items, escalations and status page incidents. A repeated key returns the first result\n3. Page with `page_size` and `after` until no cursor comes back. Do not stop at a short or empty page\n4. Keep `GET /v2/incidents` under 60 requests a minute and wait the seconds in `Retry-After` on 429\n5. Incident creation is limited to 10 an hour per key when a Slack or Teams channel is created, 300 an hour otherwise\n\n## Questions\n\n### Which is better for AI agents, Cronitor MCP server or incident.io API?\n\nincident.io API scores 68.9 (B) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 6 of 7 scored categories. Cronitor MCP server leads on payments \u0026 pricing.\n\n### Do Cronitor MCP server and incident.io API need an API key?\n\nCronitor MCP server uses an OAuth sign-in. incident.io API takes an API key or an OAuth sign-in.\n\n### Can an agent call Cronitor MCP server and incident.io API without installing anything?\n\nYes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and incident.io API at https://mcp.incident.io/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cronitor-mcp\", \"b\": \"incident-io\"}`. From a terminal: `anchor compare cronitor-mcp incident-io`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/incident-io.json\n\n## Other comparisons with Cronitor MCP server or incident.io API\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)\n- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md)\n- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)\n- [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md)\n- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)\n- [Causely MCP server vs incident.io API](https://www.anchorterminal.com/compare/causely-vs-incident-io.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md)\n- [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md)\n- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)\n- [Datadog MCP Server vs incident.io API](https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md)\n- [Grafana MCP Server vs incident.io API](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-incident-io.md)\n- [incident.io API vs New Relic MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-new-relic.md)\n- [incident.io API vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-pagerduty-mcp.md)\n- [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md)\n- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)\n", "meta": { "attribution": "Anchor Terminal (https://www.anchorterminal.com)", "attributionRequired": true, "credit": "CC BY 4.0, credit Anchor Terminal and link the page or API address you took it from (https://www.anchorterminal.com/terms/#data)", "docs": "https://www.anchorterminal.com/docs/", "generatedAt": "2026-11-08", "license": "CC-BY-4.0", "method": "https://www.anchorterminal.com/benchmark/", "methodology": "0.7", "openapi": "https://www.anchorterminal.com/openapi.json", "preview": false, "run": "2026-10-01", "runLabel": "October 2026 research run", "terms": "https://www.anchorterminal.com/terms/#data" }, "page": { "breadcrumbs": [ { "name": "Home", "url": "https://www.anchorterminal.com/" }, { "name": "Compare", "url": "https://www.anchorterminal.com/compare/" }, { "name": "Cronitor MCP server vs incident.io API", "url": "" } ], "description": "incident.io scores 68.9 (B) to Cronitor's 59.1 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cronitor MCP server C 59.1", "incident.io API B 68.9", "scores" ], "h1": "Cronitor MCP server vs incident.io API", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cronitor-mcp-vs-incident-io", "published": "2026-10-01", "section": "tools", "title": "Cronitor vs incident.io for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io" }, "tokens": { "markdown": 4200, "slim": 2580 }, "version": 1 }