# Axiom MCP Server vs New Relic MCP Server (slim)

> Axiom scores 68.2 (B) to New Relic's 61 (C) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.

- Full: https://www.anchorterminal.com/compare/axiom-vs-new-relic.md (~4,200 tokens) · this version ~2,330 tokens · JSON https://www.anchorterminal.com/compare/axiom-vs-new-relic.json · canonical https://www.anchorterminal.com/compare/axiom-vs-new-relic
- Index: https://www.anchorterminal.com/llms.txt · API: https://www.anchorterminal.com/api/v1/index.json · MCP: https://www.anchorterminal.com/mcp · Updated: 2026-11-04
- Licence: CC BY 4.0, credit Anchor Terminal and link this page (https://www.anchorterminal.com/terms/#data)

Axiom MCP Server scores 68.2 (B) on agent readiness against New Relic MCP Server's 61 (C), and leads in 5 of 7 scored categories. New Relic MCP Server leads on transparency & trust. Both do observability logs.

- Axiom MCP Server: B 68.2, rank #269 of 1349 · https://www.anchorterminal.com/tools/axiom.min.md
- New Relic MCP Server: C 61, rank #567 of 1349 · https://www.anchorterminal.com/tools/new-relic.min.md
- Axiom MCP Server, good for Agents that investigate logs, traces and metrics with APL and need a budget cap, and agents that must bootstrap their own observability without a person. Ahead on Reliability, 72 against 60; Schema & documentation, 62 against 51; Payments & pricing, 60 against 30.
- New Relic MCP Server, good for Agents investigating incidents, errors, deployments and performance in an existing New Relic account, where reads are enough. Ahead on Transparency & trust, 81 against 70.

| Category | Axiom MCP Server | New Relic MCP Server |
| --- | --- | --- |
| Reliability (16%) | 72 | 60 |
| Performance (10%) | pending | pending |
| Schema & documentation (13%) | 62 | 51 |
| Agent ergonomics (13%) | 63 | 59 |
| Security & auth (14%) | 72 | 76 |
| Payments & pricing (10%) | 60 | 30 |
| Task success (10%) | pending | pending |
| Maintenance & community (7%) | 83 | 80 |
| Transparency & trust (7%) | 70 | 81 |

| Fact (where they differ) | Axiom MCP Server | New Relic MCP Server |
| --- | --- | --- |
| Vendor | Axiom, Inc. | New Relic, Inc. |
| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.newrelic.com/mcp/` |
| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP |
| Tools exposed | 31 | 40 |
| Read-only variant documented | no | yes |
| MCP registry | `co.axiom/mcp` | `com.newrelic/mcp-server` |
| Last release | 2026-10-29 | 2026-10-28 |
| Terms last updated | no date given | 2022-11-08 |
| Privacy policy last updated | no date given | 2026-09-14 |
| Terms restrict benchmarking | not found in the text | yes |

Why the edge:
- Payments & pricing, Axiom MCP Server +30: Axiom MCP Server 60 (No x402, MPP or L402 (0). The pricing page states the platform fee, the free allowances, add-on prices and that usage carries volume discounts, with a calculator rather than a printed per-unit rate (20). The Personal plan is free with no card (20). `POST /v2/orgs/provision` needs no authentication and returns a working token, so an agent can start without a person, though a person must claim the organisation within 24 hours for it to persist (20). 0 + 20 + 20 + 20 = 60.); 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.)
- Reliability, Axiom MCP Server +12: Axiom MCP Server 72 (Scored as a hosted MCP server. status.axiom.co is an incident.io page with six US and six EU components (API, ingest, querying, alerting, endpoints, app) and uptime per component for August to November 2026, with no MCP component (20). feed.rss holds nine incidents in the 90 days to 3 November 2026, among them elevated query errors in the US from 18:05 to 19:15 UTC on 14 October with missed monitor runs, a metrics ingestion and query disruption on 15 October, elevated query errors after a deployment on 21 October, metrics query error rates on 25 October, query errors and monitor delays on 27 October, metrics ingest on 30 October, EU monitor alerting degraded on 7 October, and console authentication through GitHub degraded on 12 August. US querying shows 99.90 per cent uptime. One incident over an hour on the query path and several shorter ones, so one major (10). Rate limits are published as headers (X-RateLimit-Scope, -Limit, -Remaining, -Reset) and plan limits on the limits page, but the per-minute numbers aren't printed (12). 429 with a message and reset headers, query cost caps that answer 429 with the reset time, and provisioning 429 with backoff guidance; no idempotency keys for the write tools (10). A published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits (10). Not marked beta; registry version 1.0.0 (10). 20 + 10 + 12 + 10 + 10 + 10 = 72.); 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.)
- Schema & documentation, Axiom MCP Server +11: Axiom MCP Server 62 (The server is closed source (axiomhq/mcp isn't public) and tools/list needs a session, so the input schemas couldn't be read; partial credit for a contract that exists (10). llms.txt on axiom.co and a Markdown twin of every docs page (10). The tools reference gives each tool a purpose, an example request and a Read or Write label, says to use `queryMetrics` for metrics datasets instead of `queryDataset`, and the 29 October 2026 changelog adds session instructions on finding dataset and field names first (15). No parameters, types or enums are published for the tools (4). An example per tool, the REST docs' error shapes and the 429 bodies; no MCP error list (8). A dated changelog with MCP entries and a protocol version stated (2026-07-28 alongside the session transport), and a registry version (15). 10 + 10 + 15 + 4 + 8 + 15 = 62.); 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.)
- Transparency & trust, New Relic MCP Server +11: Axiom MCP Server 70 (Closed service with clear terms naming Axiom, Inc. (15). A privacy policy with retention by data category, a DPA that names the sub-processor page and US or EU processing, and per-plan retention on the pricing page; the sub-processor list itself renders through a script and the terms carry no date (20). The changelog has a deprecation category and the docs mark the legacy query endpoint, but no notice period is written down (10). US and EU edge deployments are documented and the DPA says data may be processed in either, with the sub-processor list unread (12). 15 + 20 + 10 + 12 = 57.); 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.)