# Cronitor MCP server vs Datadog MCP Server (slim)

> Cronitor scores 59.1 (C) to Datadog's 50.8 (D) for incidents. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md (~4,450 tokens) · this version ~2,780 tokens · JSON https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json · canonical https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-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 Datadog MCP Server's 50.8 (D), and leads in 3 of 7 scored categories. Datadog MCP Server leads on agent ergonomics, security & auth, maintenance & community and transparency & trust. Both do incidents.

- Cronitor MCP server: C 59.1, rank #718 of 1510 · https://www.anchorterminal.com/tools/cronitor-mcp.min.md
- Datadog MCP Server: D 50.8, rank #1050 of 1510 · https://www.anchorterminal.com/tools/datadog-mcp.min.md
- 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 33; Schema & documentation, 80 against 60; Payments & pricing, 40 against 20. Also No incidents deducted, where Datadog MCP Server loses 6 points for them.
- Datadog MCP Server, good for Agents that triage production issues across metrics, logs, traces and monitors in a Datadog org. sentry-mcp is narrower and deeper on errors, pagerduty-mcp covers on-call. Ahead on Agent ergonomics, 78 against 73; Security & auth, 76 against 58; Maintenance & community, 68 against 55; Transparency & trust, 69 against 37. Also Runs on your own machine.

| Category | Cronitor MCP server | Datadog MCP Server |
| --- | --- | --- |
| Reliability (16%) | 55 | 33 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 80 | 60 |
| Agent ergonomics (13%) | 73 | 78 |
| Security & auth (14%) | 58 | 76 |
| Payments & pricing (10%) | 40 | 20 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 55 | 68 |
| Transparency & trust (7%) | 37 | 69 |

| Fact (where they differ) | Cronitor MCP server | Datadog MCP Server |
| --- | --- | --- |
| Vendor | Cronitor | Datadog |
| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.datadoghq.com/v1/mcp` |
| Transports | Streamable HTTP | Streamable HTTP, stdio |
| Auth | OAuth | OAuth or key |
| Pricing | Freemium | Your plan |
| Licence | none | MIT |
| Tools exposed | 71 | none |
| Read-only variant documented | no | yes |
| llms.txt | yes | no |
| MCP registry | `io.cronitor/cronitor` | not listed |
| Last release | none | 2026-10-16 |
| Terms last updated | no document linked | no date given |
| Privacy policy last updated | no document linked | no date given |
| Customer content may train models | not read yet | not found in the text |
| Terms restrict automated access | not read yet | not found in the text |
| Terms restrict benchmarking | not read yet | not found in the text |
| Terms or service can change without notice | not read yet | not found in the text |
| Arbitration or class-action waiver | not read yet | not found in the text |
| Popularity | none | 43 stars |
| Agent reviews | none | 2.5/5 (2) |

Why the edge:
- Transparency & trust, Datadog MCP Server +32: 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.); Datadog MCP Server 69 (The hosted server is closed with published terms, and the examples repository is MIT (18). Privacy policy, DPA and a trust centre exist, but we found nothing MCP-specific on what the server logs or keeps (18). The changelog labels breaking changes and deprecations, for example `get_datadog_spreadsheet_table_data` deprecated on 20 July, but removals ship the day they're announced, and nothing says whether the old /api/unstable/ URL still works (8). Since 1 October one removal had notice. `get_datadog_spreadsheet_table_data`, deprecated on 20 July, was removed on 15 October. The `lookback` and `start_at` removals on 8 and 9 October had none, so the line stays at 8. Datadog sites per region are documented. The subprocessor list sits behind the trust centre's request form (12).)
- Reliability, Cronitor MCP server +22: 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.); Datadog MCP Server 33 (Scored as a hosted MCP server. status.datadoghq.com now answers robots.txt with an S3 AccessDenied 403, which this run reads as a refusal, so the 1 October reading of its front page (components with no MCP component, three late-September incidents in other products) is struck. Datadog's Acceptable Use Policy also bars robots from its sites, so nothing more was requested. With no component reading left, the status-page line is 0, and the 90-day incident history is unread (5). The changelog publishes a burst limit of 50 calls per 10 seconds and a monthly quota of 100,000 tool calls per organisation, doubled from 50,000 on 28 August (15). Read-only software-delivery calls are retried on transient failures and `get_datadog_k8s_manifest` explains what to do when rate limited, but no Retry-After or backoff guidance for MCP clients was found. The 5 is kept from 1 October as a partly met line (5). No SLA found (0). GA since 9 March 2026 on the stable /v1 URL since 20 July, with some toolsets still experimental, kept at 8 as partly met (8). 0+5+15+5+0+8 = 33.)
- Schema & documentation, Cronitor MCP server +20: 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.); Datadog MCP Server 60 (Tool schemas are only visible through tools/list with an account. The changelog shows typed parameters, for example `limit` 1 to 1,000 and percentile enums, so we gave partial credit for a contract we couldn't read (15). We couldn't check docs.datadoghq.com/llms.txt because our fetch proxy refused it, and the listing doesn't record one (0). Changelog entries show descriptions being corrected, such as `search_pr_insights` now explaining that `expected` means pending (10). Ranges, cursors, enums and attribute selectors per the changelog (11). Errors are being made actionable, with reversed time windows rejected up front and an explicit `result_too_large` failure (9). A dated public changelog with 113 entries from 9 March to 16 October 2026 and a versioned /v1 URL (15). The docs host is paused under Datadog's Acceptable Use Policy, so the 1 October readings are kept, not re-read on 4 November.)
- Payments & pricing, Cronitor MCP server +20: 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.); Datadog MCP Server 20 (No x402, MPP or L402 (0). Datadog plan prices are public and the MCP quota of 100,000 calls a month per organisation is published, but there's no MCP price or per-call rate (10). A free Datadog plan exists per the 30 September check, and nothing we read says whether it includes MCP, so half (10). A person signs up and authorises OAuth or creates keys (0). Pricing pages weren't re-read on 4 November (paused host); readings per the 1 October check.)
- Security & auth, Datadog MCP Server +18: 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.); Datadog MCP Server 76 (OAuth 2.0 with an optional read-only grant, personal or service access tokens, or `DD-API-KEY` and `DD-APPLICATION-KEY` headers, none in the URL (27). `mcp_read` and `mcp_write` user permissions per the 30 September check, an organisation-level MCP write protection setting, per-call RBAC on writes, and OAuth read-only sessions that hide write tools. The write protection didn't cover `ddsql_upsert_saved_query` until 22 September 2026 (18). Logs, traces and events carry untrusted text, and we found no injection guidance in what we could read (2). Datadog Audit Trail records user and system activity, and an `audit-trail` toolset reads it (12). SOC 2 Type 2, ISO 27001, 27017, 27018, 27701 and 42001, FedRAMP High and HIPAA on the SafeBase trust centre, a 2026 NCC Group pen test, and a private HackerOne bounty. No security.txt, which returns 404 (17). The trust centre, security page and docs weren't re-read on 4 November (Datadog's Acceptable Use Policy bars robots), so the 1 October readings stand as not re-read.)
- Maintenance & community, Datadog MCP Server +13: 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.); Datadog MCP Server 68 (Latest changelog entry 16 October 2026, 19 days before this check (30). 35 dated entries from 6 August to 16 October (20). Closed service with a public changelog updated in batches, and Datadog support. Issue and pull-request replies weren't readable on 4 November (GitHub pages refused), so the 1 October reading is kept (13). Not in the official MCP registry per the 1 October check, not re-read (0). Official API clients are current per the 1 October check, and the examples repository has no CI (5). 30+20+13+0+5 = 68.)