# Causely MCP server vs Cronitor MCP server (slim)

> Cronitor scores 59.1 (C) to Causely's 39.5 (E) for incidents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.md (~4,550 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp.json · canonical https://www.anchorterminal.com/compare/causely-vs-cronitor-mcp
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-07
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Cronitor MCP server scores 59.1 (C) on agent readiness against Causely MCP server's 39.5 (E), and leads in 4 of 7 scored categories. Causely MCP server leads on maintenance & community and transparency & trust. Both do incidents.

- Causely MCP server: E 39.5, rank #1340 of 1510 · https://www.anchorterminal.com/tools/causely.min.md
- Cronitor MCP server: C 59.1, rank #718 of 1510 · https://www.anchorterminal.com/tools/cronitor-mcp.min.md
- Causely MCP server, good for Teams that already run Causely, or will, and want agents to start an incident from an inferred root cause, blast radius and recent changes rather than raw metrics and logs. Ahead on Maintenance & community, 79 against 55; Transparency & trust, 57 against 37.
- Cronitor MCP server, good for Teams who monitor cron jobs, heartbeats and sites with Cronitor and want an agent to set up and triage monitoring. Ahead on Reliability, 55 against 12; Schema & documentation, 80 against 65; Agent ergonomics, 73 against 42; Payments & pricing, 40 against 20. Also No incidents deducted, where Causely MCP server loses 5 points for them.

| Category | Causely MCP server | Cronitor MCP server |
| --- | --- | --- |
| Reliability (16%) | 12 | 55 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 65 | 80 |
| Agent ergonomics (13%) | 42 | 73 |
| Security & auth (14%) | 59 | 58 |
| Payments & pricing (10%) | 20 | 40 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 79 | 55 |
| Transparency & trust (7%) | 57 | 37 |

| Fact (where they differ) | Causely MCP server | Cronitor MCP server |
| --- | --- | --- |
| Vendor | Causely, Inc. | Cronitor |
| Hosted endpoint | `https://api.causely.app/mcp` | `https://cronitor.io/mcp` |
| Auth | OAuth or key | OAuth |
| Pricing | Paid | Freemium |
| Licence | Proprietary hosted service under Causely's Terms of Service and Platform Terms & Conditions. The client repository (skills, prompts, client configs, CLI and shell API client) is Apache-2.0; the MCP server's source is not public | none |
| Tools exposed | 46 | 71 |
| MCP registry | `app.causely/causely` | `io.cronitor/cronitor` |
| Last release | 2026-10-19 | none |
| Terms last updated | 2023-06-05 | no document linked |
| Privacy policy last updated | 2026-05-07 | no document linked |
| Customer content may train models | not found in the text | not read yet |
| Terms restrict automated access | not found in the text | not read yet |
| Terms restrict benchmarking | not found in the text | not read yet |
| Terms or service can change without notice | yes | not read yet |
| Arbitration or class-action waiver | not found in the text | not read yet |
| Agent reviews | 2.8/5 (4) | none |

