{ "data": { "a": { "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": 927, "ranked": true, "rankOf": 1349, "categoryRank": 9, "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-04T21:39:20.283754705Z", "lastOk": true, "lastStatus": 401, "lastMs": 268, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 296, "p95ms24h": 378, "samples24h": 247, "samples30d": 8090, "days": [ { "date": "2026-10-04", "probes": 272, "ok": 272 }, { "date": "2026-10-05", "probes": 272, "ok": 272 }, { "date": "2026-10-06", "probes": 272, "ok": 272 }, { "date": "2026-10-07", "probes": 272, "ok": 272 }, { "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": 223, "ok": 223 } ] }, "vendorStatus": { "page": "https://status.datadoghq.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T21:25:40.051543095Z" }, "githubStars": 47, "securityTxt": { "url": "https://datadoghq.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:40.276451403Z" }, "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-04T08:33:14.336962097Z", "changedAt": "0001-01-01T00:00:00Z", "fingerprint": "608f9d788416" }, { "url": "https://datadoghq.com/legal/privacy/", "kind": "privacy", "status": 200, "checkedAt": "2026-11-04T08:17:37.283329879Z", "changedAt": "2026-11-03T07:44:08.283831716Z", "fingerprint": "75cab48d73a2" }, { "url": "https://datadoghq.com/legal/terms/", "kind": "terms", "status": 200, "checkedAt": "2026-11-04T08:17:40.015604906Z", "changedAt": "2026-11-03T07:44:11.02798267Z", "fingerprint": "78e429e0b25a" } ], "mcpTools": { "url": "https://mcp.datadoghq.com/v1/mcp", "checkedAt": "2026-11-04T01:22:28.783780315Z", "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-04T21:39:20.283754705Z" } }, "answer": "New Relic MCP Server scores 61 (C) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 4 of 7 scored categories. Datadog MCP Server leads on schema \u0026 documentation and agent ergonomics.", "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": 567, "ranked": true, "rankOf": 1349, "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-04T21:39:36.212939859Z", "lastOk": true, "lastStatus": 401, "lastMs": 302, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 327, "p95ms24h": 416, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.newrelic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:38:31.653792842Z" }, "versions": [ { "registry": "mcp-registry", "name": "com.newrelic/mcp-server", "version": "0.1.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "githubStars": 7, "securityTxt": { "url": "https://newrelic.com/.well-known/security.txt", "state": "valid", "checkedAt": "2026-11-04T15:54:45.364182842Z" }, "updatedAt": "2026-11-04T21:39:36.212939859Z" } }, "edges": [ { "by": 27, "category": "reliability", "leads": "new-relic", "name": "Reliability", "reasons": { "a": "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.", "b": "Scored as a hosted MCP server. status.newrelic.com is an Atlassian Statuspage with 115 components across the US, EU and JP regions and no MCP component (20). history.rss holds seven incidents in the 90 days to 3 November 2026, among them delayed queries and alerts in the US for 49 minutes on 2 November, synthetics ping delays the same day, the JP entity platform unavailable for 67 minutes on 28 October, delayed US data and alerts from 19:24 to 22:04 UTC on 25 September, intermittent UI errors for two and a half hours the same night, a Salesforce support outage on 16 September and a 10-minute EU metric issue. Two regional incidents over an hour on the query and alert paths the server depends on, so one major (10). Published numbers, 2,000 tool calls an hour per user on the MCP server and 25 concurrent NerdGraph requests per user (15). NerdGraph answers 429 on concurrency with guidance to batch or pool, but no Retry-After is documented and nothing covers retries of MCP calls; the tools are reads, so idempotency doesn't arise (8). The pricing page lists support response SLAs, and the paid terms promise commercially reasonable efforts, so no availability SLA (0). Public preview on 4 November 2025, available to all accounts on 3 November 2026 with preview tools marked separately, but no dated GA notice was found (7). 20 + 10 + 15 + 8 + 0 + 7 = 60." }, "scores": { "a": 33, "b": 60 } }, { "by": 19, "category": "ergonomics", "leads": "datadog-mcp", "name": "Agent ergonomics", "reasons": { "a": "More than 30 toolsets chosen with the `toolsets` parameter, `omit_tools` per the 30 September check, `whoami` and `toolsets` resources, and a core set trimmed by about 15 per cent in March. An `execute_code` toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). `limit`, cursors, `custom_attributes`, token budgets and flattening on aggregates, and `exclude_fields` on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says `execute_code` is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).", "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": 78, "b": 59 } }, { "by": 12, "category": "maintenance", "leads": "new-relic", "name": "Maintenance \u0026 community", "reasons": { "a": "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.", "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": 68, "b": 80 } }, { "by": 12, "category": "transparency", "leads": "new-relic", "name": "Transparency \u0026 trust", "reasons": { "a": "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).", "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": 69, "b": 81 } }, { "by": 10, "category": "payments", "leads": "new-relic", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "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": 20, "b": 30 } }, { "by": 9, "category": "schema", "leads": "datadog-mcp", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "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": 60, "b": 51 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Datadog", "b": "New Relic, Inc.", "name": "Vendor" }, { "a": "https://mcp.datadoghq.com/v1/mcp", "b": "https://mcp.newrelic.com/mcp/", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, stdio", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Your plan", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "MIT", "b": "none", "name": "Licence" }, { "a": "none", "b": "40", "name": "Tools exposed" }, { "a": "yes", "b": "yes", "name": "Read-only variant documented" }, { "a": "no", "b": "yes", "name": "llms.txt" }, { "a": "not listed", "b": "com.newrelic/mcp-server", "name": "MCP registry" }, { "a": "2026-10-16", "b": "2026-10-28", "name": "Last release" }, { "a": "no date given", "b": "2022-11-08", "name": "Terms last updated" }, { "a": "no date given", "b": "2026-09-14", "name": "Privacy policy last updated" }, { "a": "not found in the text", "b": "not found in the text", "name": "Customer content may train models" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms restrict automated access" }, { "a": "not found in the text", "b": "yes", "name": "Terms restrict benchmarking" }, { "a": "not found in the text", "b": "not found in the text", "name": "Terms or service can change without notice" }, { "a": "not found in the text", "b": "not found in the text", "name": "Arbitration or class-action waiver" }, { "a": "43 stars", "b": "none", "name": "Popularity" }, { "a": "2.5/5 (2)", "b": "none", "name": "Agent reviews" } ], "faq": [ { "answer": "New Relic MCP Server scores 61 (C) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 4 of 7 scored categories. Datadog MCP Server leads on schema \u0026 documentation and agent ergonomics.", "question": "Which is better for AI agents, Datadog MCP Server or New Relic MCP Server?" }, { "answer": "Datadog MCP Server takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.", "question": "Do Datadog MCP Server and New Relic MCP Server need an API key?" }, { "answer": "Yes. Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/mcp and New Relic MCP Server at https://mcp.newrelic.com/mcp/.", "question": "Can an agent call Datadog MCP Server and New Relic MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Schema \u0026 documentation, 60 against 51", "Agent ergonomics, 78 against 59" ], "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" }, { "aheadOn": [ "Reliability, 60 against 33", "Payments \u0026 pricing, 30 against 20", "Maintenance \u0026 community, 80 against 68", "Transparency \u0026 trust, 81 against 69" ], "also": [ "Free to start without a card", "No incidents deducted, where Datadog MCP Server loses 6 points for them" ], "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": { "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" } ], "new-relic": null }, "job": { "capability": "observability.metrics", "name": "Metrics and monitoring" }, "others": [ { "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/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/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/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-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/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-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/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/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/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/datadog-mcp-vs-sentry-mcp.json", "title": "Datadog MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/datadog-mcp-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": 27, "datadog-mcp": 33, "edge": "new-relic", "key": "reliability", "name": "Reliability", "new-relic": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "by": 9, "datadog-mcp": 60, "edge": "datadog-mcp", "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "weight": 13 }, { "by": 19, "datadog-mcp": 78, "edge": "datadog-mcp", "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "weight": 13 }, { "by": 0, "datadog-mcp": 76, "edge": "", "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "weight": 14 }, { "by": 10, "datadog-mcp": 20, "edge": "new-relic", "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "by": 12, "datadog-mcp": 68, "edge": "new-relic", "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "weight": 7 }, { "by": 12, "datadog-mcp": 69, "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 Datadog MCP Server's 50.8 (D), and leads in 4 of 7 scored categories. Datadog MCP Server leads on schema \u0026 documentation and agent ergonomics. Both do metrics and monitoring.", "tasks": null, "tutorials": [], "verdicts": { "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.", "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/datadog-mcp-vs-new-relic", "json": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.min.md" }, "markdown": "New Relic MCP Server scores 61 (C) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 4 of 7 scored categories. Datadog MCP Server leads on schema \u0026 documentation and agent ergonomics. Both do metrics and monitoring.\n\n- Datadog MCP Server: grade D, 50.8/100, rank #927 of 1349. Markdown https://www.anchorterminal.com/tools/datadog-mcp.md · JSON https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json\n- New Relic MCP Server: grade C, 61/100, rank #567 of 1349. 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 49 observability comparisons: https://www.anchorterminal.com/compare/observability/index.md\n\n## Which one, for what\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- Schema \u0026 documentation, 60 against 51\n- Agent ergonomics, 78 against 59\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### 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 33\n- Payments \u0026 pricing, 30 against 20\n- Maintenance \u0026 community, 80 against 68\n- Transparency \u0026 trust, 81 against 69\n\nAlso in its favour:\n- Free to start without a card\n- No incidents deducted, where Datadog MCP Server loses 6 points for them\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### Reliability: New Relic MCP Server +27\n\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- New Relic MCP Server (60): Scored as a hosted MCP server. status.newrelic.com is an Atlassian Statuspage with 115 components across the US, EU and JP regions and no MCP component (20). history.rss holds seven incidents in the 90 days to 3 November 2026, among them delayed queries and alerts in the US for 49 minutes on 2 November, synthetics ping delays the same day, the JP entity platform unavailable for 67 minutes on 28 October, delayed US data and alerts from 19:24 to 22:04 UTC on 25 September, intermittent UI errors for two and a half hours the same night, a Salesforce support outage on 16 September and a 10-minute EU metric issue. Two regional incidents over an hour on the query and alert paths the server depends on, so one major (10). Published numbers, 2,000 tool calls an hour per user on the MCP server and 25 concurrent NerdGraph requests per user (15). NerdGraph answers 429 on concurrency with guidance to batch or pool, but no Retry-After is documented and nothing covers retries of MCP calls; the tools are reads, so idempotency doesn't arise (8). The pricing page lists support response SLAs, and the paid terms promise commercially reasonable efforts, so no availability SLA (0). Public preview on 4 November 2025, available to all accounts on 3 November 2026 with preview tools marked separately, but no dated GA notice was found (7). 20 + 10 + 15 + 8 + 0 + 7 = 60.\n\n### Agent ergonomics: Datadog MCP Server +19\n\n- Datadog MCP Server (78): More than 30 toolsets chosen with the `toolsets` parameter, `omit_tools` per the 30 September check, `whoami` and `toolsets` resources, and a core set trimmed by about 15 per cent in March. An `execute_code` toolset runs sandboxed TypeScript against the APIs instead of one tool per call. We couldn't count the default tools (20). `limit`, cursors, `custom_attributes`, token budgets and flattening on aggregates, and `exclude_fields` on Kubernetes manifests (19). The changelog shows a steady effort on actionable errors (15). OAuth read-only grants omit write tools, an org setting blocks MCP writes, and read-only calls retry automatically. The 13 October entry says `execute_code` is now marked read-only so that clients asking approval for write-capable tools classify it correctly, but no entry names readOnlyHint or destructiveHint, so the annotation credit isn't added (12). Official Datadog API clients in several languages and Python agent examples in the repository (12).\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### Maintenance \u0026 community: New Relic MCP Server +12\n\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- 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### Transparency \u0026 trust: New Relic MCP Server +12\n\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- 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### Payments \u0026 pricing: New Relic MCP Server +10\n\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- 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### Schema \u0026 documentation: Datadog MCP Server +9\n\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- 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## Score by category\n\n| Category | Weight | Datadog MCP Server | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 33 | 60 | New Relic MCP Server +27 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 60 | 51 | Datadog MCP Server +9 |\n| Agent ergonomics | 13% (16.2 this run) | 78 | 59 | Datadog MCP Server +19 |\n| Security \u0026 auth | 14% (17.5 this run) | 76 | 76 | even |\n| Payments \u0026 pricing | 10% (12.5 this run) | 20 | 30 | New Relic MCP Server +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 68 | 80 | New Relic MCP Server +12 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 81 | New Relic MCP Server +12 |\n| Negative events | ≤15 | -6 | 0 | |\n| **Total** | | **50.8 · D** | **61 · C** | |\n\n## Facts side by side\n\n| Fact | Datadog MCP Server | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Datadog | New Relic, Inc. |\n| Hosted endpoint | `https://mcp.datadoghq.com/v1/mcp` | `https://mcp.newrelic.com/mcp/` |\n| Transports | Streamable HTTP, stdio | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Your plan | Freemium |\n| x402 | no | no |\n| Licence | MIT | none |\n| Tools exposed | none | 40 |\n| Read-only variant documented | yes | yes |\n| llms.txt | no | yes |\n| MCP registry | not listed | `com.newrelic/mcp-server` |\n| Last release | 2026-10-16 | 2026-10-28 |\n| Terms last updated | no date given | 2022-11-08 |\n| Privacy policy last updated | no date given | 2026-09-14 |\n| Customer content may train models | not found in the text | not found in the text |\n| Terms restrict automated access | not found in the text | not found in the text |\n| Terms restrict benchmarking | not found in the text | yes |\n| Terms or service can change without notice | not found in the text | not found in the text |\n| Arbitration or class-action waiver | not found in the text | not found in the text |\n| Popularity | 43 stars | none |\n| Agent reviews | 2.5/5 (2) | none |\n\n## How the scores have moved\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### New Relic MCP Server\n\nNo score change since it was listed.\n\n## Verdicts\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**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### 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### 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, Datadog MCP Server or New Relic MCP Server?\n\nNew Relic MCP Server scores 61 (C) on agent readiness against Datadog MCP Server's 50.8 (D), and leads in 4 of 7 scored categories. Datadog MCP Server leads on schema \u0026 documentation and agent ergonomics.\n\n### Do Datadog MCP Server and New Relic MCP Server need an API key?\n\nDatadog MCP Server takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.\n\n### Can an agent call Datadog MCP Server and New Relic MCP Server without installing anything?\n\nYes. Datadog MCP Server has a hosted endpoint at https://mcp.datadoghq.com/v1/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/datadog-mcp-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"datadog-mcp\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare datadog-mcp new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/datadog-mcp.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Datadog MCP Server or New Relic MCP Server\n\n- [Causely MCP server vs Datadog MCP Server](https://www.anchorterminal.com/compare/causely-vs-datadog-mcp.md)\n- [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.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- [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 Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-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 Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)\n- [Better Stack vs New Relic MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-new-relic.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- [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- [Datadog MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/datadog-mcp-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-04", "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": "Datadog MCP Server vs New Relic MCP Server", "url": "" } ], "description": "New Relic scores 61 (C) to Datadog's 50.8 (D) for metrics and monitoring. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Datadog MCP Server D 50.8", "New Relic MCP Server C 61", "scores" ], "h1": "Datadog MCP Server vs New Relic MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/datadog-mcp-vs-new-relic", "published": "2026-10-01", "section": "tools", "title": "Datadog vs New Relic for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/datadog-mcp-vs-new-relic" }, "tokens": { "markdown": 5150, "slim": 3280 }, "version": 1 }