{ "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": "Cronitor MCP server scores 59.1 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "rootly-mcp", "name": "Rootly MCP Server", "vendor": "Rootly Inc.", "vendorUrl": "https://rootly.com", "kind": "mcp", "category": "observability", "summary": "Rootly's MCP server for its incident management and on-call platform. Agents list, search and update incidents, alerts, schedules and escalation policies through a hosted endpoint at mcp.rootly.com with OAuth or an API key, or run the Apache-2.0 package themselves.", "url": "https://www.anchorterminal.com/tools/rootly-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/rootly-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/rootly-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/rootly-mcp.json", "dns": "rootly-mcp.grade.anchorterminal.com", "repo": "https://github.com/rootlyhq/rootly-mcp-server", "license": "Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use", "transports": [ "streamable-http", "sse", "stdio" ], "remoteUrl": "https://mcp.rootly.com/mcp", "packages": [ { "registry": "pypi", "name": "rootly-mcp-server" } ], "auth": "mixed", "authNotes": "The hosted server takes an OAuth 2 login or a Rootly API key as a bearer token. OAuth clients can register themselves (RFC 7591), public clients must use PKCE with S256, access tokens last one hour and refresh tokens rotate. The MCP resource metadata advertises a single `all` scope. API keys are created by a person under Organisation Settings and are global with a chosen role, team-wide or personal. A local server reads `ROOTLY_API_TOKEN`.", "pricing": "paid", "pricingNotes": "No separate charge for MCP. It is included in the Essentials plan at $20 per product per user a month, where incident response and on-call are separate products, and in Enterprise, which is by quote. No free tier. Self-serve sign-up starts a trial of about two weeks, and whether it needs a card wasn't established (https://rootly.com/pricing, checked 2026-10-09).", "priceSummary": "$20 / seat-mo", "where": "both", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the repository, the MCP docs or the pricing page (checked 2026-10-09).", "endpoints": [] }, "toolCount": 218, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-10-09" }, "docsUrl": "https://docs.rootly.com/integrations/mcp-server", "llmsTxt": "https://rootly.com/llms.txt", "openapi": "https://rootly.com/swagger/v1/swagger.json", "registryName": "com.rootly/mcp-server", "capabilities": [ "observability.incidents", "work.oncall" ], "tags": [ "official", "hosted", "open-source", "mcp", "oauth", "api-key", "incidents", "on-call", "python", "code-mode", "status-page", "soc2" ], "lastRelease": "2026-10-31", "graded": true, "anchor": { "graded": true, "score": 53.8, "grade": "D", "agentReady": false, "rank": 938, "ranked": true, "rankOf": 1510, "categoryRank": 9, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 48, "schema": 78, "security": 65, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -9, "negativeNotes": [ "Between 23 and 29 September 2026 two changes to hosted telemetry broke tool calls. Removing an injected `context` parameter failed fifteen curated tools for clients with cached tool lists, and a PostHog analytics layer failed every hosted tool call until it was switched off. Both are fixed and described in the 2.3.21 changelog, so 3 points (https://github.com/rootlyhq/rootly-mcp-server/blob/main/CHANGELOG.md)", "Released fixes of the server's own described flaws with no advisory. 2.3.22 (21 October 2026) stopped MCP responses exposing heartbeat ping secrets and email addresses and meeting credentials embedded in attach-alert responses, and 2.4.0 (31 October 2026) restored the per-`execute` tool call limit that let one Code Mode script make unbounded API calls. OSV lists no advisory for rootly-mcp-server, so one folded 3 points (https://github.com/rootlyhq/rootly-mcp-server/blob/main/CHANGELOG.md)", "A fix in no release. Commit 4875057 on main (2 November 2026) says `api_token`, `auth_token`, `oauth_token` and similar keys and their values reached AgentCat and Sentry telemetry unscrubbed. No tag carries it on 4 November, so 3 points until a release does (https://github.com/rootlyhq/rootly-mcp-server/commit/4875057)" ], "verdict": "The server is open source under Apache-2.0, ships dated releases every few weeks, and has a slim profile and a Code Mode endpoint that cut the list of about 218 tools. Hosted connections expose write tools by default. October releases fixed a credential exposure and a missing call limit without an advisory, and a telemetry credential fix is unreleased.", "bestFor": "Incident and on-call agents in teams that already run Rootly.", "strengths": [ "Apache-2.0 source for the same server Rootly hosts, with seven dated releases between 10 August and 31 October 2026", "A slim profile of about 70 tools and a Code Mode endpoint with five meta-tools reduce the full list of about 218", "Every tool sets `readOnlyHint`, `destructiveHint` and `openWorldHint` since 2.3.19 of 9 September 2026", "OAuth with dynamic client registration, PKCE, one-hour access tokens, rotating refresh tokens and a revocation endpoint", "Delete operations are off by default, and API key, user, role and webhook endpoints are excluded from the tool list" ], "weaknesses": [ "Hosted connections expose write tools by default, and the docs describe the read-only switch only for servers the owner runs", "The 2.3.21 changelog records two hosted regressions in late September 2026, one failing fifteen tools for clients with cached schemas and one failing every tool call", "2.3.22 and 2.4.0 fixed exposed heartbeat and meeting credentials and an unbounded Code Mode call budget with no advisory", "Hosted telemetry records tool arguments and responses through AgentCat per the README. AgentCat isn't named on Rootly's subprocessor list", "status.rootly.com's incident history rests on the 9 October check, when it answered with a bot check", "Rootly's Terms of Use bar crawling or scraping the Services by manual or automated means. This matters before any probe is run", "A fix stopping API tokens reaching AgentCat and Sentry telemetry is on main since 2 November 2026 but in no release" ], "agentNotes": [ "Connect to `https://mcp.rootly.com/mcp-codemode` or add `?tool_profile=slim` to `/mcp`. The default endpoint loads about 218 tool definitions", "Connect Code Mode in place of the classic endpoint, not beside it. The docs say models skip `execute` when both are present", "Use a Global API key for `get_oncall_handoff_summary` and `get_oncall_shift_metrics`. Team and personal keys return partial results", "Refetch the tool list after a server release. Curated tools reject undeclared arguments, which failed calls from cached schemas in September 2026", "Treat a 404 from a generated tool as a possible plan limit or missing parent record, and read the hint in the response", "Move off `https://mcp.rootly.com/sse` before 20 November 2026, when Rootly removes the SSE transport" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 4, "avgRating": 2.5, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "D", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 53.8 } ], "editorialScores": { "ergonomics": 77, "maintenance": 81, "payments": 20, "reliability": 48, "schema": 78, "security": 65, "transparency": 65 }, "provenanceScore": 96, "checked": { "categories": { "ergonomics": "2026-11-04", "maintenance": "2026-11-04", "payments": "2026-11-04", "reliability": "2026-11-04", "schema": "2026-11-04", "security": "2026-11-04", "transparency": "2026-11-04" }, "last": "2026-11-04", "lastMoved": "2026-11-04", "oldest": "2026-11-04", "stale": false, "staleAfterDays": 90 } }, "connect": { "install": "uvx --from rootly-mcp-server rootly-mcp-server", "claudeCode": "claude mcp add --transport http rootly https://mcp.rootly.com/mcp", "config": { "mcpServers": { "rootly": { "url": "https://mcp.rootly.com/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.incidents", "tool": "https://letme.dev/rootly-mcp" }, "area": "developer", "unitPrices": [ { "item": "Essentials plan, incident response", "unit": "seat-month", "usd": 20, "note": "MCP, API and status pages included" }, { "item": "Essentials plan, on-call", "unit": "seat-month", "usd": 20, "note": "added to incident response, $40 for both" } ], "provenance": { "legalEntity": "Rootly Inc.", "domain": "rootly.com", "domainRegistered": "2006-05-27", "endpointOnVendorDomain": true, "terms": "https://rootly.com/legal/terms", "privacy": "https://rootly.com/legal/privacy", "statusPage": "https://status.rootly.com", "changelog": "https://github.com/rootlyhq/rootly-mcp-server/blob/main/CHANGELOG.md", "securityTxt": "valid", "checked": "2026-10-09", "notes": [ "The Terms of Use (last updated July 2026) are a contract with ROOTLY INC., 1390 Market Street, San Francisco, and cover its websites, products, services and applications. The privacy policy (October 2026) writes the name as Rootly, Inc.", "The hosted MCP endpoint is mcp.rootly.com and the REST API is api.rootly.com, both on the vendor's domain.", "rootly.com/.well-known/security.txt names security@rootly.com and expires on 1 September 2027.", "status.rootly.com is linked from the site and llms.txt. It answered our reader with a bot check and was unread.", "RDAP for rootly.com gives a registration date of 2006-05-27.", "The subprocessor page refers to a U.S. Data Processing Addendum of September 2026, which we didn't find published." ], "score": 96 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/rootly-mcp.json", "live": { "slug": "rootly-mcp", "probe": { "target": "https://mcp.rootly.com/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T00:56:02.165442372Z", "lastOk": true, "lastStatus": 401, "lastMs": 199, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 140, "p95ms24h": 372, "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": 253 }, { "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": 250, "ok": 250 }, { "date": "2026-10-29", "probes": 249, "ok": 249 }, { "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.rootly.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:55:31.884160715Z" }, "versions": [ { "registry": "github", "name": "rootlyhq/rootly-mcp-server", "version": "v2.4.0", "released": "2026-10-31", "seenAt": "2026-11-07T00:02:23.978041419Z" }, { "registry": "mcp-registry", "name": "com.rootly/mcp-server", "version": "2.2.4", "seenAt": "2026-11-07T18:16:28.95801333Z" }, { "registry": "pypi", "name": "rootly-mcp-server", "version": "2.4.0", "released": "2026-10-31", "seenAt": "2026-11-07T00:02:23.7346079Z" } ], "githubStars": 45, "pypiWeekly": 1248, "securityTxt": { "url": "https://rootly.com/.well-known/security.txt", "state": "valid", "expires": "2027-09-01T00:00:00.000Z", "checkedAt": "2026-11-07T16:00:10.305059413Z" }, "llmsTxt": { "url": "https://rootly.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:50.622100649Z" }, "domain": { "domain": "rootly.com", "registered": "2006-05-27", "source": "https://rdap.verisign.com/com/v1/domain/rootly.com", "checkedAt": "2026-11-01T14:15:39.541548429Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/rootlyhq/rootly-mcp-server/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:23:18.842763686Z", "changedAt": "2026-11-01T06:54:45.034758757Z", "fingerprint": "e2dcb07f9103" }, { "url": "https://rootly.com/pricing", "kind": "pricing", "status": 200, "checkedAt": "2026-11-07T14:18:50.465655451Z", "changedAt": "2026-11-07T14:18:50.465655451Z", "fingerprint": "9431e9da4ae2" }, { "url": "https://rootly.com/legal/privacy", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:18:45.900465018Z", "changedAt": "2026-11-07T14:18:45.900465018Z", "fingerprint": "f15722b7e065" }, { "url": "https://rootly.com/legal/terms", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:18:48.310306945Z", "changedAt": "2026-11-07T14:18:48.310306945Z", "fingerprint": "b6b88dc5a8a0" } ], "mcpTools": { "url": "https://mcp.rootly.com/mcp", "checkedAt": "2026-11-07T01:47:29.825646589Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-10-09T21:40:55.523633877Z" }, "github": { "repo": "rootlyhq/rootly-mcp-server", "checkedAt": "2026-11-02T09:22:31.826134781Z", "stars": 45, "archived": false, "issuesEnabled": true, "pushedAt": "2026-11-02T08:19:56Z", "openIssues": 0, "openPRs": 1, "issuesOpened90d": 1, "issuesClosed90d": 3, "prsMerged90d": 102, "ci": { "branch": "main", "runs": 50, "success": 48, "failure": 0, "other": 2, "latest": "success", "latestAt": "2026-11-02T08:28:03Z" }, "replies": { "sampled": 8, "unanswered": 0, "medianDays": 34 } }, "updatedAt": "2026-11-08T00:56:02.165442372Z" } }, "edges": [ { "by": 44, "category": "transparency", "leads": "rootly-mcp", "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": "The server is Apache-2.0 and the hosted service runs under Rootly's Terms of Use of July 2026 (27). A privacy policy of October 2026, a subprocessor list and AI data pages are public, and retention is stated only in general terms. The README says hosted telemetry records tool arguments, responses, timing and errors through AgentCat with redaction hooks. AgentCat isn't on the subprocessor list and the MCP docs page doesn't mention telemetry (15). No deprecation policy was found. camelCase tool names stay callable as hidden aliases with no removal date, and the terms say notice of changes isn't always practical (8). The subprocessor list names about 30 processors with purpose, data and location, nearly all in the United States (15)." }, "scores": { "a": 37, "b": 81 } }, { "by": 26, "category": "maintenance", "leads": "rootly-mcp", "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": "v2.4.0 was tagged on 31 October 2026, four days before this check (30). Dated releases from 6 August to 4 November 2026 are 2.3.17 (10 August), 2.3.18 (29 August), 2.3.19 (9 September), 2.3.20 (14 September), 2.3.21 (5 October), 2.3.22 (21 October) and 2.4.0 (31 October) (20). The commit log shows pull requests merged through 3 November. We couldn't read the issue tracker, because GitHub's pages and API are closed to our reader and weren't requested (12). The official MCP registry lists `com.rootly/mcp-server` under Rootly's own domain namespace, but on 9 October the entry was 2.2.4 from 18 February 2026 and named only the SSE endpoint. The repository's server.json is now 2.4.0, with no workflow that publishes it (10). CI runs lint, two type checkers, unit and integration tests on Python 3.12 and 3.13 and a container protocol test, with a lockfile check, Dependabot and a dependency review workflow (9)." }, "scores": { "a": 55, "b": 81 } }, { "by": 20, "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 are public. Essentials is $20 per product per user a month, with MCP and API access included, and Enterprise is by quote. No per-call price (10). No free tier. Self-serve sign-up starts a trial of about two weeks per the pricing page. The sign-up page answered with a bot check, so whether a card is needed wasn't established, and the line takes half marks (10). A person signs up in a browser and either logs in through OAuth or creates an API key (0). The package is free to run but needs a Rootly account, so the self-hosted rule doesn't apply." }, "scores": { "a": 40, "b": 20 } }, { "by": 7, "category": "reliability", "leads": "cronitor-mcp", "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 MCP server, the path the docs recommend. status.rootly.com is linked from the site and llms.txt. On 9 October it answered our reader with a bot check, so its components (15) and incident history (5) were unread. Rootly's Terms of Use bar crawling or scraping the Services, and this run pauses such hosts pending a ruling, so the 9 October readings are kept. The REST API behind the tools allows 3,000 read calls and 3,000 write calls a minute per API key, and 50 alert creations a minute. No separate limit for mcp.rootly.com was found (12). A 429 returns a JSON error with `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Used` and `X-RateLimit-Reset` headers. No `Retry-After`, backoff guidance or idempotency keys were found (8). The pricing table lists \"99.99 % Reliability\" for on-call, and no SLA document was found (0). The hosted `/mcp` and `/mcp-codemode` endpoints carry no beta label. The README calls Code Mode experimental while the docs recommend it (8)." }, "scores": { "a": 55, "b": 48 } }, { "by": 7, "category": "security", "leads": "rootly-mcp", "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": "OAuth 2 with dynamic client registration, PKCE with S256, one-hour access tokens, rotating refresh tokens, a revocation endpoint and `:read` and `:write` scopes per resource. The MCP server's resource metadata advertises a single `all` scope since 2.3.13, so MCP logins aren't narrowed by scope. API keys are global with a chosen role, team or personal, sent in the `Authorization` header (26). Delete operations are off by default and API key, user, role and webhook endpoints are excluded. Write tools are on by default for hosted connections, the documented read-only switch applies to servers the owner runs, and no confirmation step was found (11). Incident text, alert payloads and meeting transcripts are untrusted content, and no injection guidance was found (3). `list_audits` reads Rootly's audit log, which the pricing page lists under Enterprise (9). security.txt valid to 1 September 2027, a disclosure policy with safe harbour and response times, no paid bounty, SOC 2 Type II stated with the report on request, and dependency advisories recorded in the changelog. The server's own fixes in 2.3.22 and 2.4.0 carry no advisory, and OSV holds none for the package (16)." }, "scores": { "a": 58, "b": 65 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Cronitor", "b": "Rootly Inc.", "name": "Vendor" }, { "a": "https://cronitor.io/mcp", "b": "https://mcp.rootly.com/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, SSE (legacy), stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Paid", "name": "Pricing" }, { "a": "not published", "b": "$20 per seat per month", "name": "Price for incidents" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use", "name": "Licence" }, { "a": "71", "b": "218", "name": "Tools exposed" }, { "a": "no", "b": "no", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.cronitor/cronitor", "b": "com.rootly/mcp-server", "name": "MCP registry" }, { "a": "none", "b": "2026-10-31", "name": "Last release" }, { "a": "no document linked", "b": "2026-07-01", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-10-01", "name": "Privacy policy last updated" }, { "a": "not read yet", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not read yet", "b": "yes", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "yes", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "yes", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "2.5/5 (4)", "name": "Agent reviews" } ], "faq": [ { "answer": "Cronitor MCP server scores 59.1 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Cronitor MCP server or Rootly MCP Server?" }, { "answer": "Cronitor MCP server uses an OAuth sign-in. Rootly MCP Server takes an API key or an OAuth sign-in.", "question": "Do Cronitor MCP server and Rootly MCP Server need an API key?" }, { "answer": "Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and Rootly MCP Server at https://mcp.rootly.com/mcp.", "question": "Can an agent call Cronitor MCP server and Rootly MCP Server without installing anything?" }, { "answer": "No open-source release is listed for Cronitor MCP server. Rootly MCP Server is open source (Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use).", "question": "Are Cronitor MCP server and Rootly MCP Server open source?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 55 against 48", "Payments \u0026 pricing, 40 against 20" ], "also": [ "No incidents deducted, where Rootly MCP Server loses 9 points for them" ], "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": [ "Security \u0026 auth, 65 against 58", "Maintenance \u0026 community, 81 against 55", "Transparency \u0026 trust, 81 against 37" ], "also": [ "Runs on your own machine", "Open source" ], "goodFor": "Incident and on-call agents in teams that already run Rootly.", "slug": "rootly-mcp", "watchFor": "Hosted connections expose write tools by default, and the docs describe the read-only switch only for servers the owner runs" } ], "history": { "cronitor-mcp": null, "rootly-mcp": [ { "causes": [ "security" ], "date": "2026-11-04", "delta": -6, "from": 59.8, "fromGrade": "C", "to": 53.8, "toGrade": "D" }, { "causes": [ "method" ], "date": "2026-10-28", "delta": 0.1, "from": 59.7, "fromGrade": "C", "to": 59.8, "toGrade": "C" } ] }, "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-rootly-mcp.json", "title": "Axiom MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp" }, { "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-rootly-mcp.json", "title": "Better Stack vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp" }, { "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-rootly-mcp.json", "title": "Causely MCP server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/causely-vs-rootly-mcp" }, { "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-incident-io.json", "title": "Cronitor MCP server vs incident.io API", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io" }, { "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/datadog-mcp-vs-rootly-mcp.json", "title": "Datadog MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.json", "title": "Grafana MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-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/new-relic-vs-rootly-mcp.json", "title": "New Relic MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/pagerduty-mcp-vs-rootly-mcp.json", "title": "PagerDuty MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/pagerduty-mcp-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": 7, "cronitor-mcp": 55, "edge": "cronitor-mcp", "key": "reliability", "name": "Reliability", "rootly-mcp": 48, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 2, "cronitor-mcp": 80, "edge": "cronitor-mcp", "key": "schema", "name": "Schema \u0026 documentation", "rootly-mcp": 78, "weight": 13 }, { "by": 4, "cronitor-mcp": 73, "edge": "rootly-mcp", "key": "ergonomics", "name": "Agent ergonomics", "rootly-mcp": 77, "weight": 13 }, { "by": 7, "cronitor-mcp": 58, "edge": "rootly-mcp", "key": "security", "name": "Security \u0026 auth", "rootly-mcp": 65, "weight": 14 }, { "by": 20, "cronitor-mcp": 40, "edge": "cronitor-mcp", "key": "payments", "name": "Payments \u0026 pricing", "rootly-mcp": 20, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 26, "cronitor-mcp": 55, "edge": "rootly-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "rootly-mcp": 81, "weight": 7 }, { "by": 44, "cronitor-mcp": 37, "edge": "rootly-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "rootly-mcp": 81, "weight": 7 } ], "summary": "Cronitor MCP server scores 59.1 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. 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.", "rootly-mcp": "The server is open source under Apache-2.0, ships dated releases every few weeks, and has a slim profile and a Code Mode endpoint that cut the list of about 218 tools. Hosted connections expose write tools by default. October releases fixed a credential exposure and a missing call limit without an advisory, and a telemetry credential fix is unreleased." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp", "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.min.md" }, "markdown": "Cronitor MCP server scores 59.1 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust. 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- Rootly MCP Server: grade D, 53.8/100, rank #938 of 1510. Markdown https://www.anchorterminal.com/tools/rootly-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/rootly-mcp.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- Reliability, 55 against 48\n- Payments \u0026 pricing, 40 against 20\n\nAlso in its favour:\n- No incidents deducted, where Rootly MCP Server loses 9 points for them\n\nWatch for: 71 tools, a heavy context load\n\n### Rootly MCP Server (D)\n\nGood for: Incident and on-call agents in teams that already run Rootly.\n\nAhead on:\n- Security \u0026 auth, 65 against 58\n- Maintenance \u0026 community, 81 against 55\n- Transparency \u0026 trust, 81 against 37\n\nAlso in its favour:\n- Runs on your own machine\n- Open source\n\nWatch for: Hosted connections expose write tools by default, and the docs describe the read-only switch only for servers the owner runs\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Rootly MCP Server +44\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- Rootly MCP Server (81): The server is Apache-2.0 and the hosted service runs under Rootly's Terms of Use of July 2026 (27). A privacy policy of October 2026, a subprocessor list and AI data pages are public, and retention is stated only in general terms. The README says hosted telemetry records tool arguments, responses, timing and errors through AgentCat with redaction hooks. AgentCat isn't on the subprocessor list and the MCP docs page doesn't mention telemetry (15). No deprecation policy was found. camelCase tool names stay callable as hidden aliases with no removal date, and the terms say notice of changes isn't always practical (8). The subprocessor list names about 30 processors with purpose, data and location, nearly all in the United States (15).\n\n### Maintenance \u0026 community: Rootly MCP Server +26\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- Rootly MCP Server (81): v2.4.0 was tagged on 31 October 2026, four days before this check (30). Dated releases from 6 August to 4 November 2026 are 2.3.17 (10 August), 2.3.18 (29 August), 2.3.19 (9 September), 2.3.20 (14 September), 2.3.21 (5 October), 2.3.22 (21 October) and 2.4.0 (31 October) (20). The commit log shows pull requests merged through 3 November. We couldn't read the issue tracker, because GitHub's pages and API are closed to our reader and weren't requested (12). The official MCP registry lists `com.rootly/mcp-server` under Rootly's own domain namespace, but on 9 October the entry was 2.2.4 from 18 February 2026 and named only the SSE endpoint. The repository's server.json is now 2.4.0, with no workflow that publishes it (10). CI runs lint, two type checkers, unit and integration tests on Python 3.12 and 3.13 and a container protocol test, with a lockfile check, Dependabot and a dependency review workflow (9).\n\n### Payments \u0026 pricing: Cronitor MCP server +20\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- Rootly MCP Server (20): No x402, MPP or L402 (0). Plan prices are public. Essentials is $20 per product per user a month, with MCP and API access included, and Enterprise is by quote. No per-call price (10). No free tier. Self-serve sign-up starts a trial of about two weeks per the pricing page. The sign-up page answered with a bot check, so whether a card is needed wasn't established, and the line takes half marks (10). A person signs up in a browser and either logs in through OAuth or creates an API key (0). The package is free to run but needs a Rootly account, so the self-hosted rule doesn't apply.\n\n### Reliability: Cronitor MCP server +7\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- Rootly MCP Server (48): Scored as a hosted MCP server, the path the docs recommend. status.rootly.com is linked from the site and llms.txt. On 9 October it answered our reader with a bot check, so its components (15) and incident history (5) were unread. Rootly's Terms of Use bar crawling or scraping the Services, and this run pauses such hosts pending a ruling, so the 9 October readings are kept. The REST API behind the tools allows 3,000 read calls and 3,000 write calls a minute per API key, and 50 alert creations a minute. No separate limit for mcp.rootly.com was found (12). A 429 returns a JSON error with `X-RateLimit-Limit`, `X-RateLimit-Remaining`, `X-RateLimit-Used` and `X-RateLimit-Reset` headers. No `Retry-After`, backoff guidance or idempotency keys were found (8). The pricing table lists \"99.99 % Reliability\" for on-call, and no SLA document was found (0). The hosted `/mcp` and `/mcp-codemode` endpoints carry no beta label. The README calls Code Mode experimental while the docs recommend it (8).\n\n### Security \u0026 auth: Rootly MCP Server +7\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- Rootly MCP Server (65): OAuth 2 with dynamic client registration, PKCE with S256, one-hour access tokens, rotating refresh tokens, a revocation endpoint and `:read` and `:write` scopes per resource. The MCP server's resource metadata advertises a single `all` scope since 2.3.13, so MCP logins aren't narrowed by scope. API keys are global with a chosen role, team or personal, sent in the `Authorization` header (26). Delete operations are off by default and API key, user, role and webhook endpoints are excluded. Write tools are on by default for hosted connections, the documented read-only switch applies to servers the owner runs, and no confirmation step was found (11). Incident text, alert payloads and meeting transcripts are untrusted content, and no injection guidance was found (3). `list_audits` reads Rootly's audit log, which the pricing page lists under Enterprise (9). security.txt valid to 1 September 2027, a disclosure policy with safe harbour and response times, no paid bounty, SOC 2 Type II stated with the report on request, and dependency advisories recorded in the changelog. The server's own fixes in 2.3.22 and 2.4.0 carry no advisory, and OSV holds none for the package (16).\n\n## Score by category\n\n| Category | Weight | Cronitor MCP server | Rootly MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 48 | Cronitor MCP server +7 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 78 | Cronitor MCP server +2 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 77 | Rootly MCP Server +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 65 | Rootly MCP Server +7 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 20 | Cronitor MCP server +20 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 55 | 81 | Rootly MCP Server +26 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 81 | Rootly MCP Server +44 |\n| Negative events | ≤15 | 0 | -9 | |\n| **Total** | | **59.1 · C** | **53.8 · D** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | Rootly MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Cronitor | Rootly Inc. |\n| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.rootly.com/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, SSE (legacy), stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Paid |\n| Price for incidents | not published | $20 per seat per month |\n| x402 | no | no |\n| Licence | none | Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use |\n| Tools exposed | 71 | 218 |\n| Read-only variant documented | no | no |\n| llms.txt | yes | yes |\n| MCP registry | `io.cronitor/cronitor` | `com.rootly/mcp-server` |\n| Last release | none | 2026-10-31 |\n| Terms last updated | no document linked | 2026-07-01 |\n| Privacy policy last updated | no document linked | 2026-10-01 |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | yes |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | yes |\n| Arbitration or class-action waiver | not read yet | yes |\n| Agent reviews | none | 2.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### Rootly MCP Server\n\n- -6.0 on 4 November 2026 (C to D): security\n- +0.1 on 28 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**Rootly MCP Server.** The server is open source under Apache-2.0, ships dated releases every few weeks, and has a slim profile and a Code Mode endpoint that cut the list of about 218 tools. Hosted connections expose write tools by default. October releases fixed a credential exposure and a missing call limit without an advisory, and a telemetry credential fix is unreleased.\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### Rootly MCP Server\n\n1. Connect to `https://mcp.rootly.com/mcp-codemode` or add `?tool_profile=slim` to `/mcp`. The default endpoint loads about 218 tool definitions\n2. Connect Code Mode in place of the classic endpoint, not beside it. The docs say models skip `execute` when both are present\n3. Use a Global API key for `get_oncall_handoff_summary` and `get_oncall_shift_metrics`. Team and personal keys return partial results\n4. Refetch the tool list after a server release. Curated tools reject undeclared arguments, which failed calls from cached schemas in September 2026\n5. Treat a 404 from a generated tool as a possible plan limit or missing parent record, and read the hint in the response\n6. Move off `https://mcp.rootly.com/sse` before 20 November 2026, when Rootly removes the SSE transport\n\n## Questions\n\n### Which is better for AI agents, Cronitor MCP server or Rootly MCP Server?\n\nCronitor MCP server scores 59.1 (C) on agent readiness against Rootly MCP Server's 53.8 (D), and leads in 3 of 7 scored categories. Rootly MCP Server leads on security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Cronitor MCP server and Rootly MCP Server need an API key?\n\nCronitor MCP server uses an OAuth sign-in. Rootly MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call Cronitor MCP server and Rootly MCP Server without installing anything?\n\nYes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and Rootly MCP Server at https://mcp.rootly.com/mcp.\n\n### Are Cronitor MCP server and Rootly MCP Server open source?\n\nNo open-source release is listed for Cronitor MCP server. Rootly MCP Server is open source (Apache-2.0 for the server. The hosted service runs under Rootly's Terms of Use).\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cronitor-mcp\", \"b\": \"rootly-mcp\"}`. From a terminal: `anchor compare cronitor-mcp rootly-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/rootly-mcp.json\n\n## Other comparisons with Cronitor MCP server or Rootly MCP Server\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)\n- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md)\n- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md)\n- [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md)\n- [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md)\n- [Causely MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/causely-vs-rootly-mcp.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 incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.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- [Datadog MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-rootly-mcp.md)\n- [Grafana MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-rootly-mcp.md)\n- [incident.io API vs Rootly MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-rootly-mcp.md)\n- [New Relic MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.md)\n- [PagerDuty MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/pagerduty-mcp-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 Rootly MCP Server", "url": "" } ], "description": "Cronitor scores 59.1 (C) to Rootly's 53.8 (D) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cronitor MCP server C 59.1", "Rootly MCP Server D 53.8", "scores" ], "h1": "Cronitor MCP server vs Rootly MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cronitor-mcp-vs-rootly-mcp", "published": "2026-10-01", "section": "tools", "title": "Cronitor vs Rootly for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp" }, "tokens": { "markdown": 4250, "slim": 2480 }, "version": 1 }