{ "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 Datadog MCP Server's 50.8 (D), and leads in 3 of 7 scored categories. Datadog MCP Server leads on agent ergonomics, security \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "b": { "slug": "datadog-mcp", "name": "Datadog MCP Server", "vendor": "Datadog", "vendorUrl": "https://docs.datadoghq.com/mcp_server/", "kind": "mcp", "category": "observability", "summary": "Datadog's hosted MCP server for querying monitors, logs, metrics, traces, dashboards, incidents and more, with 30-plus toolsets, a sandboxed code-execution toolset, OAuth 2.0 or key auth, and per-call permission checks on writes.", "url": "https://www.anchorterminal.com/tools/datadog-mcp", "markdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/datadog-mcp.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json", "dns": "datadog-mcp.grade.anchorterminal.com", "repo": "https://github.com/datadog-labs/mcp-server", "license": "MIT", "transports": [ "streamable-http", "stdio" ], "remoteUrl": "https://mcp.datadoghq.com/v1/mcp", "packages": [], "auth": "mixed", "authNotes": "OAuth 2.0 (recommended, with an optional read-only grant that hides write tools), personal or service access tokens as a Bearer header, or `DD-API-KEY` plus `DD-APPLICATION-KEY` headers. A local `datadog_mcp_cli` binary gives you stdio where remote auth isn't possible. EU endpoint at mcp.datadoghq.eu. Users need the `mcp_read` and `mcp_write` permissions, and an organisation setting can block MCP writes.", "pricing": "byo-plan", "pricingNotes": "No separate charge stated. Datadog plan prices are public and a free plan exists. MCP use is capped by a default quota of 100,000 tool calls a month per organisation (raised from 50,000 on 2026-08-28) and a burst limit of 50 calls per 10 seconds. Whether the free plan includes MCP isn't stated (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).", "priceSummary": "Your plan", "where": "both", "x402": { "level": "no", "evidence": "No payments. Access follows the Datadog account.", "endpoints": [] }, "toolCount": null, "popularity": { "githubStars": 43, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-09-26" }, "docsUrl": "https://docs.datadoghq.com/mcp_server/", "capabilities": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents" ], "tags": [ "official", "hosted", "oauth", "toolsets", "enterprise", "preview-parts" ], "lastRelease": "2026-10-16", "graded": true, "anchor": { "graded": true, "score": 50.8, "grade": "D", "agentReady": false, "rank": 1050, "ranked": true, "rankOf": 1510, "categoryRank": 10, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 78, "maintenance": 68, "payments": 20, "reliability": 33, "schema": 60, "security": 76, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-04" }, "negative": -6, "negativeNotes": [ "-3: published tool behaviour changed for existing callers with no notice, each posted in the changelog on or after the day it took effect. Detection-rule tools replaced and removed on 2026-06-17, `service` and `family` removed from `explore_profiling_call_graph` on 2026-06-26, `start_at` removed from `search_datadog_spans` on 2026-08-20, the `traces` extension removed from `execute_code` on 2026-09-24, `start_at` replaced by `cursor` on `search_datadog_rum_events` on 2026-10-08 and `lookback` removed from three RUM operation tools on 2026-10-09. Repeats of one kind fold into one term (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md).", "-3: until 2026-09-22, `ddsql_upsert_saved_query` created or updated saved queries even when an organisation had disabled MCP writes. The fix in the hosted server is described only in the changelog, with no security advisory, which this run reads as an unadvised fix of the product's own flaw (https://github.com/datadog-labs/mcp-server/blob/main/CHANGELOG.md)." ], "verdict": "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.", "bestFor": "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.", "strengths": [ "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes", "Toolsets, a sandboxed `execute_code` toolset and `whoami` and `toolsets` resources keep the schema in proportion", "Dated public changelog with 35 entries from 6 August to 16 October 2026", "Published burst limit and monthly quota", "SOC 2 Type 2, ISO 27001 and FedRAMP High, with a private HackerOne bounty" ], "weaknesses": [ "Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026", "Not in the official MCP registry, and Datadog's status host refuses our reader, so the incident record is unread", "Tool schemas and descriptions aren't readable without an account", "No security.txt, and the write-protection setting missed one tool until 22 September 2026, with no advisory", "Whether the free plan includes MCP isn't stated" ], "agentNotes": [ "Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one", "Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first", "Pass `limit` and `custom_attributes` on span searches and page with `cursor`. `start_at` is gone from spans and RUM events", "Pass `from` and `to` to the RUM operation tools. `lookback` was removed on 9 October 2026", "Budget calls. The org shares 100,000 a month and 50 per 10 seconds" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 2, "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": 50.8 } ], "editorialScores": { "ergonomics": 78, "maintenance": 68, "payments": 20, "reliability": 33, "schema": 60, "security": 76, "transparency": 56 }, "provenanceScore": 81, "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": { "claudeCode": "claude mcp add --transport http datadog https://mcp.datadoghq.com/v1/mcp", "config": { "mcpServers": { "datadog": { "type": "http", "url": "https://mcp.datadoghq.com/v1/mcp" } } }, "headless": { "mcpServers": { "datadog": { "headers": { "DD-API-KEY": "${DD_API_KEY}", "DD-APPLICATION-KEY": "${DD_APPLICATION_KEY}" }, "type": "http", "url": "https://mcp.datadoghq.com/v1/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/datadog-mcp" }, "area": "developer", "provenance": { "legalEntity": "Datadog, Inc.", "domain": "datadoghq.com", "domainRegistered": "2010-07-09", "endpointOnVendorDomain": true, "terms": "https://datadoghq.com/legal/terms/", "privacy": "https://datadoghq.com/legal/privacy/", "statusPage": "https://status.datadoghq.com", "changelog": "", "securityTxt": "none", "checked": "2026-09-26", "score": 81 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/datadog-mcp.json", "live": { "slug": "datadog-mcp", "probe": { "target": "https://mcp.datadoghq.com/v1/mcp", "method": "mcp-initialize", "lastAt": "2026-11-08T01:01:26.823125457Z", "lastOk": true, "lastStatus": 401, "lastMs": 328, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 284, "p95ms24h": 364, "samples24h": 244, "samples30d": 7705, "days": [ { "date": "2026-10-08", "probes": 268, "ok": 268 }, { "date": "2026-10-09", "probes": 250, "ok": 250 }, { "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": 251, "ok": 251 }, { "date": "2026-10-29", "probes": 248, "ok": 248 }, { "date": "2026-10-30", "probes": 249, "ok": 249 }, { "date": "2026-10-31", "probes": 251, "ok": 251 }, { "date": "2026-11-01", "probes": 249, "ok": 249 }, { "date": "2026-11-02", "probes": 250, "ok": 250 }, { "date": "2026-11-03", "probes": 248, "ok": 248 }, { "date": "2026-11-04", "probes": 246, "ok": 246 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 11, "ok": 11 } ] }, "vendorStatus": { "page": "https://status.datadoghq.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-08T00:31:11.551705254Z" }, "githubStars": 47, "securityTxt": { "url": "https://datadoghq.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-07T16:00:50.599261079Z" }, "domain": { "domain": "datadoghq.com", "registered": "2010-07-09", "source": "https://rdap.verisign.com/com/v1/domain/datadoghq.com", "checkedAt": "2026-11-01T14:25:58.901200417Z" }, "pages": [ { "url": "https://raw.githubusercontent.com/datadog-labs/mcp-server/main/CHANGELOG.md", "kind": "deprecations", "status": 304, "checkedAt": "2026-11-07T14:20:29.897987673Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "608f9d788416" }, { "url": "https://datadoghq.com/legal/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-07T14:02:25.702132215Z", "changedAt": "2026-11-03T07:44:08.283831716Z", "fingerprint": "75cab48d73a2" }, { "url": "https://datadoghq.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-07T14:02:28.231366123Z", "changedAt": "2026-11-03T07:44:11.02798267Z", "fingerprint": "78e429e0b25a" } ], "mcpTools": { "url": "https://mcp.datadoghq.com/v1/mcp", "checkedAt": "2026-11-07T01:43:41.914159909Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-09-28T21:55:38.616526541Z" }, "github": { "repo": "datadog-labs/mcp-server", "checkedAt": "2026-11-02T08:42:52.249779198Z", "stars": 47, "archived": false, "issuesEnabled": false, "pushedAt": "2026-10-16T22:22:44Z", "openIssues": 0, "openPRs": 0, "issuesOpened90d": 0, "issuesClosed90d": 0, "prsMerged90d": 3 }, "updatedAt": "2026-11-08T01:01:26.823125457Z" } }, "edges": [ { "by": 32, "category": "transparency", "leads": "datadog-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 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)." }, "scores": { "a": 37, "b": 69 } }, { "by": 22, "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. 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." }, "scores": { "a": 55, "b": 33 } }, { "by": 20, "category": "schema", "leads": "cronitor-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.", "b": "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." }, "scores": { "a": 80, "b": 60 } }, { "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). 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." }, "scores": { "a": 40, "b": 20 } }, { "by": 18, "category": "security", "leads": "datadog-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.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." }, "scores": { "a": 58, "b": 76 } }, { "by": 13, "category": "maintenance", "leads": "datadog-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": "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." }, "scores": { "a": 55, "b": 68 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Cronitor", "b": "Datadog", "name": "Vendor" }, { "a": "https://cronitor.io/mcp", "b": "https://mcp.datadoghq.com/v1/mcp", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP, stdio", "name": "Transports" }, { "a": "OAuth", "b": "OAuth or key", "name": "Auth" }, { "a": "Freemium", "b": "Your plan", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "none", "b": "MIT", "name": "Licence" }, { "a": "71", "b": "none", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "no", "name": "llms.txt" }, { "a": "io.cronitor/cronitor", "b": "not listed", "name": "MCP registry" }, { "a": "none", "b": "2026-10-16", "name": "Last release" }, { "a": "no document linked", "b": "no date given", "name": "Terms last updated" }, { "a": "no document linked", "b": "no date given", "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": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms restrict benchmarking" }, { "a": "not read yet", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not read yet", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "none", "b": "43 stars", "name": "Popularity" }, { "a": "none", "b": "2.5/5 (2)", "name": "Agent reviews" } ], "faq": [ { "answer": "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 \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.", "question": "Which is better for AI agents, Cronitor MCP server or Datadog MCP Server?" }, { "answer": "Cronitor MCP server uses an OAuth sign-in. Datadog MCP Server takes an API key or an OAuth sign-in.", "question": "Do Cronitor MCP server and Datadog MCP Server need an API key?" }, { "answer": "Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and Datadog MCP Server at https://mcp.datadoghq.com/v1/mcp.", "question": "Can an agent call Cronitor MCP server and Datadog MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 55 against 33", "Schema \u0026 documentation, 80 against 60", "Payments \u0026 pricing, 40 against 20" ], "also": [ "No incidents deducted, where Datadog MCP Server loses 6 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": [ "Agent ergonomics, 78 against 73", "Security \u0026 auth, 76 against 58", "Maintenance \u0026 community, 68 against 55", "Transparency \u0026 trust, 69 against 37" ], "also": [ "Runs on your own machine" ], "goodFor": "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.", "slug": "datadog-mcp", "watchFor": "Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026" } ], "history": { "cronitor-mcp": null, "datadog-mcp": [ { "causes": [ "evidence", "correction" ], "date": "2026-11-04", "delta": -6, "from": 56.8, "fromGrade": "C", "to": 50.8, "toGrade": "D" }, { "causes": [ "evidence" ], "date": "2026-10-28", "delta": 0.1, "from": 56.7, "fromGrade": "C", "to": 56.8, "toGrade": "C" }, { "causes": [ "method" ], "date": "2026-10-27", "delta": 0.1, "from": 56.6, "fromGrade": "C", "to": 56.7, "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/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/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-datadog-mcp.json", "title": "Causely MCP server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/causely-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/cronitor-mcp-vs-rootly-mcp.json", "title": "Cronitor MCP server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.json", "title": "Datadog MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-pagerduty-mcp.json", "title": "Datadog MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-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/axiom-vs-datadog-mcp.json", "title": "Axiom MCP Server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.json", "title": "Better Stack vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-datadog-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" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.json", "title": "Datadog MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.json", "title": "Datadog MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.json", "title": "Datadog MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp.json", "title": "Datadog MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-mcp" } ], "panel": null, "scores": [ { "by": 22, "cronitor-mcp": 55, "datadog-mcp": 33, "edge": "cronitor-mcp", "key": "reliability", "name": "Reliability", "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 20, "cronitor-mcp": 80, "datadog-mcp": 60, "edge": "cronitor-mcp", "key": "schema", "name": "Schema \u0026 documentation", "weight": 13 }, { "by": 5, "cronitor-mcp": 73, "datadog-mcp": 78, "edge": "datadog-mcp", "key": "ergonomics", "name": "Agent ergonomics", "weight": 13 }, { "by": 18, "cronitor-mcp": 58, "datadog-mcp": 76, "edge": "datadog-mcp", "key": "security", "name": "Security \u0026 auth", "weight": 14 }, { "by": 20, "cronitor-mcp": 40, "datadog-mcp": 20, "edge": "cronitor-mcp", "key": "payments", "name": "Payments \u0026 pricing", "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 13, "cronitor-mcp": 55, "datadog-mcp": 68, "edge": "datadog-mcp", "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7 }, { "by": 32, "cronitor-mcp": 37, "datadog-mcp": 69, "edge": "datadog-mcp", "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7 } ], "summary": "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 \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.", "datadog-mcp": "OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp", "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.min.md" }, "markdown": "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 \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- Datadog MCP Server: grade D, 50.8/100, rank #1050 of 1510. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-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 33\n- Schema \u0026 documentation, 80 against 60\n- Payments \u0026 pricing, 40 against 20\n\nAlso in its favour:\n- No incidents deducted, where Datadog MCP Server loses 6 points for them\n\nWatch for: 71 tools, a heavy context load\n\n### Datadog MCP Server (D)\n\nGood 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.\n\nAhead on:\n- Agent ergonomics, 78 against 73\n- Security \u0026 auth, 76 against 58\n- Maintenance \u0026 community, 68 against 55\n- Transparency \u0026 trust, 69 against 37\n\nAlso in its favour:\n- Runs on your own machine\n\nWatch for: Tools and parameters are removed the day they're announced, most recently `lookback` on three RUM tools on 9 October 2026\n\n\n## Why the edge\n\n### Transparency \u0026 trust: Datadog MCP Server +32\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- 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).\n\n### Reliability: Cronitor MCP server +22\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- 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.\n\n### Schema \u0026 documentation: Cronitor MCP server +20\n\n- Cronitor MCP server (80): Every tool's input schema declares additionalProperties false, and the docs call tools/list the field-level reference (25). llms.txt and .md pages for agents (10). Detailed tool guidance, including which to start with and what not to request (18 of 20). Typed inputs with enums, required combinations and no untyped data objects (15). A table of JSON-RPC error codes with their data fields, and worked calls (12 of 15). No public changelog found (404) (0). 25 + 10 + 18 + 15 + 12 + 0 = 80.\n- 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.\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- 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.\n\n### Security \u0026 auth: Datadog MCP Server +18\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- 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.\n\n### Maintenance \u0026 community: Datadog MCP Server +13\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- 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.\n\n## Score by category\n\n| Category | Weight | Cronitor MCP server | Datadog MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 33 | Cronitor MCP server +22 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 60 | Cronitor MCP server +20 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 78 | Datadog MCP Server +5 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 76 | Datadog MCP Server +18 |\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 | 68 | Datadog MCP Server +13 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 69 | Datadog MCP Server +32 |\n| Negative events | ≤15 | 0 | -6 | |\n| **Total** | | **59.1 · C** | **50.8 · D** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | Datadog MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Cronitor | Datadog |\n| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.datadoghq.com/v1/mcp` |\n| Transports | Streamable HTTP | Streamable HTTP, stdio |\n| Auth | OAuth | OAuth or key |\n| Pricing | Freemium | Your plan |\n| x402 | no | no |\n| Licence | none | MIT |\n| Tools exposed | 71 | none |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | no |\n| MCP registry | `io.cronitor/cronitor` | not listed |\n| Last release | none | 2026-10-16 |\n| Terms last updated | no document linked | no date given |\n| Privacy policy last updated | no document linked | no date given |\n| Customer content may train models | not read yet | not found in the text |\n| Terms restrict automated access | not read yet | not found in the text |\n| Terms restrict benchmarking | not read yet | not found in the text |\n| Terms or service can change without notice | not read yet | not found in the text |\n| Arbitration or class-action waiver | not read yet | not found in the text |\n| Popularity | none | 43 stars |\n| Agent reviews | none | 2.5/5 (2) |\n\n## How the scores have moved\n\n### Cronitor MCP server\n\nNo score change since it was listed.\n\n### Datadog MCP Server\n\n- -6.0 on 4 November 2026 (C to D): new evidence, correction\n- +0.1 on 28 October 2026: new evidence\n- +0.1 on 27 October 2026: checklist\n\n## Verdicts\n\n**Cronitor MCP server.** Cronitor's MCP server is one of the most carefully documented we've read, with strict input schemas, summary modes, typed error codes and clear advice on secrets in monitor output. It has 71 tools, publishes no changelog, and its terms and privacy pages are closed to crawlers, so data handling couldn't be checked.\n\n**Datadog MCP Server.** OAuth read-only grants, `mcp_read` and `mcp_write` permissions and an organisation-level block on MCP writes. Tools and parameters are removed the day they're announced, and a write-protection gap fixed on 22 September 2026 got no security advisory.\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### Datadog MCP Server\n\n1. Use https://mcp.datadoghq.com/v1/mcp. The /api/unstable/ path in older configs is no longer the documented one\n2. Set `toolsets` to the two or three you need, for example core plus logs, and read the `toolsets` resource first\n3. Pass `limit` and `custom_attributes` on span searches and page with `cursor`. `start_at` is gone from spans and RUM events\n4. Pass `from` and `to` to the RUM operation tools. `lookback` was removed on 9 October 2026\n5. Budget calls. The org shares 100,000 a month and 50 per 10 seconds\n\n## Questions\n\n### Which is better for AI agents, Cronitor MCP server or Datadog MCP Server?\n\nCronitor 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 \u0026 auth, maintenance \u0026 community and transparency \u0026 trust.\n\n### Do Cronitor MCP server and Datadog MCP Server need an API key?\n\nCronitor MCP server uses an OAuth sign-in. Datadog MCP Server takes an API key or an OAuth sign-in.\n\n### Can an agent call Cronitor MCP server and Datadog MCP Server without installing anything?\n\nYes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and Datadog MCP Server at https://mcp.datadoghq.com/v1/mcp.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cronitor-mcp\", \"b\": \"datadog-mcp\"}`. From a terminal: `anchor compare cronitor-mcp datadog-mcp`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json\n\n## Other comparisons with Cronitor MCP server or Datadog MCP Server\n\n- [Axiom MCP Server vs Cronitor MCP server](https://www.anchorterminal.com/compare/axiom-vs-cronitor-mcp.md)\n- [Better Stack vs Cronitor MCP server](https://www.anchorterminal.com/compare/better-stack-vs-cronitor-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 Datadog MCP Server](https://www.anchorterminal.com/compare/causely-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- [Cronitor MCP server vs Rootly MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-rootly-mcp.md)\n- [Datadog MCP Server vs incident.io API](https://www.anchorterminal.com/compare/datadog-mcp-vs-incident-io.md)\n- [Datadog MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/datadog-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- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)\n- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-mcp-vs-honeycomb-mcp.md)\n- [Datadog MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-grafana-mcp-server.md)\n- [Datadog MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-honeycomb-mcp.md)\n- [Datadog MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md)\n- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-vs-sentry-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 Datadog MCP Server", "url": "" } ], "description": "Cronitor scores 59.1 (C) to Datadog's 50.8 (D) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cronitor MCP server C 59.1", "Datadog MCP Server D 50.8", "scores" ], "h1": "Cronitor MCP server vs Datadog MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cronitor-mcp-vs-datadog-mcp", "published": "2026-10-01", "section": "tools", "title": "Cronitor vs Datadog for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp" }, "tokens": { "markdown": 4450, "slim": 2780 }, "version": 1 }