# Cronitor MCP server > 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. - Canonical: https://www.anchorterminal.com/tools/cronitor-mcp - Pricing: https://www.anchorterminal.com/tools/cronitor-mcp#pricing - Reviews: https://www.anchorterminal.com/tools/cronitor-mcp#reviews - Markdown: https://www.anchorterminal.com/tools/cronitor-mcp.md (~4,400 tokens) - Slim: https://www.anchorterminal.com/tools/cronitor-mcp.min.md (~1,180 tokens, same facts, less prose, for token-sensitive contexts) - JSON: https://www.anchorterminal.com/tools/cronitor-mcp.json (this page as data, same URL with Accept: application/json) - Site index for agents: https://www.anchorterminal.com/llms.txt (the key docs and every listing in one file, at most 16 MB, about 4 million tokens: https://www.anchorterminal.com/llms-full.txt) - API: https://www.anchorterminal.com/api/v1/index.json - MCP: https://www.anchorterminal.com/mcp (the whole catalogue as tools, no key) - DNS: dig +short TXT cronitor-mcp.grade.anchorterminal.com (the grade as a DNS TXT record, for a sandbox with no HTTP where names still resolve; also top., best.. and .vs.. under the zone, and the same under grade.letme.dev) - Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data) - Updated: 2026-11-08 ## Overview **Grade C · 59.1/100 · rank #718 of 1510 · #7 in Observability & incidents · not agent-ready · confidence medium** ## Assessment 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. ## Facts | Field | Value | | --- | --- | | Vendor | Cronitor (https://cronitor.io) | | Kind | MCP server | | Category | Observability & incidents (https://www.anchorterminal.com/categories/observability) | | Transport | Streamable HTTP | | Endpoint | `https://cronitor.io/mcp` | | Auth | OAuth · 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 (Freemium) · 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). | | x402 | No · No x402, MPP or L402 on the MCP docs or pricing page (checked 2026-11-07). | | Licence | unknown | | Tools exposed | 71 | | MCP registry name | `io.cronitor/cronitor` | | Docs | https://cronitor.io/docs/mcp-server | | llms.txt | https://cronitor.io/llms.txt | | Surface listed | The hosted MCP server at cronitor.io/mcp, read from cronitor.io and status.cronitor.io on 7 November 2026. Only an MCP initialize was sent, which asked for sign-in | | Not read | cronitor.io/robots.txt disallows /terms and /privacy, so neither was fetched | | 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 | | JSON | https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json | ## Score breakdown (methodology v0.7, October 2026 research run) Assessed 2026-11-07 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. "This run" is each category's share of the 100 points. | Category | Weight | This run | Score (0–100) | Points | | --- | --- | --- | --- | --- | | Reliability | 16% | 20 | 55 | 11.0 | | Performance | 10% | pending | pending | n/a | | Schema & documentation | 13% | 16.2 | 80 | 13.0 | | Agent ergonomics | 13% | 16.2 | 73 | 11.9 | | Security & auth | 14% | 17.5 | 58 | 10.2 | | Payments & pricing | 10% | 12.5 | 40 | 5.0 | | Task success | 10% | pending | pending | n/a | | Maintenance & community | 7% | 8.8 | 55 | 4.8 | | Transparency & trust (editorial 25, provenance 48) | 7% | 8.8 | 37 | 3.2 | | Negative events | up to −15 | up to −15 | none recorded | 0 | | **Total** | | | | **59.1 → C** | ### Why each score - Reliability 55 (checked 2026-11-07): 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. - Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes. - Schema & documentation 80 (checked 2026-11-07): 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. - Agent ergonomics 73 (checked 2026-11-07): 71 tools (5), with four task-oriented tools and summary modes that cap list output (5 back). Summary mode defaults to 25 rows, allows 100 and returns next_page (20). Documented, recoverable errors (18 of 20). Safety metadata in each tool schema and documented repeat behaviour (15 of 20). setup_monitor takes few fields; SDKs and a CLI (10 of 15). 10 + 20 + 18 + 15 + 10 = 73. - Security & auth 58 (checked 2026-11-07): 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. - Payments & pricing 40 (checked 2026-11-07): 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. - Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored. - Maintenance & community 55 (checked 2026-11-07): 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. - Transparency & trust 37 (checked 2026-11-07): 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. Fix list, everything this grade says the listing lacks, the biggest gain first (15 items). What it covers is at https://www.anchorterminal.com/fixes/cronitor-mcp.md (JSON https://www.anchorterminal.com/fixes/cronitor-mcp.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{"listing": "cronitor-mcp", "plan": "read"}`, free while the beta runs ### What we couldn't check - Terms and privacy weren't read (robots.txt) - Incident history not readable - People, ownership and investors not researched ### Sources - MCP server docs: (seen 2026-11-07) - MCP landing page: (seen 2026-11-07) - pricing: (seen 2026-11-07) - security docs: (seen 2026-11-07) - status page: (seen 2026-11-07) - llms.txt: (seen 2026-11-07) - lead, awesome-remote-mcp-servers pull request #3869: (seen 2026-11-07) ## Score history Every move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp/history.json - 2026-11-07: graded 59.1 C (methodology 0.7) ## Who's behind it (provenance 48/100, checked 2026-11-07) | Check | Finding | Points | | --- | --- | --- | | Legal entity named | Cronitor | 20/20 | | Domain age | cronitor.io, no registry record we could read | 0/15 | | Endpoint on the vendor's domain | cronitor.io | 15/15 | | Terms of service | not found | 0/10 | | Privacy policy | not found | 0/10 | | Status page | status.cronitor.io | 10/10 | | Changelog | not found | 0/10 | | security.txt | not found | 0/10 | | People named | not researched yet | n/a | | Support route | help pages | 5/5 | Not looked up: RDAP isn't requested under the 1 November 2026 rules. robots.txt disallows the terms and privacy pages, so the legal entity wasn't read. security.txt answered 404. ### Terms and privacy, as read A reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice. **Terms of service**. We found no terms of service published for this product, so there is nothing to read and the check scores 0. **Privacy policy**. We found no privacy policy published for this product, so there is nothing to read and the check scores 0. ## Humans behind the project (researched 2026-11-07 from public pages, not part of the grade) ### Key people - No people named yet. - Note: People, ownership and investors weren't researched in this batch (7 November 2026, leads from the awesome-remote-mcp-servers pull requests). ### Getting support - Help: https://cronitor.io/docs/mcp-server - Sources: https://cronitor.io/docs/mcp-server ## Live (updated 2026-11-08 00:43 UTC) - Right now: up, HTTP 401, 627 ms, checked 2026-11-08 00:43 UTC (mcp-initialize on `https://cronitor.io/mcp`, asks for auth) - Uptime 24h 100.0% (61 probes) · 30 days 100.0% (61 probes) · p50 629 ms · p95 703 ms - Vendor status page: not read, no machine-readable status found - Always current: https://www.anchorterminal.com/api/v1/live/cronitor-mcp.json ## Probe metrics Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score. ## 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 ## Before you call it (notes for agents) 1. Start with list_monitors and list_issues in summary mode 2. Ask the user before expanding event messages, command output or request bodies 3. On a rate-limit error, wait retry_after_seconds 4. Over the plan's monitor limit, new monitors are saved but disabled ## Connect Claude Code: ```bash claude mcp add cronitor --transport http https://cronitor.io/mcp ``` MCP client configuration: ```json { "mcpServers": { "cronitor": { "url": "https://cronitor.io/mcp" } } } ``` Through letme: https://letme.dev/cronitor-mcp. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md ## Similar tools Ranked by shared capabilities, then score. Same-category tools with no shared capability key are listed last. | Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown | | --- | --- | --- | --- | --- | --- | --- | | Grafana MCP Server | BB | 71 | 172 | observability.metrics, observability.incidents | no | https://www.anchorterminal.com/tools/grafana-mcp-server.md | | Axiom MCP Server | B | 68.2 | 294 | observability.metrics, observability.incidents | no | https://www.anchorterminal.com/tools/axiom.md | | New Relic MCP Server | C | 61 | 630 | observability.metrics, observability.incidents | no | https://www.anchorterminal.com/tools/new-relic.md | | Better Stack | C | 54.2 | 917 | observability.incidents, observability.metrics | no | https://www.anchorterminal.com/tools/better-stack.md | | Datadog MCP Server | D | 50.8 | 1050 | observability.metrics, observability.incidents | no | https://www.anchorterminal.com/tools/datadog-mcp.md | | Causely MCP server | E | 39.5 | 1340 | observability.incidents, observability.metrics | no | https://www.anchorterminal.com/tools/causely.md | ## Panel reviews (0) Reviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): . Desk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md ## Notable - 71 tools, four task-oriented, three discovery and 64 resource operations mirroring the Cronitor CLI (source: ) - Every input schema declares additionalProperties false (source: ) - OAuth tokens carry the user's role with no scope selection; API keys keep granular scopes (source: ) - Free plan for 5 monitors; Business $2 a monitor and $5 a user a month (source: ) - #7 of 12 in Best observability and incident tools for AI agents: https://www.anchorterminal.com/best/observability/index.md - All 59 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md ## Compare - [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md): B 68.2 vs C 59.1 - [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-mcp.md): C 54.2 vs C 59.1 - [Causely MCP server vs Cronitor MCP server](https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md): E 39.5 vs C 59.1 - [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md): C 59.1 vs D 50.8 - [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md): C 59.1 vs BB 71 - [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md): C 59.1 vs B 68.9 - [Cronitor MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md): C 59.1 vs C 61 - [Cronitor MCP server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-pagerduty-mcp.md): C 59.1 vs E 43.9 - [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md): C 59.1 vs D 53.8 - [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md): C 59.1 vs C 60.7 ## Verify this listing For the vendor. The badge or a plain link to this page verifies the listing, from a page on cronitor.io or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{"slug": "cronitor-mcp", "url": "…"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify HTML badge: ```html Cronitor MCP server on Anchor Terminal ``` Markdown badge, for a README: ```markdown [![Cronitor MCP server on Anchor Terminal](https://www.anchorterminal.com/badges/cronitor-mcp.svg)](https://www.anchorterminal.com/tools/cronitor-mcp) ``` Plain link: ```html Cronitor MCP server on Anchor Terminal ``` ## Share this listing For the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Cronitor MCP server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score. - Dark: https://www.anchorterminal.com/assets/share/cronitor-mcp-dark.png - Light: https://www.anchorterminal.com/assets/share/cronitor-mcp-light.png --- Query this catalogue directly over MCP: https://www.anchorterminal.com/mcp (Streamable HTTP, no key). How: https://www.anchorterminal.com/agents/#mcp