Why the edge:
- Reliability, Cronitor MCP server +43: Causely MCP server 12 (Graded with the hosted lines, on the remote MCP server at api.causely.app/mcp. No public status page was found. The docs, site and llms.txt link none, and status.causely.ai and status.causely.app didn't answer (0). With no history to read, the incident record scores 5. No rate limit for the MCP server or API is published with numbers (0), and no 429, Retry-After or backoff guidance was found in the full docs corpus (0). The Professional plan promises best-effort response times and Enterprise an "option for custom SLAs" with no figure (0). The server isn't labelled beta and its registry entry is 1.0.1, but the Issues objects behind `get_issues` and `get_issue_details`, which the docs call the starting point, are an early access release per v1.0.135 (7 of 10).); 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.)
- Agent ergonomics, Cronitor MCP server +31: Causely MCP server 42 (46 tools is above the 30 line (5). No toolsets, dynamic loading or read-only subset on the server; the skills choose tools on the client side and the configuration tools refuse callers below the Developer role, but stay loaded, so nothing is added back. Filters by cluster, namespace, entity, label and date, `limit` on listing tools, summary tools split from detail tools since v1.0.133, up to 20 services per `fleet_reliability_delta` call and logs grouped by signature with counts. No pagination cursor is documented (15 of 20). Explicit errors when a cluster or namespace matches nothing and a not-found error for an unknown entity ID (v1.0.141), but no documented codes (8 of 20). Most tools read, and `set_service_tier` and the `ignore_issue` pair set a state, but annotations couldn't be read and no idempotency guidance exists for `create_threshold_configuration` (5 of 20). `get_symptoms` needs no filters and `get_alerts` matches alert names by substring. No official SDK for the MCP server; the API has a shell client and examples (9 of 15).); Cronitor MCP server 73 (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.)
- Maintenance & community, Causely MCP server +24: Causely MCP server 79 (Read as a closed hosted service. v1.0.142 shipped on 19 October 2026, v1.0.141 on 8 October changed the MCP server, and the client repository's last commit is 20 October (30). Seven dated releases in the last 90 days, v1.0.135 to v1.0.142 (20). Public changelog, a dedicated Slack or Teams channel for paying customers, a support address and a `submit_feedback` tool. The client repository's pull requests are Causely staff's; its issues couldn't be read through our GitHub access (10 of 15). `app.causely/causely` is in the official MCP registry under Causely's own domain namespace, published 17 August 2026, with 1.0.1 on 31 August (15). The client repository has shell tests but no CI workflows, and the server itself is closed (4 of 10).); 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.)
- Payments & pricing, Cronitor MCP server +20: Causely MCP server 20 (No x402, MPP or L402 (0). Plan prices are public, with Professional at $2,000 a month for up to 500 services, Enterprise on request, with the MCP server included and no per-call price (10). A free 30-day trial starts from a self-serve sign-up page. That page is drawn by script and the host blocked our reader, so whether it asks for a card is unchecked (10 of 20). A person signs up in a browser and installs the Mediator in their own environment before an agent has anything to query (0).); 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.)
- Transparency & trust, Causely MCP server +20: Causely MCP server 57 (The editorial half. A closed hosted service under Terms of Service naming Causely, Inc. and New York law. The website section is dated 5 June 2023 and the Platform Terms & Conditions on the same page are undated. Skills, prompts and client code are Apache-2.0 (17). The security docs say what leaves the customer's environment, what is scrubbed and that customer data never trains shared or foundational models, and the plan states 30 days of retention. The Privacy Policy (7 May 2026) gives no retention periods for the service, no DPA was found, and the security page's "No sensitive data or PII is stored or processed" is stronger than the docs' "filtered out to the extent possible" (15 of 30). No deprecation policy. Tool replacements are dated in the changelog, on the day they shipped (3 of 20). No subprocessor list; the terms mention unnamed vendors and hosting partners, the privacy policy says data is processed in the United States, and a BYOC deployment keeps the backend in the customer's network (6 of 20).); 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.)
- Schema & documentation, Cronitor MCP server +15: Causely MCP server 65 (MCP `tools/list` answered 401 without a key, and no tool schemas or annotations are published elsewhere. Partial credit for a contract that exists but isn't public, as for Honeycomb (12). llms.txt, llms-full.txt, a primer for models and a Markdown copy of every docs page (10). The tool reference gives each of the 46 tools a "When to use" line, marks `get_entities` as the place to start, and the skills add rules such as not looping `get_topology` where `rank_entities` does it in one call. Few say when not to use a tool (15 of 20). Parameters appear only in the skills' key-parameter columns, some with enums such as `INDIVIDUAL`, `LABEL` and `GLOBAL` or the tier values, and RFC3339 times, with no types or required fields (6 of 15). Worked prompts and tool sequences for four workflows and 27 prompt files, but no error list; the changelog describes explicit errors for unmatched filters and unknown IDs (7 of 15). A dated changelog with RSS, Atom and JSON feeds, MCP changes named per release, and registry versions 1.0.0 and 1.0.1 (15).); 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.)