{ "data": { "a": { "slug": "axiom", "name": "Axiom MCP Server", "vendor": "Axiom, Inc.", "vendorUrl": "https://axiom.co", "kind": "mcp", "category": "observability", "summary": "Axiom's hosted MCP server at mcp.axiom.co lets AI agents query logs, traces, events and metrics in an Axiom organisation with APL, read and manage dashboards, monitors and notifiers, and inspect the service map, over OAuth or a token header.", "url": "https://www.anchorterminal.com/tools/axiom", "markdownUrl": "https://www.anchorterminal.com/tools/axiom.md", "slimMarkdownUrl": "https://www.anchorterminal.com/tools/axiom.min.md", "jsonUrl": "https://www.anchorterminal.com/api/v1/tools/axiom.json", "dns": "axiom.grade.anchorterminal.com", "transports": [ "streamable-http", "sse" ], "remoteUrl": "https://mcp.axiom.co/mcp", "packages": [], "auth": "oauth", "authNotes": "Browser OAuth (recommended) creates a session the agent uses as the signed-in user; sessions are listed and revoked under Settings \u003e Profile. Agents without a browser send `Authorization: Bearer` with a personal access token and `x-axiom-org-id`, or put the organisation id in the URL as `?org-id=`. A PAT has full account rights; scoped API tokens with dataset and action permissions, expiry and dollar query-cost limits exist for the REST API and Skills. EU organisations use mcp.eu.axiom.co.", "pricing": "freemium", "pricingNotes": "Personal plan $0 with no card, with 500 GB a month of data loading compute, 10 GB-hours of query compute, 25 GB storage, 30-day retention. Axiom Cloud $25 a month platform fee plus usage, with an Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage, volume discounts and add-ons (RBAC $50, extended audit logs $50, SAML SSO $100, directory sync $100 a month). An agent can provision a temporary organisation with no account (https://axiom.co/pricing).", "priceSummary": "$25 / mo", "where": "hosted", "x402": { "level": "no", "evidence": "No x402, MPP or L402 in the MCP docs, API docs, pricing or terms (checked 2026-11-03). Usage is billed to the organisation; unclaimed agent-created organisations have fixed free limits for 24 hours.", "endpoints": [] }, "toolCount": 31, "popularity": { "githubStars": null, "npmWeekly": null, "pypiWeekly": null, "asOf": "2026-11-03" }, "docsUrl": "https://axiom.co/docs/console/intelligence/mcp-server", "llmsTxt": "https://axiom.co/llms.txt", "registryName": "co.axiom/mcp", "capabilities": [ "observability.logs", "observability.traces", "observability.metrics", "observability.incidents", "observability.errors" ], "tags": [ "hosted", "freemium", "free-tier", "no-card", "mcp", "remote-mcp", "mcp-registry", "oauth", "llms-txt", "status-page", "sla", "security-txt", "bug-bounty", "soc2", "iso27001", "eu-region", "usage-priced", "closed-source" ], "lastRelease": "2026-10-29", "graded": true, "anchor": { "graded": true, "score": 68.2, "grade": "B", "agentReady": false, "rank": 269, "ranked": true, "rankOf": 1349, "categoryRank": 3, "methodology": "0.7", "run": "2026-10-01", "scores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 70 }, "pending": [ "performance", "tasks" ], "assessment": { "confidence": "medium", "date": "2026-11-03" }, "negative": 0, "verdict": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "bestFor": "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.", "strengths": [ "`POST /v2/orgs/provision` needs no account and returns a working token; a person claims the organisation later or it expires in 24 hours", "Query cost limits in dollars per hour and per day on tokens and roles bound what an agent can spend, with 429 past the cap", "OAuth sessions keep tokens away from the agent and are revocable per session; ISO 27001, SOC 2 Type II, a security.txt and a bug bounty policy", "99.9 per cent monthly uptime SLA with service credits, published rate-limit headers and a status page with per-component uptime", "Dated changelog with MCP entries, llms.txt, Markdown twins of every docs page and setup for 16 clients" ], "weaknesses": [ "The server is closed source and tool input schemas are only visible through an authenticated session", "The AI agents overview calls the MCP server read-only while the tools reference lists delete tools for dashboards, monitors and notifiers", "A header-based connection uses a personal access token with full account rights, since scoped API tokens aren't accepted by the MCP server per the docs", "Nine status incidents between 12 August and 30 October 2026, mostly elevated query errors, one of 70 minutes in the US", "Logs and traces come back as untrusted text with no prompt-injection guidance, and the sub-processor list renders through a script our reader couldn't run" ], "agentNotes": [ "With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed", "Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL", "Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner", "Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first", "`deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting" ], "metrics": { "kind": "remote", "measured": false }, "reviewCount": 0, "avgRating": 0, "history": [ { "basis": "public evidence", "confidence": "medium", "grade": "B", "methodology": "0.7", "pending": [ "performance", "tasks" ], "run": "2026-10-01", "runLabel": "October 2026 research run", "score": 68.2 } ], "editorialScores": { "ergonomics": 63, "maintenance": 83, "payments": 60, "reliability": 72, "schema": 62, "security": 72, "transparency": 57 }, "provenanceScore": 83, "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": { "install": "npx -y add-mcp https://mcp.axiom.co/mcp -g", "http": "curl -X POST https://api.axiom.co/v2/orgs/provision -H 'Content-Type: application/json' -d '{\"name\":\"agent-sandbox\"}'", "claudeCode": "claude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp", "config": { "mcpServers": { "axiom": { "url": "https://mcp.axiom.co/mcp" } } } }, "letme": { "capability": "https://letme.dev/observability.logs", "tool": "https://letme.dev/axiom" }, "area": "developer", "unitPrices": [ { "item": "Axiom Cloud platform fee", "unit": "month", "usd": 25, "note": "Plus usage beyond the Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage a month" }, { "item": "Role-based access control add-on", "unit": "month", "usd": 50, "note": "Extended audit logs $50, SAML SSO $100, directory sync $100" } ], "provenance": { "legalEntity": "Axiom, Inc.", "domain": "axiom.co", "domainRegistered": "", "endpointOnVendorDomain": true, "terms": "https://axiom.co/docs/legal/terms-of-service", "privacy": "https://axiom.co/docs/legal/privacy", "statusPage": "https://status.axiom.co", "changelog": "https://axiom.co/changelog", "securityTxt": "valid", "checked": "2026-11-03", "notes": [ "The terms of service name Axiom, Inc. under California law and carry no last-updated date in the text; the privacy policy and DPA name Axiom Inc. and privacy@axiom.co. No clause on automated reading of the website was found.", "axiom.co/robots.txt allows all crawlers, naming ClaudeBot, Claude-User and others as allowed, and disallows only /api/. trust.axiom.co renders through a script (Vanta) and its sub-processor list was not readable.", "axiom.co/.well-known/security.txt redirects to app.axiom.co, where it names security@axiom.co, a policy at axiom.co/security and an expiry of 1 April 2027.", "status.axiom.co is an incident.io page with six US and six EU components and per-component uptime for August to November 2026; feed.rss holds nine incidents back to 12 August 2026.", "RDAP for axiom.co couldn't be read (the .co registry's RDAP answered 502 and rdap.org returned nothing), so the registration date is blank. firstReleased is 5 December 2024, the v0.0.1 tag of the earlier open-source mcp-server-axiom; the hosted server's own first date isn't on a first-hand page, and its registry entry is from 30 September 2025." ], "score": 83 }, "pageJsonUrl": "https://www.anchorterminal.com/tools/axiom.json", "live": { "slug": "axiom", "probe": { "target": "https://mcp.axiom.co/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T21:39:14.263725519Z", "lastOk": true, "lastStatus": 401, "lastMs": 72, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 91, "p95ms24h": 177, "samples24h": 64, "samples30d": 64, "days": [ { "date": "2026-11-04", "probes": 64, "ok": 64 } ] }, "vendorStatus": { "page": "https://status.axiom.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T21:37:46.118662306Z" }, "versions": [ { "registry": "mcp-registry", "name": "co.axiom/mcp", "version": "1.0.0", "seenAt": "2026-11-04T17:11:44.552009456Z" } ], "securityTxt": { "url": "https://axiom.co/.well-known/security.txt", "state": "valid", "expires": "2027-04-01T00:01:00Z", "checkedAt": "2026-11-04T15:54:16.073085585Z" }, "updatedAt": "2026-11-04T21:39:14.263725519Z" } }, "answer": "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 \u0026 trust.", "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": 30, "category": "payments", "leads": "axiom", "name": "Payments \u0026 pricing", "reasons": { "a": "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.", "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": 60, "b": 30 } }, { "by": 12, "category": "reliability", "leads": "axiom", "name": "Reliability", "reasons": { "a": "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.", "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": 72, "b": 60 } }, { "by": 11, "category": "schema", "leads": "axiom", "name": "Schema \u0026 documentation", "reasons": { "a": "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.", "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": 62, "b": 51 } }, { "by": 11, "category": "transparency", "leads": "new-relic", "name": "Transparency \u0026 trust", "reasons": { "a": "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.", "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": 70, "b": 81 } } ], "facts": [ { "a": "MCP server", "b": "MCP server", "name": "Kind" }, { "a": "Axiom, Inc.", "b": "New Relic, Inc.", "name": "Vendor" }, { "a": "https://mcp.axiom.co/mcp", "b": "https://mcp.newrelic.com/mcp/", "name": "Hosted endpoint" }, { "a": "Streamable HTTP, SSE (legacy)", "b": "Streamable HTTP", "name": "Transports" }, { "a": "OAuth", "b": "OAuth", "name": "Auth" }, { "a": "Freemium", "b": "Freemium", "name": "Pricing" }, { "a": "no", "b": "no", "name": "x402" }, { "a": "31", "b": "40", "name": "Tools exposed" }, { "a": "no", "b": "yes", "name": "Read-only variant documented" }, { "a": "yes", "b": "yes", "name": "llms.txt" }, { "a": "co.axiom/mcp", "b": "com.newrelic/mcp-server", "name": "MCP registry" }, { "a": "2026-10-29", "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" } ], "faq": [ { "answer": "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 \u0026 trust.", "question": "Which is better for AI agents, Axiom MCP Server or New Relic MCP Server?" }, { "answer": "Both use an OAuth sign-in.", "question": "Do Axiom MCP Server and New Relic MCP Server need an API key?" }, { "answer": "Yes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/mcp and New Relic MCP Server at https://mcp.newrelic.com/mcp/.", "question": "Can an agent call Axiom MCP Server and New Relic MCP Server without installing anything?" } ], "goodFor": [ { "aheadOn": [ "Reliability, 72 against 60", "Schema \u0026 documentation, 62 against 51", "Payments \u0026 pricing, 60 against 30" ], "also": null, "goodFor": "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.", "slug": "axiom", "watchFor": "The server is closed source and tool input schemas are only visible through an authenticated session" }, { "aheadOn": [ "Transparency \u0026 trust, 81 against 70" ], "also": null, "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/axiom-vs-incident-io.json", "title": "Axiom MCP Server vs incident.io API", "url": "https://www.anchorterminal.com/compare/axiom-vs-incident-io" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.json", "title": "Axiom MCP Server vs PagerDuty MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.json", "title": "Axiom MCP Server vs Rootly MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-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-causely.json", "title": "Axiom MCP Server vs Causely MCP server", "url": "https://www.anchorterminal.com/compare/axiom-vs-causely" }, { "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-grafana-mcp-server.json", "title": "Axiom MCP Server vs Grafana MCP Server", "url": "https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server" }, { "json": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.json", "title": "Axiom MCP Server vs Honeycomb MCP", "url": "https://www.anchorterminal.com/compare/axiom-vs-honeycomb-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-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/axiom-vs-sentry-mcp.json", "title": "Axiom MCP Server vs Sentry MCP", "url": "https://www.anchorterminal.com/compare/axiom-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": [ { "axiom": 72, "by": 12, "edge": "axiom", "key": "reliability", "name": "Reliability", "new-relic": 60, "weight": 16 }, { "key": "performance", "name": "Performance", "pending": true, "weight": 10 }, { "axiom": 62, "by": 11, "edge": "axiom", "key": "schema", "name": "Schema \u0026 documentation", "new-relic": 51, "weight": 13 }, { "axiom": 63, "by": 4, "edge": "axiom", "key": "ergonomics", "name": "Agent ergonomics", "new-relic": 59, "weight": 13 }, { "axiom": 72, "by": 4, "edge": "new-relic", "key": "security", "name": "Security \u0026 auth", "new-relic": 76, "weight": 14 }, { "axiom": 60, "by": 30, "edge": "axiom", "key": "payments", "name": "Payments \u0026 pricing", "new-relic": 30, "weight": 10 }, { "key": "tasks", "name": "Task success", "pending": true, "weight": 10 }, { "axiom": 83, "by": 3, "edge": "axiom", "key": "maintenance", "name": "Maintenance \u0026 community", "new-relic": 80, "weight": 7 }, { "axiom": 70, "by": 11, "edge": "new-relic", "key": "transparency", "name": "Transparency \u0026 trust", "new-relic": 81, "weight": 7 } ], "summary": "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 \u0026 trust. Both do observability logs.", "tasks": null, "tutorials": [], "verdicts": { "axiom": "An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.", "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/axiom-vs-new-relic", "json": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.md", "mcp": "https://www.anchorterminal.com/mcp", "slim": "https://www.anchorterminal.com/compare/axiom-vs-new-relic.min.md" }, "markdown": "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 \u0026 trust. Both do observability logs.\n\n- Axiom MCP Server: grade B, 68.2/100, rank #269 of 1349. Markdown https://www.anchorterminal.com/tools/axiom.md · JSON https://www.anchorterminal.com/api/v1/tools/axiom.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### Axiom MCP Server (B)\n\nGood 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.\n\nAhead on:\n- Reliability, 72 against 60\n- Schema \u0026 documentation, 62 against 51\n- Payments \u0026 pricing, 60 against 30\n\nWatch for: The server is closed source and tool input schemas are only visible through an authenticated session\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- Transparency \u0026 trust, 81 against 70\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### Payments \u0026 pricing: Axiom MCP Server +30\n\n- 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.\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### Reliability: Axiom MCP Server +12\n\n- 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.\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### Schema \u0026 documentation: Axiom MCP Server +11\n\n- 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.\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### Transparency \u0026 trust: New Relic MCP Server +11\n\n- 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.\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## Score by category\n\n| Category | Weight | Axiom MCP Server | New Relic MCP Server | Edge |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% (20 this run) | 72 | 60 | Axiom MCP Server +12 |\n| Performance | 10%, pending | pending | pending | not scored in this run |\n| Schema \u0026 documentation | 13% (16.2 this run) | 62 | 51 | Axiom MCP Server +11 |\n| Agent ergonomics | 13% (16.2 this run) | 63 | 59 | Axiom MCP Server +4 |\n| Security \u0026 auth | 14% (17.5 this run) | 72 | 76 | New Relic MCP Server +4 |\n| Payments \u0026 pricing | 10% (12.5 this run) | 60 | 30 | Axiom MCP Server +30 |\n| Task success | 10%, pending | pending | pending | not scored in this run |\n| Maintenance \u0026 community | 7% (8.8 this run) | 83 | 80 | Axiom MCP Server +3 |\n| Transparency \u0026 trust | 7% (8.8 this run) | 70 | 81 | New Relic MCP Server +11 |\n| Negative events | ≤15 | 0 | 0 | |\n| **Total** | | **68.2 · B** | **61 · C** | |\n\n## Facts side by side\n\n| Fact | Axiom MCP Server | New Relic MCP Server |\n| --- | --- | --- |\n| Kind | MCP server | MCP server |\n| Vendor | Axiom, Inc. | New Relic, Inc. |\n| Hosted endpoint | `https://mcp.axiom.co/mcp` | `https://mcp.newrelic.com/mcp/` |\n| Transports | Streamable HTTP, SSE (legacy) | Streamable HTTP |\n| Auth | OAuth | OAuth |\n| Pricing | Freemium | Freemium |\n| x402 | no | no |\n| Tools exposed | 31 | 40 |\n| Read-only variant documented | no | yes |\n| llms.txt | yes | yes |\n| MCP registry | `co.axiom/mcp` | `com.newrelic/mcp-server` |\n| Last release | 2026-10-29 | 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\n## Verdicts\n\n**Axiom MCP Server.** An agent can start without a person, provisioning a temporary organisation with one unauthenticated call, and then query with OAuth sessions capped by dollar cost limits under a 99.9 per cent SLA. Tool schemas aren't public, the server is closed source, and the docs call it read-only while listing delete tools.\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### Axiom MCP Server\n\n1. With no organisation, call `POST https://api.axiom.co/v2/orgs/provision` once, store the returned token and surface the `claimUrl` to the person; both are shown once and the organisation is deleted after 24 hours unclaimed\n2. Call `listDatasets` and `getDatasetFields` before `queryDataset`; metrics datasets take `queryMetrics` with MPL, not APL\n3. Treat a 429 as a rate limit or a query-cost cap; read `X-RateLimit-Reset` or the limit message for when the window resets, and don't resend sooner\n4. Prefer OAuth; if a token header is the only option, expect the PAT to carry the person's full rights and ask them to set a query cost limit on their role first\n5. `deleteDashboard`, `deleteMonitor` and `deleteNotifier` are live writes with no confirmation step; list first and confirm with the person before deleting\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, Axiom MCP Server or New Relic MCP Server?\n\nAxiom 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 \u0026 trust.\n\n### Do Axiom MCP Server and New Relic MCP Server need an API key?\n\nBoth use an OAuth sign-in.\n\n### Can an agent call Axiom MCP Server and New Relic MCP Server without installing anything?\n\nYes. Axiom MCP Server has a hosted endpoint at https://mcp.axiom.co/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/axiom-vs-new-relic.json, and with the fewest tokens: https://www.anchorterminal.com/compare/axiom-vs-new-relic.min.md\n- Over MCP at https://www.anchorterminal.com/mcp (no key): `compare_tools {\"a\": \"axiom\", \"b\": \"new-relic\"}`. From a terminal: `anchor compare axiom new-relic`\n- Each listing in full: https://www.anchorterminal.com/api/v1/tools/axiom.json and https://www.anchorterminal.com/api/v1/tools/new-relic.json\n\n## Other comparisons with Axiom MCP Server or New Relic MCP Server\n\n- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md)\n- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md)\n- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-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 Causely MCP server](https://www.anchorterminal.com/compare/axiom-vs-causely.md)\n- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md)\n- [Axiom MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md)\n- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-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 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- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-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": "Axiom MCP Server vs New Relic MCP Server", "url": "" } ], "description": "Axiom scores 68.2 (B) to New Relic's 61 (C) for observability logs. Prices, MCP, x402, uptime and agent notes side by side.", "facts": [ "Axiom MCP Server B 68.2", "New Relic MCP Server C 61", "scores" ], "h1": "Axiom MCP Server vs New Relic MCP Server", "image": "https://www.anchorterminal.com/assets/og/default.png", "path": "/compare/axiom-vs-new-relic", "published": "2026-10-01", "section": "tools", "title": "Axiom vs New Relic for AI agents in 2026: scores and prices", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/compare/axiom-vs-new-relic" }, "tokens": { "markdown": 4200, "slim": 2330 }, "version": 1 }