{ "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": "New Relic MCP Server scores 61 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "b": { "slug": "new-relic", "name": "New Relic MCP Server", "vendor": "New Relic, Inc.", "vendorUrl": "https://newrelic.com", "kind": "mcp", "category": "observability", "summary": "New Relic's hosted MCP server at mcp.newrelic.com gives AI agents read access to an account's entities, NRQL data, alerts, issues, logs, errors, traces and deployments, with OAuth or a user API key, on top of the NerdGraph API.", "url": "https://www.anchorterminal.com/tools/new-relic", "markdownUrl": "https://www.anchorterminal.com/tools/new-relic.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/new-relic.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/new-relic.json", "dns": "new-relic.grade.anchorterminal.com", "repo": "https://github.com/newrelic/nr-skills-hub", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.newrelic.com/mcp/", "packages": [], "auth": "oauth", "authNotes": "OAuth 2.0 (recommended) with scopes `observability:read`, `offline` and `offline_access`; access tokens expire after 5 minutes and are refreshed, with sign-in again after 24 hours. Or a user API key (`NRAK-...`) in an `api-key` header, which the docs say only works where stated and excludes the AI analysis, gap and preview tools. An administrator must leave the MCP toggles on in feature control manager and the user needs an organisation-scoped read role. EU and JP accounts use mcp.eu.newrelic.com and mcp.jp.newrelic.com.", "pricing": "freemium", "pricingNotes": "MCP is available on every New Relic account, including the free tier (100 GB of ingest a month, one full platform user, no card). Most tools are metered as Core Compute Units against the account's allocation and four AI analysis tools as Advanced Compute Units; no per-call price is published. Data beyond 100 GB costs $0.40 per GB; user and edition prices are quoted on request (https://newrelic.com/pricing).", "priceSummary": "$0.40 / GB", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, pricing page or terms (checked 2026-11-03). MCP calls are metered as compute units on the account's bill.", "endpoints": [] }, "toolCount": 40, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://docs.newrelic.com/docs/agentic-ai/mcp/overview/", "llmsTxt": "https://docs.newrelic.com/llms.txt", "registryName": "com.newrelic/mcp-server", "capabilities": [ "observability.metrics", "observability.logs", "observability.errors", "observability.traces", "observability.incidents" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "mcp-registry", "oauth", "read-only-mode", "llms-txt", "status-page", "security-txt", "bug-bounty", "soc2", "eu-region", "closed-source" ], "lastRelease": "2026-10-28", "graded": true, "anchor": { "graded": true, "score": 61, "grade": "C", "agentReady": false, "rank": 630, "ranked": true, "rankOf": 1510, "categoryRank": 5, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 59, "maintenance": 80, "payments": 30, "reliability": 60, "schema": 51, "security": 76, "transparency": 81 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found.", "bestFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.", "strengths": [ "OAuth 2.0 with `observability:read`, access tokens that expire after 5 minutes, revocation by user or organisation toggle, and every call bound to the user's roles", "`include-tags` header limits the 40 tools to the groups a task needs, such as `discovery,alerting`", "Sign-ins and NRQL sent through the server are queryable in NrAuditEvent and NrdbQuery with a product label", "Available on the free tier (100 GB a month, no card) and rate-limited at a published 2,000 tool calls an hour per user", "llms.txt and Markdown twins of every docs page, a dated what's-new feed and a verified registry namespace" ], "weaknesses": [ "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters", "40 tools in the default list, above the 30-tool line, unless the client sends `include-tags`", "No per-call price; tools are metered as Core and Advanced Compute Units on the account's bill", "Public preview since 4 November 2025 with no dated general availability notice found, and preview tools mixed into the list", "Logs, errors and traces come back as untrusted text with no prompt-injection guidance; the trust centre renders through a script our reader can't run" ], "agentNotes": [ "Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated", "Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30", "Call `list_available_new_relic_accounts` first and pass the account id to every query; `convert_time_period_to_epoch_ms` turns phrases such as last 30 minutes into the epoch bounds the other tools take", "Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish", "Ask the organisation administrator to turn on the Preview Tools, API Keys, Atlassian or AWS toggles in feature control manager before relying on those tools; they are off by default" ], "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": 61 } ], "editorialScores": { "ergonomics": 59, "maintenance": 80, "payments": 30, "reliability": 60, "schema": 51, "security": 76, "transparency": 63 }, "provenanceScore": 98, "checked": { "categories": { "ergonomics": "2026-11-03", "maintenance": "2026-11-03", "payments": "2026-11-03", "reliability": "2026-11-03", "schema": "2026-11-03", "security": "2026-11-03", "transparency": "2026-11-03" }, "last": "2026-11-03", "oldest": "2026-11-03", "stale": false, "staleAfterDays": 90 } }, "connect": { "claudeCode": "claude mcp add --transport http --scope user newrelic https://mcp.newrelic.com/mcp/", "config": { "mcpServers": { "newrelic": { "type": "http", "url": "https://mcp.newrelic.com/mcp/" } } } }, "letme": { "capability": "https://letme.dev/observability.metrics", "tool": "https://letme.dev/new-relic" }, "area": "developer", "unitPrices": [ { "item": "Data ingest beyond 100 GB a month", "unit": "gb", "usd": 0.4, "note": "100 GB a month free on every edition. User and compute prices are quoted on request" } ], "provenance": { "legalEntity": "New Relic, Inc.", "domain": "newrelic.com", "domainRegistered": "2006-04-19", "endpointOnVendorDomain": true, "terms": "https://newrelic.com/termsandconditions/paid", "privacy": "https://newrelic.com/termsandconditions/privacy", "statusPage": "https://status.newrelic.com", "changelog": "https://docs.newrelic.com/whats-new/", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The paid terms of service are dated 8 November 2022 and the unpaid terms 21 October 2021; the master cloud agreement path is disallowed by newrelic.com/robots.txt and wasn't read. The privacy notice is dated 14 September 2026.", "newrelic.com/robots.txt disallows /signup/, /lp/, the master cloud agreement and a few files; /security redirected to trust.newrelic.com, which renders through a script and was not readable. docs.newrelic.com allows everything.", "security.txt at newrelic.com/.well-known/security.txt points to HackerOne for contact and policy.", "status.newrelic.com is an Atlassian Statuspage with 115 components across US, EU and JP; the history page needs JavaScript, so the 90-day record was read from history.rss, which holds 25 incidents back to 12 January 2026.", "RDAP gives newrelic.com a registration date of 19 April 2006. firstReleased is 4 November 2025, the public preview date of the MCP server." ], "score": 98 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/new-relic.json", "live": { "slug": "new-relic", "probe": { "target": "https://mcp.newrelic.com/mcp/", "method": "mcp-initialize", "lastAt": "2026-11-08T00:55:53.783788938Z", "lastOk": true, "lastStatus": 401, "lastMs": 374, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 303, "p95ms24h": 379, "samples24h": 244, "samples30d": 766, "days": [ { "date": "2026-11-04", "probes": 87, "ok": 87 }, { "date": "2026-11-05", "probes": 185, "ok": 185 }, { "date": "2026-11-06", "probes": 241, "ok": 241 }, { "date": "2026-11-07", "probes": 243, "ok": 243 }, { "date": "2026-11-08", "probes": 10, "ok": 10 } ] }, "vendorStatus": { "page": "https://status.newrelic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-08T00:55:08.242113514Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.newrelic/mcp-server", "version": "0.1.0", "seenAt": "2026-11-07T18:16:28.95801333Z" } ], "githubStars": 7, "securityTxt": { "url": "https://newrelic.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-07T16:00:05.381425501Z" }, "llmsTxt": { "url": "https://docs.newrelic.com/llms.txt", "ok": true, "status": 200, "checkedAt": "2026-11-07T15:33:19.490458286Z" }, "pages": [ { "url": "https://docs.newrelic.com/whats-new/", "kind": "changelog", "status": 200, "checkedAt": "2026-11-07T14:07:08.149209515Z", "changedAt": "2026-11-06T13:29:28.317089596Z", "fingerprint": "0dad7face61b" }, { "url": "https://newrelic.com/pricing", "kind": "pricing", "status": 304, "checkedAt": "2026-11-07T14:14:57.685712467Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "7b9eabbb1214" }, { "url": "https://newrelic.com/termsandconditions/privacy", "kind": "privacy", "status": 304, "checkedAt": "2026-11-07T14:15:01.695012996Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "2b25c71fe313" }, { "url": "https://newrelic.com/termsandconditions/paid", "kind": "terms", "status": 304, "checkedAt": "2026-11-07T14:14:59.72324771Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "c66b7d0f3973" } ], "mcpTools": { "url": "https://mcp.newrelic.com/mcp/", "checkedAt": "2026-11-07T01:46:24.779111055Z", "status": "auth", "note": "asks for credentials before listing its tools", "changedAt": "2026-11-05T01:29:27.984114072Z" }, "updatedAt": "2026-11-08T00:55:53.783788938Z" } }, "edges": [ { "by": 44, "category": "transparency", "leads": "new-relic", "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": "Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc. (15). A privacy notice of 14 September 2026, a data retention page with per-namespace periods, a security policy, and the MCP docs' statement that gap-analysis responses aren't stored; the master cloud agreement and the trust centre couldn't be read (22). End-of-life notices with dates (REST API keys, 2025) and a pre-release policy that says preview services can change or end (16). US, EU and JP regions are documented for the server and the platform, but no sub-processor list was found on a readable page (10). 15 + 22 + 16 + 10 = 63." }, "scores": { "a": 37, "b": 81 } }, { "by": 29, "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 input schemas are only visible through an authenticated session; the tool reference names 40 tools with one-line descriptions, so partial credit for a contract that exists but isn't public (10). docs.newrelic.com publishes llms.txt, updated 3 November 2026, and a Markdown twin of every page (10). Each tool's line says what it does, tags say which group it belongs to, and the reference says which tools need OAuth and which are preview; nothing says when not to use a tool (12). No parameters, types or enums are published; the setup examples show only the `include-tags` header (4). Example natural-language queries per group, a troubleshooting page for OAuth, API key, permission and connection errors, and no error code list (7). A dated what's-new feed and a 0.1.0 registry version, but no MCP changelog or server version in the docs (8). 10 + 10 + 12 + 4 + 7 + 8 = 51." }, "scores": { "a": 80, "b": 51 } }, { "by": 25, "category": "maintenance", "leads": "new-relic", "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": "Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80." }, "scores": { "a": 55, "b": 80 } }, { "by": 18, "category": "security", "leads": "new-relic", "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 the scopes `observability:read`, `offline` and `offline_access`, access tokens that expire after 5 minutes, refresh for 24 hours, revocation by deleting the user or turning off the organisation toggle, and the token acting as the user with no more than their roles; the alternative is a user API key in a header (28). A read scope, organisation toggles that default the API key, preview, Atlassian and AWS routes to off, an organisation-scoped role requirement, and no write tools in the list (16). Logs, error messages and trace attributes are untrusted text and no injection guidance was found (2). NrAuditEvent records sign-ins with IP addresses and NrdbQuery labels queries sent through the server, both queryable by the operator (13). security.txt pointing to a HackerOne programme, a published security policy citing SOC 2 Type 2 and ISO 27001 audits of its facilities and its own penetration testing, and an ISO 42001 certification announced on 29 September 2026; the trust centre itself renders through a script and was unread (17). 28 + 16 + 2 + 13 + 17 = 76." }, "scores": { "a": 58, "b": 76 } }, { "by": 14, "category": "ergonomics", "leads": "cronitor-mcp", "name": "Agent ergonomics", "reasons": { "a": "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.", "b": "40 tools in the default list, above the 30-tool line (5), with the `include-tags` header to load only named groups (add 10, so 15). Time windows on most tools, `convert_time_period_to_epoch_ms`, filters on incidents, errors and logs, and NRQL's own LIMIT and FACET; no documented page size (14). The troubleshooting page covers setup errors with fixes, and the docs say nothing about tool-level error bodies (8). Every tool is a read (query, list, fetch, analyse) and the gap tool reads files the client sends, so a retry is safe; no readOnlyHint or destructiveHint was confirmed because tools/list wasn't read (12). Natural-language prompts need no parameters from the user, and the API behind the server has official NerdGraph clients; nothing agent-specific beyond skills (10). 15 + 14 + 8 + 12 + 10 = 59." }, "scores": { "a": 73, "b": 59 } }, { "by": 10, "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). The pricing page is public for the free tier and data ingest ($0.40 per GB beyond 100 GB), but MCP tools are metered as compute units with no per-call rate, and user and edition prices are quoted on request (10). The free tier includes MCP, 100 GB a month and one full platform user with no card (20). A person signs up in a browser and completes the OAuth flow (0). 0 + 10 + 20 + 0 = 30." }, "scores": { "a": 40, "b": 30 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Cronitor", "b": "New Relic, Inc.", "name": "Vendor" }, { "a": "https://cronitor.io/mcp", "b": "https://mcp.newrelic.com/mcp/", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "71", "b": "40", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "io.cronitor/cronitor", "b": "com.newrelic/mcp-server", "name": "MCP registry" }, { "a": "none", "b": "2026-10-28", "name": "Last release" }, { "a": "no document linked", "b": "2022-11-08", "name": "Terms last updated" }, { "a": "no document linked", "b": "2026-09-14", "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": "yes", "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" } ], "faq": [ { "answer": "New Relic MCP Server scores 61 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.", "question": "Which is better for AI agents, Cronitor MCP server or New Relic MCP Server?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Cronitor MCP server and New Relic MCP Server need an API key?" }, { "answer": "Yes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and New Relic MCP Server at https://mcp.newrelic.com/mcp/.", "question": "Can an agent call Cronitor MCP server and New Relic MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 80 against 51", "Agent ergonomics, 73 against 59", "Payments \u0026 pricing, 40 against 30" ], "also": null, "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": [ "Reliability, 60 against 55", "Security \u0026 auth, 76 against 58", "Maintenance \u0026 community, 80 against 55", "Transparency \u0026 trust, 81 against 37" ], "also": [ "Free to start without a card" ], "goodFor": "Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.", "slug": "new-relic", "watchFor": "Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters" } ], "history": null, "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-new-relic.json", "title": "Causely MCP server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/causely-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.json", "title": "Cronitor MCP server vs Datadog MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.json", "title": "Cronitor MCP server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.json", "title": "Cronitor MCP server vs incident.io API", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-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/incident-io-vs-new-relic.json", "title": "incident.io API vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/incident-io-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.json", "title": "New Relic MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.json", "title": "New Relic MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.json", "title": "Axiom MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.json", "title": "Better Stack vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic" }, { "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-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/grafana-mcp-server-vs-new-relic.json", "title": "Grafana MCP Server vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic" }, { "json": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.json", "title": "New Relic MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp" }, { "json": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.json", "title": "Honeycomb MCP vs New Relic MCP Server", "url": "https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic" } ], "panel": null, "scores": [ { "by": 5, "cronitor-mcp": 55, "edge": "new-relic", "key": "reliability", "name": "Reliability", "new-relic": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 29, "cronitor-mcp": 80, "edge": "cronitor-mcp", "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "weight": 13 }, { "by": 14, "cronitor-mcp": 73, "edge": "cronitor-mcp", "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "weight": 13 }, { "by": 18, "cronitor-mcp": 58, "edge": "new-relic", "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "weight": 14 }, { "by": 10, "cronitor-mcp": 40, "edge": "cronitor-mcp", "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 25, "cronitor-mcp": 55, "edge": "new-relic", "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "weight": 7 }, { "by": 44, "cronitor-mcp": 37, "edge": "new-relic", "key": "transparency", "name": "Transparency \u0026 trust", "new-relic": 81, "weight": 7 } ], "summary": "New Relic MCP Server scores 61 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. 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.", "new-relic": "OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found." } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic", "json": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.min.md" }, "markdown": "New Relic MCP Server scores 61 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing. 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- New Relic MCP Server: grade C, 61/100, rank #630 of 1510. Markdown https://www.anchorterminal.com/tools/new-relic.md · JSON https://www.anchorterminal.com/api/v1/tools/new-relic.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- Schema \u0026 documentation, 80 against 51\n- Agent ergonomics, 73 against 59\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: 71 tools, a heavy context load\n\n### New Relic MCP Server (C)\n\nGood for: Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough.\n\nAhead on:\n- Reliability, 60 against 55\n- Security \u0026 auth, 76 against 58\n- Maintenance \u0026 community, 80 against 55\n- Transparency \u0026 trust, 81 against 37\n\nAlso in its favour:\n- Free to start without a card\n\nWatch for: Tool input schemas are visible only through an authenticated session; the docs give one-line descriptions and no parameters\n\n\n## Why the edge\n\n### Transparency \u0026 trust: New Relic MCP Server +44\n\n- Cronitor MCP server (37): robots.txt disallows the terms and privacy pages, so neither was read (5 of 30, terms exist but weren't readable). Data handling only from the security page (encryption, backups) (10 of 30). No deprecation policy found; the docs version the error codes by protocol revision (5 of 20). Subprocessors not found (5 of 20). 5 + 10 + 5 + 5 = 25.\n- New Relic MCP Server (81): Closed service with clear dated terms (paid 8 November 2022, unpaid 21 October 2021) naming New Relic, Inc. (15). A privacy notice of 14 September 2026, a data retention page with per-namespace periods, a security policy, and the MCP docs' statement that gap-analysis responses aren't stored; the master cloud agreement and the trust centre couldn't be read (22). End-of-life notices with dates (REST API keys, 2025) and a pre-release policy that says preview services can change or end (16). US, EU and JP regions are documented for the server and the platform, but no sub-processor list was found on a readable page (10). 15 + 22 + 16 + 10 = 63.\n\n### Schema \u0026 documentation: Cronitor MCP server +29\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- New Relic MCP Server (51): Tool input schemas are only visible through an authenticated session; the tool reference names 40 tools with one-line descriptions, so partial credit for a contract that exists but isn't public (10). docs.newrelic.com publishes llms.txt, updated 3 November 2026, and a Markdown twin of every page (10). Each tool's line says what it does, tags say which group it belongs to, and the reference says which tools need OAuth and which are preview; nothing says when not to use a tool (12). No parameters, types or enums are published; the setup examples show only the `include-tags` header (4). Example natural-language queries per group, a troubleshooting page for OAuth, API key, permission and connection errors, and no error code list (7). A dated what's-new feed and a 0.1.0 registry version, but no MCP changelog or server version in the docs (8). 10 + 10 + 12 + 4 + 7 + 8 = 51.\n\n### Maintenance \u0026 community: New Relic MCP Server +25\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- New Relic MCP Server (80): Read as a closed service. The what's-new feed and press releases record changes through October 2026, the latest on 28 October (Change Tracking in GitHub Copilot), and docs llms.txt was regenerated on 3 November (30). More than three dated entries in 90 days, among them the Ground Truth CLI on 6 October, the CEO appointment on 1 October, OpenTelemetry AI monitoring in August and the ISO 42001 announcement (20). A support portal, in-app support and a community forum; the skills hub repository on GitHub, whose issue replies couldn't be read (10 of 15). com.newrelic/mcp-server in the official registry since 28 October 2025 under a DNS-verified namespace, still at 0.1.0 (15). No package to assess for a hosted server; NerdGraph has official clients (5). 30 + 20 + 10 + 15 + 5 = 80.\n\n### Security \u0026 auth: New Relic 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- New Relic MCP Server (76): OAuth 2.0 with the scopes `observability:read`, `offline` and `offline_access`, access tokens that expire after 5 minutes, refresh for 24 hours, revocation by deleting the user or turning off the organisation toggle, and the token acting as the user with no more than their roles; the alternative is a user API key in a header (28). A read scope, organisation toggles that default the API key, preview, Atlassian and AWS routes to off, an organisation-scoped role requirement, and no write tools in the list (16). Logs, error messages and trace attributes are untrusted text and no injection guidance was found (2). NrAuditEvent records sign-ins with IP addresses and NrdbQuery labels queries sent through the server, both queryable by the operator (13). security.txt pointing to a HackerOne programme, a published security policy citing SOC 2 Type 2 and ISO 27001 audits of its facilities and its own penetration testing, and an ISO 42001 certification announced on 29 September 2026; the trust centre itself renders through a script and was unread (17). 28 + 16 + 2 + 13 + 17 = 76.\n\n### Agent ergonomics: Cronitor MCP server +14\n\n- 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.\n- New Relic MCP Server (59): 40 tools in the default list, above the 30-tool line (5), with the `include-tags` header to load only named groups (add 10, so 15). Time windows on most tools, `convert_time_period_to_epoch_ms`, filters on incidents, errors and logs, and NRQL's own LIMIT and FACET; no documented page size (14). The troubleshooting page covers setup errors with fixes, and the docs say nothing about tool-level error bodies (8). Every tool is a read (query, list, fetch, analyse) and the gap tool reads files the client sends, so a retry is safe; no readOnlyHint or destructiveHint was confirmed because tools/list wasn't read (12). Natural-language prompts need no parameters from the user, and the API behind the server has official NerdGraph clients; nothing agent-specific beyond skills (10). 15 + 14 + 8 + 12 + 10 = 59.\n\n### Payments \u0026 pricing: Cronitor MCP server +10\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- New Relic MCP Server (30): No x402, MPP or L402 (0). The pricing page is public for the free tier and data ingest ($0.40 per GB beyond 100 GB), but MCP tools are metered as compute units with no per-call rate, and user and edition prices are quoted on request (10). The free tier includes MCP, 100 GB a month and one full platform user with no card (20). A person signs up in a browser and completes the OAuth flow (0). 0 + 10 + 20 + 0 = 30.\n\n## Score by category\n\n| Category | Weight | Cronitor MCP server | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 55 | 60 | New Relic MCP Server +5 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 80 | 51 | Cronitor MCP server +29 |\n| Agent ergonomics | 13% (16.2 this run) | 73 | 59 | Cronitor MCP server +14 |\n| Security \u0026 auth | 14% (17.5 this run) | 58 | 76 | New Relic MCP Server +18 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Cronitor MCP server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 55 | 80 | New Relic MCP Server +25 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 37 | 81 | New Relic MCP Server +44 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **59.1 · C** | **61 · C** | |\n\n## Facts side by side\n\n| Fact | Cronitor MCP server | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Cronitor | New Relic, Inc. |\n| Hosted endpoint | `https://cronitor.io/mcp` | `https://mcp.newrelic.com/mcp/` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 71 | 40 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `io.cronitor/cronitor` | `com.newrelic/mcp-server` |\n| Last release | none | 2026-10-28 |\n| Terms last updated | no document linked | 2022-11-08 |\n| Privacy policy last updated | no document linked | 2026-09-14 |\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 | yes |\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\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**New Relic MCP Server.** OAuth with a read scope, 5-minute access tokens, role-bound calls and a queryable audit trail make this a safe read surface over an account's data, and the free tier includes it. 40 tools need tag filtering, the schemas aren't public, there is no per-call price, and no dated GA notice was found.\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### New Relic MCP Server\n\n1. Connect with OAuth; an `api-key` header reaches only the core tools and the docs say the API key route works only where stated\n2. Send `include-tags` with the groups the task needs (for example `discovery,data-access`) to keep the tool list under 30\n3. Call `list_available_new_relic_accounts` first and pass the account id to every query; `convert_time_period_to_epoch_ms` turns phrases such as last 30 minutes into the epoch bounds the other tools take\n4. Stay under 2,000 tool calls an hour per user and 25 concurrent NerdGraph requests; a 429 clears as in-flight requests finish\n5. Ask the organisation administrator to turn on the Preview Tools, API Keys, Atlassian or AWS toggles in feature control manager before relying on those tools; they are off by default\n\n## Questions\n\n### Which is better for AI agents, Cronitor MCP server or New Relic MCP Server?\n\nNew Relic MCP Server scores 61 (C) on agent readiness against Cronitor MCP server's 59.1 (C), and leads in 4 of 7 scored categories. Cronitor MCP server leads on schema \u0026 documentation, agent ergonomics and payments \u0026 pricing.\n\n### Do Cronitor MCP server and New Relic MCP Server need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Cronitor MCP server and New Relic MCP Server without installing anything?\n\nYes. Cronitor MCP server has a hosted endpoint at https://cronitor.io/mcp and New Relic MCP Server at https://mcp.newrelic.com/mcp/.\n\n\n## For agents\n\n- This comparison as JSON: https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"cronitor-mcp\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare cronitor-mcp new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/cronitor-mcp.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Cronitor MCP server or New Relic 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 New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.md)\n- [Cronitor MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-datadog-mcp.md)\n- [Cronitor MCP server vs Grafana MCP Server](https://www.anchorterminal.com/compare/cronitor-mcp-vs-grafana-mcp-server.md)\n- [Cronitor MCP server vs incident.io API](https://www.anchorterminal.com/compare/cronitor-mcp-vs-incident-io.md)\n- [Cronitor MCP server vs 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- [incident.io API vs New Relic MCP Server](https://www.anchorterminal.com/compare/incident-io-vs-new-relic.md)\n- [New Relic MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-pagerduty-mcp.md)\n- [New Relic MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/new-relic-vs-rootly-mcp.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md)\n- [Cronitor MCP server vs Honeycomb MCP](https://www.anchorterminal.com/compare/cronitor-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- [Grafana MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/grafana-mcp-server-vs-new-relic.md)\n- [New Relic MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/new-relic-vs-sentry-mcp.md)\n- [Honeycomb MCP vs New Relic MCP Server](https://www.anchorterminal.com/compare/honeycomb-mcp-vs-new-relic.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 New Relic MCP Server", "url": "" } ], "description": "New Relic scores 61 (C) to Cronitor's 59.1 (C) for incidents. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Cronitor MCP server C 59.1", "New Relic MCP Server C 61", "scores" ], "h1": "Cronitor MCP server vs New Relic MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/cronitor-mcp-vs-new-relic", "published": "2026-10-01", "section": "tools", "title": "Cronitor vs New Relic for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-07", "url": "https://www.anchorterminal.com/compare/cronitor-mcp-vs-new-relic" }, "tokens": { "markdown": 4350, "slim": 2630 }, "version": 1 }