{ "data": { "a": { "slug": "better-stack", "name": "Better Stack", "vendor": "Better Stack, Inc.", "vendorUrl": "https://betterstack.com", "kind": "mcp", "category": "observability", "summary": "Better Stack is a hosted observability and incident management service from Better Stack, Inc. with uptime monitors, on-call, status pages, logs, metrics, traces and error tracking, reached through REST APIs and a remote MCP server.", "url": "https://www.anchorterminal.com/tools/better-stack", "markdownUrl": "https://www.anchorterminal.com/tools/better-stack.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/better-stack.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/better-stack.json", "dns": "better-stack.grade.anchorterminal.com", "repo": "https://github.com/BetterStackHQ/claude-plugin", "license": "Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT", "transports": [ "streamable-http" ], "remoteUrl": "https://mcp.betterstack.com", "packages": [], "auth": "mixed", "authNotes": "OAuth sign-in in the browser is the documented default for the MCP server, with a Full access level chosen at consent for writes. Unattended agents send an API token as a Bearer header. Tokens are minted in the web app under API tokens, either global (every team) or team-based (Incidents API or Telemetry API tokens), with Read \u0026 write or read access per the MCP docs. No scopes finer than that and no key expiry were found. Access is self-serve after a browser signup.", "pricing": "freemium", "pricingNotes": "The MCP server and APIs carry no separate charge. The Free plan has 10 monitors and heartbeats, one status page, 3 GB of logs and traces kept 3 days, 30 GB of metrics and 100,000 errors a month, with no card mentioned on the signup page. Responders cost $34 a month ($29 yearly), telemetry is priced per GB by region ($0.10 ingestion and $0.05 retention per GB in Europe, $0.15 and $0.08 in the US, $0.35 and $0.18 in Singapore) or in bundles from $30 a month, and audit logs are a $250 a month add-on (https://betterstack.com/pricing, checked 2026-11-03).", "priceSummary": "$34 / seat-mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the pricing page, the API docs or the MCP docs (checked 2026-11-03). Plans are paid by card through the web app.", "endpoints": [] }, "toolCount": 148, "popularity": { "githubStars": 6, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://betterstack.com/docs/getting-started/integrations/mcp/", "capabilities": [ "observability.logs", "observability.incidents", "work.oncall", "observability.metrics", "observability.traces", "observability.errors" ], "tags": [ "official", "hosted", "closed-source", "mcp", "remote-mcp", "oauth", "api-key", "toolsets", "free-tier", "freemium", "eu-hosted", "status-page", "audit-log", "soc2", "webhooks" ], "lastRelease": "2026-11-02", "graded": true, "anchor": { "graded": true, "score": 54.2, "grade": "C", "agentReady": false, "rank": 811, "ranked": true, "rankOf": 1349, "categoryRank": 7, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 55, "maintenance": 71, "payments": 40, "reliability": 50, "schema": 46, "security": 60, "transparency": 69 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.", "bestFor": "An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.", "strengths": [ "148 tools across incidents, on-call, monitors, heartbeats, status pages, catalogue, telemetry queries, dashboards, alerts, errors and team members, on one remote endpoint", "X-MCP-Tools-Only and X-MCP-Tools-Except headers give a read-only or task-sized subset, and OAuth consent or a token can be read-level", "Audit logs record API token requests with the token's name and the actor type, and can be streamed to a source or any URL", "Free plan with 10 monitors, a status page and 3 GB of logs, and per-GB prices published by region", "Dated changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026, and a plugin release on 2 November 2026" ], "weaknesses": [ "No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying", "The MCP tool schemas are not published, the REST API has no OpenAPI file and the docs have no llms.txt", "No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature", "Delayed Telemetry data processing in the Europe region ran from 3 to 6 September 2026 in entries of 6 hours to 1 day", "Audit logs cost $250 a month, and no security.txt, bug bounty or disclosure policy was found" ], "agentNotes": [ "Connect with `claude mcp add betterstack --transport http https://mcp.betterstack.com` and sign in, or send a team-based API token as `Authorization: Bearer`; pick Read access unless the task writes", "Send `X-MCP-Tools-Only: monitors,monitor,incidents` or a similar list to keep the 148-tool list out of context, and `X-MCP-Tools-Except: remove_dashboard,remove_chart` to block deletes", "Call `Get query instructions` or `Plan query windows` before `Execute query`, since long time ranges are split into windows and nothing documents a result size limit", "No rate limit is published. Back off on a 429 and don't retry writes blindly, because there are no idempotency keys; `Upsert catalog records` is the one write documented as safe to repeat", "Reopening an incident only works within 24 hours of its resolution, and a comment can only be edited or removed by its author or an API token" ], "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": 54.2 } ], "editorialScores": { "ergonomics": 55, "maintenance": 71, "payments": 40, "reliability": 50, "schema": 46, "security": 60, "transparency": 48 }, "provenanceScore": 89, "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": { "http": "curl -H \"Authorization: Bearer $BETTERSTACK_API_TOKEN\" https://incidents.betterstack.com/api/v2/monitors", "claudeCode": "claude mcp add betterstack --transport http https://mcp.betterstack.com", "config": { "mcpServers": { "betterstack": { "type": "http", "url": "https://mcp.betterstack.com" } } }, "headless": { "mcpServers": { "betterstack": { "headers": { "Authorization": "Bearer $TOKEN" }, "type": "http", "url": "https://mcp.betterstack.com" } } } }, "letme": { "capability": "https://letme.dev/observability.logs", "tool": "https://letme.dev/better-stack" }, "area": "developer", "unitPrices": [ { "item": "Responder seat", "unit": "seat-month", "usd": 34, "note": "$29 a month billed yearly; team members without incident access are free" }, { "item": "Logs and traces ingestion, Europe", "unit": "gb", "usd": 0.1, "note": "$0.15 in the US and $0.35 in Singapore, plus retention from $0.05 per GB a month" }, { "item": "Telemetry Nano bundle, Europe", "unit": "month", "usd": 30, "note": "40 GB each of logs, traces and metrics with 30-day retention; $45 in the US" }, { "item": "Additional status page", "unit": "month", "usd": 15, "note": "one page included; $12 billed yearly" }, { "item": "Audit logs add-on", "unit": "month", "usd": 250, "note": "$208 billed yearly" } ], "provenance": { "legalEntity": "Better Stack, Inc.", "domain": "betterstack.com", "domainRegistered": "2013-02-08", "endpointOnVendorDomain": true, "terms": "https://betterstack.com/terms", "privacy": "https://betterstack.com/privacy", "statusPage": "https://status.betterstack.com/", "changelog": "https://betterstack.com/tag/changelog", "securityTxt": "none", "checked": "2026-11-03", "notes": [ "The Terms of Use (last updated 14 February 2025) and the privacy policy (25 November 2022) name Better Stack, Inc., a Delaware corporation, under New York law. The DPA (25 February 2025) and its schedules (14 February 2025) list nine subprocessors.", "The terms contain no clause on automated access to the site or the API. They forbid monitoring systems the user doesn't own and allow Better Stack to impose quotas and time limits.", "betterstack.com/robots.txt disallows nothing and carries Content-Signal search=yes, ai-input=yes, ai-train=yes. status.betterstack.com/robots.txt is empty.", "The MCP server answers at mcp.betterstack.com and the APIs at incidents.betterstack.com, telemetry.betterstack.com and betterstack.com, all vendor subdomains. The ClickHouse query endpoint is on betterstackdata.com.", "betterstack.com/.well-known/security.txt returns 404. The security page gives security@betterstack.com and names no bug bounty or disclosure policy.", "RDAP gives betterstack.com a registration date of 8 February 2013, before the company's 2021 founding per its careers page, so the domain was acquired." ], "score": 89 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/better-stack.json", "live": { "slug": "better-stack", "probe": { "target": "https://mcp.betterstack.com", "method": "mcp-initialize", "lastAt": "2026-11-04T20:46:35.119337454Z", "lastOk": true, "lastStatus": 401, "lastMs": 90, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 195, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://status.betterstack.com", "indicator": "unknown", "summary": "no machine-readable status found", "checkedAt": "2026-11-04T15:31:22.214208643Z" }, "githubStars": 6, "securityTxt": { "url": "https://betterstack.com/.well-known/security.txt", "state": "none", "checkedAt": "2026-11-04T15:52:41.12669976Z" }, "updatedAt": "2026-11-04T20:46:35.119337454Z" } }, "answer": "New Relic MCP Server scores 61 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 6 of 7 scored categories. Better Stack leads on 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": 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-04T20:47:02.571209734Z", "lastOk": true, "lastStatus": 401, "lastMs": 339, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 329, "p95ms24h": 416, "samples24h": 55, "samples30d": 55, "days": [ { "date": "2026-11-04", "probes": 55, "ok": 55 } ] }, "vendorStatus": { "page": "https://status.newrelic.com", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:39:30.94491711Z" }, "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-04T20:47:02.571209734Z" } }, "edges": [ { "by": 16, "category": "security", "leads": "new-relic", "name": "Security \u0026 auth", "reasons": { "a": "OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.", "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": 60, "b": 76 } }, { "by": 12, "category": "transparency", "leads": "new-relic", "name": "Transparency \u0026 trust", "reasons": { "a": "Closed service under Terms of Use (14 February 2025) that name Better Stack, Inc., a Delaware corporation, under New York law. The plugins and Terraform providers are MIT (15 of 30). The privacy policy (25 November 2022) gives no retention periods and says data is processed primarily in the EU, while the DPA (25 February 2025) names the United States and other locations and promises return or destruction on termination. Telemetry retention is a plan term (3 days free, 30 days in bundles). OpenAI is a subprocessor and nothing says whether customer data is used for model training (14 of 30). No deprecation policy. The terms allow changes at Better Stack's discretion with continued use as acceptance, and the changelog carries no deprecation notices (3 of 20). Schedule A of the DPA lists nine subprocessors with locations, the security page says data is stored in EU regions by default with custom locations for enterprise, and no notice period for new subprocessors is given (16 of 20). 15 + 14 + 3 + 16 = 48.", "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": "reliability", "leads": "new-relic", "name": "Reliability", "reasons": { "a": "Read with the hosted lines and scored on the remote MCP server at mcp.betterstack.com, which fronts the same service as the Incidents and Telemetry APIs. status.betterstack.com runs on Better Stack's own status page product with three components and a 90-day history (20). Between 5 August and 3 November 2026 it records delayed Telemetry data processing in the Europe region from 3 to 6 September in entries of 6 hours 19 minutes, 10 hours 10 minutes, 19 hours 13 minutes, 21 hours 45 minutes and 1 day, a 9-minute Telemetry degradation on 20 August, 39 minutes of wrong downtime notifications on 21 October and 8 minutes of dashboard unavailability on 2 November, every one labelled degraded, plus two migrations labelled maintenance (11 hours 13 minutes on 9 August and 17 hours). About four days of delayed log processing in one region is more than trivial and less than an outage of the API, so between minor-only and one major (15). No rate limit numbers were found in the API or MCP docs (0). The Usage API documents a 429 with the instruction to wait before retrying, with no Retry-After, no backoff guidance and no idempotency keys. `Upsert catalog records` is documented as not creating duplicates when repeated (5 of 15). No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature (0). The MCP server was announced on 15 September 2025 and carries no beta label (10). 20 + 15 + 0 + 5 + 0 + 10 = 50.", "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": 50, "b": 60 } }, { "by": 10, "category": "payments", "leads": "better-stack", "name": "Payments \u0026 pricing", "reasons": { "a": "Read with the hosted rubric. No x402, MPP or L402 (0). Per-unit prices are public without login, by GB and region for telemetry, per responder, per status page and per phone number (20). The Free plan has 10 monitors, a status page and 3 GB of logs, the signup page says Sign up for free and names no card, and we did not run the signup flow (20). A person signs up in a browser and mints a token or completes OAuth there (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 } }, { "by": 9, "category": "maintenance", "leads": "new-relic", "name": "Maintenance \u0026 community", "reasons": { "a": "Read as a closed service. The Claude plugin reached 1.3.12 on 2 November 2026 and the changelog's newest entry is 29 October 2026 (30). Changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026 (20). Public changelog, hello@betterstack.com with a stated reply within a few hours, and a community site. GitHub issues on the plugin repositories were not read (10 of 15). The MCP server is not in the official MCP registry under a verified namespace, the only entries matching the name being third-party scrapers, and there is no official API SDK. The Claude, Cursor, Codex and Antigravity plugins and two Terraform providers are current (5 of 15). The Claude plugin repository is MIT with 12 commit days since June 2026, and we didn't read its CI (6 of 10). 30 + 20 + 10 + 5 + 6 = 71.", "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": 71, "b": 80 } }, { "by": 5, "category": "schema", "leads": "new-relic", "name": "Schema \u0026 documentation", "reasons": { "a": "The server is closed and tools/list needs sign-in, so the tool schemas were not read, and no OpenAPI file was found for the REST APIs in the docs, the GitHub organisation or a search. Partial credit for a typed contract that exists but isn't public (10 of 25). No llms.txt on betterstack.com or its docs, and no Markdown twins (0). The MCP docs page gives one line per tool and says when some apply, such as Reopen incident within 24 hours and the instruction tools to call before Execute query. The REST reference pages describe each endpoint in a sentence (12 of 20). Inputs are typed only in the REST docs, with parameter tables, monitor types and status values listed in prose, and no schema to validate against (7 of 15). Every REST page carries a curl example and a 200 body; Create monitor documents a 422 with errors keyed by field, the Usage API a 401 and a 429, and no error code list exists (9 of 15). The APIs are versioned v2 in the path. The changelog is a product feed of 19 entries since March 2025 with the MCP server among them, with no API changelog and no deprecation notes (8 of 15). 10 + 0 + 12 + 7 + 9 + 8 = 46.", "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": 46, "b": 51 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Better Stack, Inc.", "b": "New Relic, Inc.", "name": "Vendor" }, { "a": "https://mcp.betterstack.com", "b": "https://mcp.newrelic.com/mcp/", "name": "Hosted endpoint" }, { "a": "Streamable HTTP", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth or key", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "$0.10 per GB of traffic", "b": "not published", "name": "Price for observability logs" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT", "b": "none", "name": "Licence" }, { "a": "148", "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-11-02", "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": "6 stars", "b": "none", "name": "Popularity" } ], "faq": [ { "answer": "New Relic MCP Server scores 61 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 6 of 7 scored categories. Better Stack leads on payments \u0026 pricing.", "question": "Which is better for AI agents, Better Stack or New Relic MCP Server?" }, { "answer": "Better Stack takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.", "question": "Do Better Stack and New Relic MCP Server need an API key?" }, { "answer": "Yes. Better Stack has a hosted endpoint at https://mcp.betterstack.com and New Relic MCP Server at https://mcp.newrelic.com/mcp/.", "question": "Can an agent call Better Stack and New Relic MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Payments \u0026 pricing, 40 against 30" ], "also": null, "goodFor": "An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.", "slug": "better-stack", "watchFor": "No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying" }, { "aheadOn": [ "Reliability, 60 against 50", "Schema \u0026 documentation, 51 against 46", "Security \u0026 auth, 76 against 60", "Maintenance \u0026 community, 80 against 71", "Transparency \u0026 trust, 81 against 69" ], "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.logs", "name": "Observability logs" }, "others": [ { "json": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io.json", "title": "Better Stack vs incident.io API", "url": "https://www.anchorterminal.com/compare/better-stack-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.json", "title": "Better Stack vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.json", "title": "Better Stack vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-rootly-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/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-better-stack.json", "title": "Axiom MCP Server vs Better Stack", "url": "https://www.anchorterminal.com/compare/axiom-vs-better-stack" }, { "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-causely.json", "title": "Better Stack vs Causely MCP server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-causely" }, { "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-grafana-mcp-server.json", "title": "Better Stack vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/better-stack-vs-honeycomb-mcp.json", "title": "Better Stack vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/better-stack-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/better-stack-vs-sentry-mcp.json", "title": "Better Stack vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp" }, { "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": [ { "better-stack": 50, "by": 10, "edge": "new-relic", "key": "reliability", "name": "Reliability", "new-relic": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "better-stack": 46, "by": 5, "edge": "new-relic", "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "weight": 13 }, { "better-stack": 55, "by": 4, "edge": "new-relic", "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "weight": 13 }, { "better-stack": 60, "by": 16, "edge": "new-relic", "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "weight": 14 }, { "better-stack": 40, "by": 10, "edge": "better-stack", "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "better-stack": 71, "by": 9, "edge": "new-relic", "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "weight": 7 }, { "better-stack": 69, "by": 12, "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 Better Stack's 54.2 (C), and leads in 6 of 7 scored categories. Better Stack leads on payments \u0026 pricing. Both do observability logs.", "tasks": null, "tutorials": [], "verdicts": { "better-stack": "One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.", "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/better-stack-vs-new-relic", "json": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic.min.md" }, "markdown": "New Relic MCP Server scores 61 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 6 of 7 scored categories. Better Stack leads on payments \u0026 pricing. Both do observability logs.\n\n- Better Stack: grade C, 54.2/100, rank #811 of 1349. Markdown https://www.anchorterminal.com/tools/better-stack.md · JSON https://www.anchorterminal.com/api/v1/tools/better-stack.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### Better Stack (C)\n\nGood for: An agent that investigates incidents, queries logs and metrics with SQL, manages monitors and posts status page updates for a team already on Better Stack, with the Claude plugin as the shortest route.\n\nAhead on:\n- Payments \u0026 pricing, 40 against 30\n\nWatch for: No rate limit numbers in the API docs, and the only 429 guidance is to wait before retrying\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 50\n- Schema \u0026 documentation, 51 against 46\n- Security \u0026 auth, 76 against 60\n- Maintenance \u0026 community, 80 against 71\n- Transparency \u0026 trust, 81 against 69\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### Security \u0026 auth: New Relic MCP Server +16\n\n- Better Stack (60): OAuth sign-in with a Full access level chosen at consent, or API tokens that are global or scoped to one team with Read \u0026 write or read access, minted and deleted in Settings. No scopes finer than read and write, no expiry and no PKCE or dynamic registration documented (24 of 30). Read-level tokens and consent, the two header allowlists, and the rule that comments can only be changed by their author or a token. No confirmation step before Remove monitor, Remove dashboard, Resolve incident or Remove team member (12 of 20). Logs, spans, errors and replays are untrusted text returned to the model, and no injection guidance was found in the MCP docs (2 of 15). Audit logs record every API token request with actor_type api_token and the token's name, never its value, and can be streamed to a Telemetry source or any URL, though the pricing page lists audit logs as a $250 a month add-on (12 of 15). SOC 2 Type 2 with the report on request, third-party penetration tests, security@betterstack.com for disclosures. No security.txt (404), no bug bounty and no disclosure policy page (10 of 20). 24 + 12 + 2 + 12 + 10 = 60.\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### Transparency \u0026 trust: New Relic MCP Server +12\n\n- Better Stack (69): Closed service under Terms of Use (14 February 2025) that name Better Stack, Inc., a Delaware corporation, under New York law. The plugins and Terraform providers are MIT (15 of 30). The privacy policy (25 November 2022) gives no retention periods and says data is processed primarily in the EU, while the DPA (25 February 2025) names the United States and other locations and promises return or destruction on termination. Telemetry retention is a plan term (3 days free, 30 days in bundles). OpenAI is a subprocessor and nothing says whether customer data is used for model training (14 of 30). No deprecation policy. The terms allow changes at Better Stack's discretion with continued use as acceptance, and the changelog carries no deprecation notices (3 of 20). Schedule A of the DPA lists nine subprocessors with locations, the security page says data is stored in EU regions by default with custom locations for enterprise, and no notice period for new subprocessors is given (16 of 20). 15 + 14 + 3 + 16 = 48.\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### Reliability: New Relic MCP Server +10\n\n- Better Stack (50): Read with the hosted lines and scored on the remote MCP server at mcp.betterstack.com, which fronts the same service as the Incidents and Telemetry APIs. status.betterstack.com runs on Better Stack's own status page product with three components and a 90-day history (20). Between 5 August and 3 November 2026 it records delayed Telemetry data processing in the Europe region from 3 to 6 September in entries of 6 hours 19 minutes, 10 hours 10 minutes, 19 hours 13 minutes, 21 hours 45 minutes and 1 day, a 9-minute Telemetry degradation on 20 August, 39 minutes of wrong downtime notifications on 21 October and 8 minutes of dashboard unavailability on 2 November, every one labelled degraded, plus two migrations labelled maintenance (11 hours 13 minutes on 9 August and 17 hours). About four days of delayed log processing in one region is more than trivial and less than an outage of the API, so between minor-only and one major (15). No rate limit numbers were found in the API or MCP docs (0). The Usage API documents a 429 with the instruction to wait before retrying, with no Retry-After, no backoff guidance and no idempotency keys. `Upsert catalog records` is documented as not creating duplicates when repeated (5 of 15). No SLA. The terms supply the service as is, and the enterprise page lists SLA reporting as a feature (0). The MCP server was announced on 15 September 2025 and carries no beta label (10). 20 + 15 + 0 + 5 + 0 + 10 = 50.\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### Payments \u0026 pricing: Better Stack +10\n\n- Better Stack (40): Read with the hosted rubric. No x402, MPP or L402 (0). Per-unit prices are public without login, by GB and region for telemetry, per responder, per status page and per phone number (20). The Free plan has 10 monitors, a status page and 3 GB of logs, the signup page says Sign up for free and names no card, and we did not run the signup flow (20). A person signs up in a browser and mints a token or completes OAuth there (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### Maintenance \u0026 community: New Relic MCP Server +9\n\n- Better Stack (71): Read as a closed service. The Claude plugin reached 1.3.12 on 2 November 2026 and the changelog's newest entry is 29 October 2026 (30). Changelog entries on 10 August, 9 September, 1 October, 15 October and 29 October 2026 (20). Public changelog, hello@betterstack.com with a stated reply within a few hours, and a community site. GitHub issues on the plugin repositories were not read (10 of 15). The MCP server is not in the official MCP registry under a verified namespace, the only entries matching the name being third-party scrapers, and there is no official API SDK. The Claude, Cursor, Codex and Antigravity plugins and two Terraform providers are current (5 of 15). The Claude plugin repository is MIT with 12 commit days since June 2026, and we didn't read its CI (6 of 10). 30 + 20 + 10 + 5 + 6 = 71.\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### Schema \u0026 documentation: New Relic MCP Server +5\n\n- Better Stack (46): The server is closed and tools/list needs sign-in, so the tool schemas were not read, and no OpenAPI file was found for the REST APIs in the docs, the GitHub organisation or a search. Partial credit for a typed contract that exists but isn't public (10 of 25). No llms.txt on betterstack.com or its docs, and no Markdown twins (0). The MCP docs page gives one line per tool and says when some apply, such as Reopen incident within 24 hours and the instruction tools to call before Execute query. The REST reference pages describe each endpoint in a sentence (12 of 20). Inputs are typed only in the REST docs, with parameter tables, monitor types and status values listed in prose, and no schema to validate against (7 of 15). Every REST page carries a curl example and a 200 body; Create monitor documents a 422 with errors keyed by field, the Usage API a 401 and a 429, and no error code list exists (9 of 15). The APIs are versioned v2 in the path. The changelog is a product feed of 19 entries since March 2025 with the MCP server among them, with no API changelog and no deprecation notes (8 of 15). 10 + 0 + 12 + 7 + 9 + 8 = 46.\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 | Better Stack | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 50 | 60 | New Relic MCP Server +10 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 46 | 51 | New Relic MCP Server +5 |\n| Agent ergonomics | 13% (16.2 this run) | 55 | 59 | New Relic MCP Server +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 60 | 76 | New Relic MCP Server +16 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 40 | 30 | Better Stack +10 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 71 | 80 | New Relic MCP Server +9 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 69 | 81 | New Relic MCP Server +12 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **54.2 · C** | **61 · C** | |\n\n## Facts side by side\n\n| Fact | Better Stack | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Better Stack, Inc. | New Relic, Inc. |\n| Hosted endpoint | `https://mcp.betterstack.com` | `https://mcp.newrelic.com/mcp/` |\n| Transports | Streamable HTTP | Streamable HTTP |\n| Auth | OAuth or key | OAuth |\n| Pricing | Freemium | Freemium |\n| Price for observability logs | $0.10 per GB of traffic | not published |\n| x402 | no | no |\n| Licence | Proprietary hosted service under the Better Stack Terms of Use. The Claude, Cursor and Codex plugins and the Terraform providers on GitHub are MIT | none |\n| Tools exposed | 148 | 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-11-02 | 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 | 6 stars | none |\n\n## Verdicts\n\n**Better Stack.** One remote MCP server reaches incidents, on-call, monitors, status pages, logs, metrics, traces and errors with OAuth or a team-scoped token, and two headers cut its 148 tools down. Tool schemas and rate limits aren't published, there is no SLA, and audit logs of token use are a paid add-on.\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### Better Stack\n\n1. Connect with `claude mcp add betterstack --transport http https://mcp.betterstack.com` and sign in, or send a team-based API token as `Authorization: Bearer`; pick Read access unless the task writes\n2. Send `X-MCP-Tools-Only: monitors,monitor,incidents` or a similar list to keep the 148-tool list out of context, and `X-MCP-Tools-Except: remove_dashboard,remove_chart` to block deletes\n3. Call `Get query instructions` or `Plan query windows` before `Execute query`, since long time ranges are split into windows and nothing documents a result size limit\n4. No rate limit is published. Back off on a 429 and don't retry writes blindly, because there are no idempotency keys; `Upsert catalog records` is the one write documented as safe to repeat\n5. Reopening an incident only works within 24 hours of its resolution, and a comment can only be edited or removed by its author or an API token\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, Better Stack or New Relic MCP Server?\n\nNew Relic MCP Server scores 61 (C) on agent readiness against Better Stack's 54.2 (C), and leads in 6 of 7 scored categories. Better Stack leads on payments \u0026 pricing.\n\n### Do Better Stack and New Relic MCP Server need an API key?\n\nBetter Stack takes an API key or an OAuth sign-in. New Relic MCP Server uses an OAuth sign-in.\n\n### Can an agent call Better Stack and New Relic MCP Server without installing anything?\n\nYes. Better Stack has a hosted endpoint at https://mcp.betterstack.com 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/better-stack-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/better-stack-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"better-stack\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare better-stack new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/better-stack.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Better Stack or New Relic MCP Server\n\n- [Better Stack vs incident.io API](https://www.anchorterminal.com/compare/better-stack-vs-incident-io.md)\n- [Better Stack vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-pagerduty-mcp.md)\n- [Better Stack vs Rootly MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-rootly-mcp.md)\n- [Causely MCP server vs New Relic MCP Server](https://www.anchorterminal.com/compare/causely-vs-new-relic.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 Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md)\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md)\n- [Better Stack vs Causely MCP server](https://www.anchorterminal.com/compare/better-stack-vs-causely.md)\n- [Better Stack vs Datadog MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-datadog-mcp.md)\n- [Better Stack vs Grafana MCP Server](https://www.anchorterminal.com/compare/better-stack-vs-grafana-mcp-server.md)\n- [Better Stack vs Honeycomb MCP](https://www.anchorterminal.com/compare/better-stack-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- [Better Stack vs Sentry MCP](https://www.anchorterminal.com/compare/better-stack-vs-sentry-mcp.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-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": "Better Stack vs New Relic MCP Server", "url": "" } ], "description": "New Relic scores 61 (C) to Better Stack's 54.2 (C) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Better Stack C 54.2", "New Relic MCP Server C 61", "scores" ], "h1": "Better Stack vs New Relic MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/better-stack-vs-new-relic", "published": "2026-10-01", "section": "tools", "title": "Better Stack vs New Relic for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/better-stack-vs-new-relic" }, "tokens": { "markdown": 5550, "slim": 3630 }, "version": 1 }