{ "data": { "similar": [ { "grade": "C", "json": "https://www.anchorterminal.com/tools/new-relic.json", "name": "New Relic MCP Server", "score": 61, "shared": [ "observability.metrics", "observability.logs", "observability.errors", "observability.traces", "observability.incidents" ], "slug": "new-relic" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/better-stack.json", "name": "Better Stack", "score": 54.2, "shared": [ "observability.logs", "observability.incidents", "observability.metrics", "observability.traces", "observability.errors" ], "slug": "better-stack" }, { "grade": "BB", "json": "https://www.anchorterminal.com/tools/grafana-mcp-server.json", "name": "Grafana MCP Server", "score": 71, "shared": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents" ], "slug": "grafana-mcp-server" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/datadog-mcp.json", "name": "Datadog MCP Server", "score": 56.8, "shared": [ "observability.metrics", "observability.logs", "observability.traces", "observability.incidents" ], "slug": "datadog-mcp" }, { "grade": "E", "json": "https://www.anchorterminal.com/tools/causely.json", "name": "Causely MCP server", "score": 39.5, "shared": [ "observability.incidents", "observability.metrics", "observability.logs", "observability.errors" ], "slug": "causely" }, { "grade": "C", "json": "https://www.anchorterminal.com/tools/honeycomb-mcp.json", "name": "Honeycomb MCP", "score": 58.5, "shared": [ "observability.traces", "observability.metrics", "observability.logs" ], "slug": "honeycomb-mcp" } ], "tool": { "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": 264, "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" ], "breakdown": [ { "key": "reliability", "name": "Reliability", "weight": 16, "effectiveWeight": 20, "score": 72, "points": 14.4, "reason": "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.", "checked": "2026-11-03" }, { "key": "performance", "name": "Performance", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes." }, { "key": "schema", "name": "Schema \u0026 documentation", "weight": 13, "effectiveWeight": 16.25, "score": 62, "points": 10.07, "reason": "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.", "checked": "2026-11-03" }, { "key": "ergonomics", "name": "Agent ergonomics", "weight": 13, "effectiveWeight": 16.25, "score": 63, "points": 10.24, "reason": "31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.", "checked": "2026-11-03" }, { "key": "security", "name": "Security \u0026 auth", "weight": 14, "effectiveWeight": 17.5, "score": 72, "points": 12.6, "reason": "Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.", "checked": "2026-11-03" }, { "key": "payments", "name": "Payments \u0026 pricing", "weight": 10, "effectiveWeight": 12.5, "score": 60, "points": 7.5, "reason": "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.", "checked": "2026-11-03" }, { "key": "tasks", "name": "Task success", "weight": 10, "effectiveWeight": 0, "pending": true, "points": 0, "reason": "Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored." }, { "key": "maintenance", "name": "Maintenance \u0026 community", "weight": 7, "effectiveWeight": 8.75, "score": 83, "points": 7.26, "reason": "Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.", "checked": "2026-11-03" }, { "key": "transparency", "name": "Transparency \u0026 trust", "weight": 7, "effectiveWeight": 8.75, "score": 70, "points": 6.13, "note": "editorial 57, provenance 83", "reason": "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.", "checked": "2026-11-03" } ], "assessment": { "date": "2026-11-03", "basis": "public evidence", "confidence": "medium", "notes": { "ergonomics": "31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.", "maintenance": "Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.", "payments": "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.", "reliability": "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.", "schema": "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.", "security": "Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.", "transparency": "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." }, "sources": [ { "what": "MCP server docs (setup, header auth, token hygiene, revocation)", "url": "https://axiom.co/docs/console/intelligence/mcp-server", "seen": "2026-11-03" }, { "what": "MCP tools reference", "url": "https://axiom.co/docs/console/intelligence/mcp-server/tools", "seen": "2026-11-03" }, { "what": "AI agents overview", "url": "https://axiom.co/docs/console/intelligence/ai-agents-overview", "seen": "2026-11-03" }, { "what": "agent-created organisations", "url": "https://axiom.co/docs/console/intelligence/agent-created-orgs", "seen": "2026-11-03" }, { "what": "query cost limits", "url": "https://axiom.co/docs/console/intelligence/query-cost-limits", "seen": "2026-11-03" }, { "what": "API limits (rate limit headers, 429)", "url": "https://axiom.co/docs/restapi/api-limits", "seen": "2026-11-03" }, { "what": "tokens", "url": "https://axiom.co/docs/reference/tokens", "seen": "2026-11-03" }, { "what": "limits", "url": "https://axiom.co/docs/reference/limits", "seen": "2026-11-03" }, { "what": "pagination", "url": "https://axiom.co/docs/restapi/pagination", "seen": "2026-11-03" }, { "what": "audit log", "url": "https://axiom.co/docs/reference/audit-log", "seen": "2026-11-03" }, { "what": "security and compliance", "url": "https://axiom.co/docs/platform-overview/security", "seen": "2026-11-03" }, { "what": "SLA", "url": "https://axiom.co/docs/legal/sla", "seen": "2026-11-03" }, { "what": "terms of service", "url": "https://axiom.co/docs/legal/terms-of-service", "seen": "2026-11-03" }, { "what": "privacy policy", "url": "https://axiom.co/docs/legal/privacy", "seen": "2026-11-03" }, { "what": "data processing addendum", "url": "https://axiom.co/docs/legal/data-processing", "seen": "2026-11-03" }, { "what": "pricing", "url": "https://axiom.co/pricing", "seen": "2026-11-03" }, { "what": "changelog", "url": "https://axiom.co/changelog", "seen": "2026-11-03" }, { "what": "agent-created organisations changelog entry", "url": "https://axiom.co/changelog/agent-created-organizations", "seen": "2026-11-03" }, { "what": "security and bug bounty policy", "url": "https://axiom.co/security", "seen": "2026-11-03" }, { "what": "security.txt", "url": "https://app.axiom.co/.well-known/security.txt", "seen": "2026-11-03" }, { "what": "llms.txt", "url": "https://axiom.co/llms.txt", "seen": "2026-11-03" }, { "what": "status page", "url": "https://status.axiom.co/", "seen": "2026-11-03" }, { "what": "status feed", "url": "https://status.axiom.co/feed.rss", "seen": "2026-11-03" }, { "what": "MCP registry entry", "url": "https://registry.modelcontextprotocol.io/v0/servers?search=axiom", "seen": "2026-11-03" }, { "what": "deprecated open-source server, shallow clone", "url": "https://github.com/axiomhq/mcp-server-axiom", "seen": "2026-11-03" }, { "what": "robots.txt", "url": "https://axiom.co/robots.txt", "seen": "2026-11-03" } ], "openQuestions": [ "unchecked: the live tools/list, input schemas and annotations, which need an OAuth session; the count of 31 tools is from the tools reference", "unchecked: the sub-processor list at trust.axiom.co/subprocessors (script-rendered) and the terms' last-updated date, which the Markdown text doesn't carry", "unchecked: the registration date of axiom.co; the .co registry's RDAP answered 502 and rdap.org returned no record", "The AI agents overview says the MCP server gives curated, read-only operations with no risk of destructive actions, while the tools reference lists createDataset and create, update and delete tools for dashboards, monitors and notifiers; recorded in the security and ergonomics scores, not as a deduction", "firstReleased is 5 December 2024, the first tag of the deprecated open-source mcp-server-axiom; the hosted server's first date isn't on a first-hand page, and its registry entry is from 30 September 2025", "Judgement call on reliability. Nine incidents in 90 days, mostly short query error spikes, were scored as one major on the 70-minute US query incident of 14 October 2026 rather than several majors, because the other entries carry no durations" ] }, "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 }, "scoreHistory": [ { "date": "2026-11-03", "grade": "B", "kind": "listed", "method": "0.7", "score": 68.2 } ] }, "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" }, "notable": [ "31 tools in the tools reference, 20 reads (query, datasets, metrics, dashboards, monitors, service map) and 11 writes (create dataset, create, update and delete dashboards, monitors and notifiers, send feedback), plus seven prebuilt prompts; the three service-map tools appear only when service map is enabled (https://axiom.co/docs/console/intelligence/mcp-server/tools)", "An agent can create a real organisation with one unauthenticated `POST https://api.axiom.co/v2/orgs/provision`, which returns a full-permission API token and a claim URL; the organisation is deleted after 24 hours unless a person claims it, with 10 GB of ingest, 1 GB-hour of query compute and at most 3 organisations a day meanwhile (https://axiom.co/docs/console/intelligence/agent-created-orgs)", "Query cost limits cap an identity's query spend per hour and per day in dollars; over the limit, queries fail with 429 until the window resets. They apply to API tokens and to roles, which is how OAuth sessions through the MCP server are capped (https://axiom.co/docs/console/intelligence/query-cost-limits)", "The AI agents overview describes the MCP server as curated, read-only operations with no risk of destructive actions, while the tools reference lists delete tools for dashboards, monitors and notifiers (https://axiom.co/docs/console/intelligence/ai-agents-overview)", "The changelog entry of 29 October 2026 adds built-in instructions at session start, two skills that let an agent send data, and support for the 2026-07-28 protocol version alongside the session-based transport (https://axiom.co/changelog)", "Published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits, and an incident.io status page showing 99.90 per cent querying uptime in the US from August to November 2026 (https://axiom.co/docs/legal/sla)", "Listed in the official MCP registry as co.axiom/mcp 1.0.0 on 30 September 2025 with the SSE URL https://mcp.axiom.co/sse; the linked repository axiomhq/mcp is not public and the older open-source mcp-server-axiom is deprecated (https://registry.modelcontextprotocol.io/v0/servers?search=axiom)" ], "area": "developer", "details": [ { "label": "Surface listed", "value": "The hosted MCP server at mcp.axiom.co and mcp.eu.axiom.co, read from the Markdown twins of axiom.co/docs (MCP server, tools reference, AI agents, agent-created organisations, query cost limits, API limits, tokens, limits, pagination, audit log, security, terms, privacy, SLA, DPA), axiom.co (pricing, changelog, company, security, llms.txt), status.axiom.co and its feed, app.axiom.co/.well-known/security.txt and the MCP registry on 3 November 2026. No account was used, no organisation provisioned and no tool called" }, { "label": "Tools", "value": "Reads are queryDataset, getSavedQueries, listDatasets, getDatasetFields, listMetrics, listMetricTags, getMetricTagValues, searchMetrics, queryMetrics, listDashboards, getDashboard, exportDashboard, checkMonitors, getMonitor, getMonitorHistory, listNotifiers, services-getMap, services-getChanges and services-getEdgeHistory. Writes are createDataset, createDashboard, updateDashboard, updateDashboardChart, deleteDashboard, createMonitor, updateMonitor, deleteMonitor, createNotifier, updateNotifier, deleteNotifier and sendFeedback" }, { "label": "Prompts", "value": "explore-unknown-dataset, detect-anomalies-in-events, correlate-events-across-datasets, data-quality-investigation, establish-performance-baseline, monitor-health-analysis, investigate-service-topology. Resources are planned" }, { "label": "Rate and cost limits", "value": "Rate limits per user and organisation stated by X-RateLimit-Scope, -Limit, -Remaining and -Reset headers, 429 with a message when exceeded; query limits in GB-milliseconds by plan in X-QueryLimit headers; query cost limits in dollars per hour and day on tokens and roles, 429 past the cap; provisioning capped at 3 organisations a day" }, { "label": "Regions", "value": "US server at mcp.axiom.co handles query results worldwide; EU server at mcp.eu.axiom.co keeps query results in EU data centres; sign-in and non-query requests go to the US API from both" }, { "label": "Agent-created organisations", "value": "Unauthenticated provisioning returns an organisation id, a full-permission token and a single-use claim URL; 24-hour expiry, 10 GB ingest and 1 GB-hour query compute while unclaimed, notifiers disabled until claimed" }, { "label": "Audit", "value": "Audit log on every organisation for the previous 30 days, full history as an add-on; OAuth sessions listed and revocable under Settings \u003e Profile" }, { "label": "Compliance", "value": "ISO 27001, SOC 2 Type II, GDPR DPA, HIPAA BAA as a self-serve add-on with RBAC, SSO and audit log, data on AWS encrypted with AES-256, sub-processor list on the trust centre, security.txt and a bug bounty policy" }, { "label": "Legal entity", "value": "Axiom, Inc., terms under California law, privacy and DPA contacts at privacy@axiom.co" } ], "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, "checks": [ { "check": "Legal entity named", "value": "Axiom, Inc.", "points": 20, "max": 20, "state": "ok" }, { "check": "Domain age", "value": "axiom.co, no registry record we could read", "points": 0, "max": 15, "state": "no" }, { "check": "Endpoint on the vendor's domain", "value": "mcp.axiom.co", "points": 15, "max": 15, "state": "ok" }, { "check": "Terms of service", "value": "read, states 4 of the 7 things a reader expects", "points": 7.4, "max": 10, "state": "part" }, { "check": "Privacy policy", "value": "read, states 7 of the 8 things a reader expects", "points": 9.3, "max": 10, "state": "part" }, { "check": "Status page", "value": "status.axiom.co", "points": 10, "max": 10, "state": "ok" }, { "check": "Changelog", "value": "published", "points": 10, "max": 10, "state": "ok" }, { "check": "security.txt", "value": "valid", "points": 10, "max": 10, "state": "ok" }, { "check": "People named", "value": "1 named with their role, none with a public profile", "points": 7, "max": 10, "state": "part" }, { "check": "Support route", "value": "a support address, help pages", "points": 5, "max": 5, "state": "ok" } ], "policies": [ { "kind": "terms", "url": "https://axiom.co/docs/legal/terms-of-service", "state": "read", "readAt": "2026-11-03", "words": 3951, "points": 7.4, "max": 10, "expected": [ { "key": "terms.date", "label": "Gives the date it was last updated", "found": false }, { "key": "terms.law", "label": "Names the governing law or courts", "found": true, "quote": "This Agreement and all matters relating to this Agreement shall be construed in accordance with and controlled by the laws of the State of California, without reference to its conflict of law principles.", "says": "The law of the State of California" }, { "key": "terms.liability", "label": "States a limit on its liability", "found": true, "quote": "AXIOM’S LIABILITY FOR ALL CLAIMS ARISING UNDER THIS AGREEMENT, WHETHER IN CONTRACT, TORT OR OTHERWISE, SHALL NOT EXCEED THE AMOUNT OF FEES PAID OR PAYABLE BY CUSTOMER UNDER THE APPLICABLE SERVICE DESCRIPTION DURING THE TWELVE (12) MONTH PERIOD PRECEDING THE CLAIM.", "says": "Capped at the fees paid in the 12 months before the claim" }, { "key": "terms.termination", "label": "Says how the agreement or account can be ended", "found": true, "quote": "Axiom may suspend Customer’s access to or use of the Service as follows: (a) immediately if Axiom reasonably believes Customer’s use of the Service may pose a security risk to or may adversely impact the Service;" }, { "key": "terms.changes", "label": "Says how changes to the terms are announced", "found": false }, { "key": "terms.use", "label": "Lists what users may not do", "found": true, "quote": "IF YOU DO NOT AGREE TO ALL OF THE FOLLOWING, YOU MAY NOT USE OR ACCESS THE SERVICES IN ANY MANNER." }, { "key": "terms.sla", "label": "Refers to a service level or uptime commitment", "found": false } ], "notes": [ { "date": "2026-11-03", "text": "Customer Data may be irretrievably deleted fifteen days after the agreement ends.", "quote": "Customer acknowledges and agrees that Customer Data may be irretrievably deleted after fifteen (15) days following a termination or expiration of this Agreement." }, { "date": "2026-11-03", "text": "Service terms renew automatically at then-current on-demand standard rates unless either party gives thirty days' written notice of non-renewal.", "quote": "Customer acknowledges and agrees that each Service Renewal shall be subject to the then-current, on-demand standard use rates, unless otherwise specified in the applicable Service Description." }, { "date": "2026-11-03", "text": "If the agreement is terminated for material breach, the customer pays all fees set out in the Service Description.", "quote": "If the Agreement is terminated due to Section 3.2 (a), Customer shall pay to Axiom all Fees set forth in the corresponding Service Description(s)." } ] }, { "kind": "privacy", "url": "https://axiom.co/docs/legal/privacy", "state": "read", "readAt": "2026-11-03", "words": 5552, "points": 9.3, "max": 10, "expected": [ { "key": "privacy.date", "label": "Gives the date it was last updated", "found": false }, { "key": "privacy.collected", "label": "Says what personal data is collected", "found": true, "quote": "‍This chart details the categories of Personal Data that we collect and have collected over the past 12 months:" }, { "key": "privacy.retention", "label": "Says how long data is kept", "found": true, "quote": "We retain Personal Data about you for as long as reasonably necessary to provide you with our Services or otherwise in support of our business or commercial purposes for utilization of your Personal Data, as expressed.", "says": "For as long as needed, with no period named" }, { "key": "privacy.processors", "label": "Says who else receives the data", "found": true, "quote": "Categories of Third Parties With Whom We Share this Personal Data" }, { "key": "privacy.sale", "label": "Says whether personal data is sold or shared for advertising", "found": true, "quote": "We will not sell your Personal Data, and have not done so over the last 12 months.", "says": "Says it does not sell personal data" }, { "key": "privacy.rights", "label": "Says what rights people have over their data", "found": true, "quote": "If we are processing your Personal Data as a service provider, you may contact the entity that collected your Personal Data in the first instance to address your rights with respect to such data as desired." }, { "key": "privacy.contact", "label": "Gives a privacy contact", "found": true, "quote": "If you believe that a child under 13 years of age may have provided Personal Data to us, please contact us at privacy@axiom.co.", "says": "privacy@axiom.co" }, { "key": "privacy.transfers", "label": "Says where data is transferred or stored", "found": true, "quote": "servers, and you authorize Company to transfer, store and process your information to and in the U.S., and possibly other countries." } ], "toKnow": [ { "key": "privacy.sells", "label": "Says it sells personal data or shares it for advertising", "found": true, "quote": "Some of these disclosures may constitute a “sale” of your Personal Data as defined under applicable laws." } ] } ] }, "humans": { "slug": "axiom", "checked": "2026-11-03", "company": "Axiom", "people": [ { "name": "Neil Jagdish Patel", "role": "Co-founder", "founder": true, "bio": "Neil Jagdish Patel is a co-founder of Axiom. He wrote the June 2020 funding post signed by the Axiom co-founders and the company's 2025 year-in-review and August 2026 redesign posts on the Axiom blog.", "bioSources": [ "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "https://axiom.co/blog/year-in-review-2025", "https://axiom.co/blog/a-new-look-for-the-modern-machine-data-platform" ], "page": "/people/neil-jagdish-patel/" } ], "peopleNote": "Axiom's June 2020 funding post is signed Neil, Gord, and Seif, Axiom Co-Founders, and is authored by Neil Jagdish Patel; the other two co-founders appear only by first name on axiom.co, and no first-hand page gives their full names or current roles, so the roster is incomplete and no title beyond co-founder is recorded. The company page describes a remote team without naming anyone. Investors are from the same 2020 post, which names the round's investors and says LocalGlobe led the previous round; no later round was found on the blog's company category, the pricing page or the docs.", "companySocial": { "linkedin": "https://www.linkedin.com/company/axiomhq", "x": "https://x.com/axiomhq", "github": "https://github.com/axiomhq" }, "support": { "emails": [ "support@axiom.co" ], "urls": [ "https://axiom.co/docs/console/intelligence/mcp-server", "https://axiom.co/docs" ], "contactEmails": [ "privacy@axiom.co", "security@axiom.co" ], "contactUrls": [ "https://axiom.co/company" ] }, "sources": [ "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "https://axiom.co/blog/year-in-review-2025", "https://axiom.co/blog/a-new-look-for-the-modern-machine-data-platform", "https://axiom.co/blog/category/company", "https://axiom.co/company", "https://axiom.co/docs/console/intelligence/mcp-server", "https://axiom.co/docs/platform-overview/security", "https://axiom.co/docs/legal/terms-of-service" ], "ownership": { "status": "private", "totalRaised": { "amount": "$7M", "asOf": "2020-06", "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches" }, "checked": "2026-11-03", "sources": [ "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "https://axiom.co/docs/legal/terms-of-service" ] }, "investors": [ { "name": "Crane Venture Partners", "kind": "vc", "rounds": [ "$7M round, June 2020" ], "url": "https://crane.vc", "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "Axiom has raised $7M from Crane Ventures, Fly Ventures, Mango Capital, and LocalGlobe, who led our previous round.", "page": "/investors/crane-venture-partners/" }, { "name": "Fly Ventures", "kind": "vc", "rounds": [ "$7M round, June 2020" ], "url": "https://www.fly.vc", "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "Axiom has raised $7M from Crane Ventures, Fly Ventures, Mango Capital, and LocalGlobe", "page": "/investors/fly-ventures/" }, { "name": "Mango Capital", "kind": "vc", "rounds": [ "$7M round, June 2020" ], "url": "https://mangocap.com", "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "Axiom has raised $7M from Crane Ventures, Fly Ventures, Mango Capital, and LocalGlobe", "page": "/investors/mango-capital/" }, { "name": "LocalGlobe", "kind": "vc", "rounds": [ "Previous round, before June 2020", "$7M round, June 2020" ], "lead": true, "url": "https://localglobe.vc", "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "LocalGlobe, who led our previous round", "page": "/investors/localglobe/" }, { "name": "Nat Friedman", "kind": "angel", "rounds": [ "$7M round, June 2020" ], "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "Angel investors include former Xamarin founder and GitHub CEO Nat Friedman", "page": "/investors/nat-friedman/" }, { "name": "Adam Wiggins", "kind": "angel", "rounds": [ "$7M round, June 2020" ], "source": "https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches", "quote": "Angel investors include former Xamarin founder and GitHub CEO Nat Friedman and Heroku co-founder Adam Wiggins", "page": "/investors/adam-wiggins/" } ] }, "pageJsonUrl": "https://www.anchorterminal.com/tools/axiom.json", "live": { "slug": "axiom", "probe": { "target": "https://mcp.axiom.co/mcp", "method": "mcp-initialize", "lastAt": "2026-11-04T20:04:51.175272228Z", "lastOk": true, "lastStatus": 401, "lastMs": 133, "lastNote": "asks for credentials", "authRequired": true, "uptime24h": 100, "uptime30d": 100, "p50ms24h": 85, "p95ms24h": 171, "samples24h": 48, "samples30d": 48, "days": [ { "date": "2026-11-04", "probes": 48, "ok": 48 } ] }, "vendorStatus": { "page": "https://status.axiom.co", "indicator": "none", "summary": "All Systems Operational", "checkedAt": "2026-11-04T20:04:40.498454391Z" }, "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-04T20:04:51.175272228Z" } }, "verify": { "accepts": "a page on axiom.co or one of its subdomains", "badgeUrl": "https://www.anchorterminal.com/badges/axiom.svg", "body": { "slug": "axiom", "url": "the page with the badge or the link" }, "docs": "https://www.anchorterminal.com/builders/#verify", "effect": "none, it never changes a grade, rank or review", "endpoint": "https://www.anchorterminal.com/api/v1/verify", "listingUrl": "https://www.anchorterminal.com/tools/axiom", "mcpTool": "verify_listing", "recheck": "weekly; two failed checks in a row and it lapses, a later pass restores it", "snippets": { "html": "\u003ca href=\"https://www.anchorterminal.com/tools/axiom\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/axiom.svg\" alt=\"Axiom MCP Server on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e", "markdown": "[![Axiom MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/axiom.svg)](https://www.anchorterminal.com/tools/axiom)", "link": "\u003ca href=\"https://www.anchorterminal.com/tools/axiom\"\u003eAxiom MCP Server on Anchor Terminal\u003c/a\u003e" } } }, "kind": "anchor.page", "links": { "api": "https://www.anchorterminal.com/api/v1/index.json", "html": "https://www.anchorterminal.com/tools/axiom", "json": "https://www.anchorterminal.com/tools/axiom.json", "llms": "https://www.anchorterminal.com/llms.txt", "markdown": "https://www.anchorterminal.com/tools/axiom.md", "mcp": "https://www.anchorterminal.com/mcp", "pricing": "https://www.anchorterminal.com/tools/axiom#pricing", "reviews": "https://www.anchorterminal.com/tools/axiom#reviews", "slim": "https://www.anchorterminal.com/tools/axiom.min.md" }, "markdown": "## Overview\n\n**Grade B · 68.2/100 · rank #264 of 1349 · #3 in Observability \u0026 incidents · not agent-ready · confidence medium**\n\n\n## Assessment\n\nAn 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## Facts\n\n| Field | Value |\n| --- | --- |\n| Vendor | Axiom, Inc. (https://axiom.co) |\n| Kind | MCP server |\n| Category | Observability \u0026 incidents (https://www.anchorterminal.com/categories/observability) |\n| Transport | Streamable HTTP, SSE (legacy) |\n| Endpoint | `https://mcp.axiom.co/mcp` |\n| Auth | OAuth · 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. |\n| Pricing | Freemium ($25 / mo) · 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). |\n| x402 | No · 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. |\n| Licence | unknown |\n| Tools exposed | 31 |\n| MCP registry name | `co.axiom/mcp` |\n| Docs | https://axiom.co/docs/console/intelligence/mcp-server |\n| llms.txt | https://axiom.co/llms.txt |\n| Last release | 2026-10-29 |\n| Surface listed | The hosted MCP server at mcp.axiom.co and mcp.eu.axiom.co, read from the Markdown twins of axiom.co/docs (MCP server, tools reference, AI agents, agent-created organisations, query cost limits, API limits, tokens, limits, pagination, audit log, security, terms, privacy, SLA, DPA), axiom.co (pricing, changelog, company, security, llms.txt), status.axiom.co and its feed, app.axiom.co/.well-known/security.txt and the MCP registry on 3 November 2026. No account was used, no organisation provisioned and no tool called |\n| Tools | Reads are queryDataset, getSavedQueries, listDatasets, getDatasetFields, listMetrics, listMetricTags, getMetricTagValues, searchMetrics, queryMetrics, listDashboards, getDashboard, exportDashboard, checkMonitors, getMonitor, getMonitorHistory, listNotifiers, services-getMap, services-getChanges and services-getEdgeHistory. Writes are createDataset, createDashboard, updateDashboard, updateDashboardChart, deleteDashboard, createMonitor, updateMonitor, deleteMonitor, createNotifier, updateNotifier, deleteNotifier and sendFeedback |\n| Prompts | explore-unknown-dataset, detect-anomalies-in-events, correlate-events-across-datasets, data-quality-investigation, establish-performance-baseline, monitor-health-analysis, investigate-service-topology. Resources are planned |\n| Rate and cost limits | Rate limits per user and organisation stated by X-RateLimit-Scope, -Limit, -Remaining and -Reset headers, 429 with a message when exceeded; query limits in GB-milliseconds by plan in X-QueryLimit headers; query cost limits in dollars per hour and day on tokens and roles, 429 past the cap; provisioning capped at 3 organisations a day |\n| Regions | US server at mcp.axiom.co handles query results worldwide; EU server at mcp.eu.axiom.co keeps query results in EU data centres; sign-in and non-query requests go to the US API from both |\n| Agent-created organisations | Unauthenticated provisioning returns an organisation id, a full-permission token and a single-use claim URL; 24-hour expiry, 10 GB ingest and 1 GB-hour query compute while unclaimed, notifiers disabled until claimed |\n| Audit | Audit log on every organisation for the previous 30 days, full history as an add-on; OAuth sessions listed and revocable under Settings \u003e Profile |\n| Compliance | ISO 27001, SOC 2 Type II, GDPR DPA, HIPAA BAA as a self-serve add-on with RBAC, SSO and audit log, data on AWS encrypted with AES-256, sub-processor list on the trust centre, security.txt and a bug bounty policy |\n| Legal entity | Axiom, Inc., terms under California law, privacy and DPA contacts at privacy@axiom.co |\n| Capabilities | observability.logs, observability.traces, observability.metrics, observability.incidents, observability.errors |\n| 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 |\n| JSON | https://www.anchorterminal.com/api/v1/tools/axiom.json |\n\n## Score breakdown (methodology v0.7, October 2026 research run)\n\nAssessed 2026-11-03 from public evidence against the published checklist (https://www.anchorterminal.com/benchmark/#checklist). Confidence: medium. Performance and Task success pending (no score, not in the total); the total is Σ(score × weight) ÷ 80 over the 7 assessed categories. \"This run\" is each category's share of the 100 points.\n\n| Category | Weight | This run | Score (0–100) | Points |\n| --- | --- | --- | --- | --- |\n| Reliability | 16% | 20 | 72 | 14.4 |\n| Performance | 10% | pending | pending | n/a |\n| Schema \u0026 documentation | 13% | 16.2 | 62 | 10.1 |\n| Agent ergonomics | 13% | 16.2 | 63 | 10.2 |\n| Security \u0026 auth | 14% | 17.5 | 72 | 12.6 |\n| Payments \u0026 pricing | 10% | 12.5 | 60 | 7.5 |\n| Task success | 10% | pending | pending | n/a |\n| Maintenance \u0026 community | 7% | 8.8 | 83 | 7.3 |\n| Transparency \u0026 trust (editorial 57, provenance 83) | 7% | 8.8 | 70 | 6.1 |\n| Negative events | up to −15 | up to −15 | none recorded | 0 |\n| **Total** | | | | **68.2 → B** |\n\n### Why each score\n\n- Reliability 72 (checked 2026-11-03): 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- Performance: Pending. Latency is measured per call by our probes, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until the first probe window closes.\n- Schema \u0026 documentation 62 (checked 2026-11-03): 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- Agent ergonomics 63 (checked 2026-11-03): 31 tools in the reference, 28 without service map, so the 11-to-30 band with no toolset switch (15). APL queries take their own limits and time ranges, and the REST API documents timestamp pagination; nothing documents page sizes for the list tools (15). 429 bodies state the limit and reset, the REST docs describe error shapes, and a `sendFeedback` tool reports unclear descriptions to Axiom (12). Reads and writes are labelled in the docs, but delete tools have no confirmation step, no idempotency keys exist for writes, and annotations weren't confirmed (8). One-command setup for 16 clients with OAuth, a setup prompt for agents, and official SDKs in eight languages for the API behind it (13). 15 + 15 + 12 + 8 + 13 = 63.\n- Security \u0026 auth 72 (checked 2026-11-03): Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings \u003e Profile, and the docs say agents never see tokens; the header route uses a personal access token with full account rights, and the organisation id, not a secret, may go in the URL (26). Query cost limits on roles cap what an OAuth session can spend, scoped API tokens with expiry exist for the REST API, but the MCP server runs with the user's whole role and lists delete tools with no confirmation, and the AI agents page's read-only description contradicts the tools reference (12). Log, trace and event content is untrusted text and no injection guidance was found (2). An audit log on every organisation for 30 days, full history as an add-on, and session listing (12). ISO 27001, SOC 2 Type II, a security.txt on app.axiom.co, a bug bounty policy at axiom.co/security and annual penetration tests (20). 26 + 12 + 2 + 12 + 20 = 72.\n- Payments \u0026 pricing 60 (checked 2026-11-03): 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- Task success: Pending. Task success needs the category task suites run through each tool, which haven't run yet, so this run doesn't score it. Its weight is shared across the assessed categories until then. A data provider's data-quality score is published on its listing now and becomes half of this category when it's scored.\n- Maintenance \u0026 community 83 (checked 2026-11-03): Read as a closed service. Changelog entry of 29 October 2026 covering the MCP server (30). Dated entries on 7 August, 23 September and 16, 21, 22, 28 and 29 October 2026 (20). A Discord community linked from the company page, support@axiom.co in the docs and email support on paid plans; no public issue tracker for the hosted server (12 of 15). co.axiom/mcp in the official registry under a DNS-verified namespace since 30 September 2025, though the entry still points at the SSE URL and version 1.0.0 (15). No package to assess for a hosted server; Axiom keeps SDKs in eight languages for the API (6). 30 + 20 + 12 + 15 + 6 = 83.\n- Transparency \u0026 trust 70 (checked 2026-11-03): 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\nFix list, everything this grade says the listing lacks, the biggest gain first (17 items). What it covers is at https://www.anchorterminal.com/fixes/axiom.md (JSON https://www.anchorterminal.com/fixes/axiom.json). The whole list for a coding agent comes from `POST https://www.anchorterminal.com/api/v1/fix-list` with `{\"listing\": \"axiom\", \"plan\": \"read\"}`, free while the beta runs\n\n### What we couldn't check\n\n- unchecked: the live tools/list, input schemas and annotations, which need an OAuth session; the count of 31 tools is from the tools reference\n- unchecked: the sub-processor list at trust.axiom.co/subprocessors (script-rendered) and the terms' last-updated date, which the Markdown text doesn't carry\n- unchecked: the registration date of axiom.co; the .co registry's RDAP answered 502 and rdap.org returned no record\n- The AI agents overview says the MCP server gives curated, read-only operations with no risk of destructive actions, while the tools reference lists createDataset and create, update and delete tools for dashboards, monitors and notifiers; recorded in the security and ergonomics scores, not as a deduction\n- firstReleased is 5 December 2024, the first tag of the deprecated open-source mcp-server-axiom; the hosted server's first date isn't on a first-hand page, and its registry entry is from 30 September 2025\n- Judgement call on reliability. Nine incidents in 90 days, mostly short query error spikes, were scored as one major on the 70-minute US query incident of 14 October 2026 rather than several majors, because the other entries carry no durations\n\n### Sources\n\n- MCP server docs (setup, header auth, token hygiene, revocation): \u003chttps://axiom.co/docs/console/intelligence/mcp-server\u003e (seen 2026-11-03)\n- MCP tools reference: \u003chttps://axiom.co/docs/console/intelligence/mcp-server/tools\u003e (seen 2026-11-03)\n- AI agents overview: \u003chttps://axiom.co/docs/console/intelligence/ai-agents-overview\u003e (seen 2026-11-03)\n- agent-created organisations: \u003chttps://axiom.co/docs/console/intelligence/agent-created-orgs\u003e (seen 2026-11-03)\n- query cost limits: \u003chttps://axiom.co/docs/console/intelligence/query-cost-limits\u003e (seen 2026-11-03)\n- API limits (rate limit headers, 429): \u003chttps://axiom.co/docs/restapi/api-limits\u003e (seen 2026-11-03)\n- tokens: \u003chttps://axiom.co/docs/reference/tokens\u003e (seen 2026-11-03)\n- limits: \u003chttps://axiom.co/docs/reference/limits\u003e (seen 2026-11-03)\n- pagination: \u003chttps://axiom.co/docs/restapi/pagination\u003e (seen 2026-11-03)\n- audit log: \u003chttps://axiom.co/docs/reference/audit-log\u003e (seen 2026-11-03)\n- security and compliance: \u003chttps://axiom.co/docs/platform-overview/security\u003e (seen 2026-11-03)\n- SLA: \u003chttps://axiom.co/docs/legal/sla\u003e (seen 2026-11-03)\n- terms of service: \u003chttps://axiom.co/docs/legal/terms-of-service\u003e (seen 2026-11-03)\n- privacy policy: \u003chttps://axiom.co/docs/legal/privacy\u003e (seen 2026-11-03)\n- data processing addendum: \u003chttps://axiom.co/docs/legal/data-processing\u003e (seen 2026-11-03)\n- pricing: \u003chttps://axiom.co/pricing\u003e (seen 2026-11-03)\n- changelog: \u003chttps://axiom.co/changelog\u003e (seen 2026-11-03)\n- agent-created organisations changelog entry: \u003chttps://axiom.co/changelog/agent-created-organizations\u003e (seen 2026-11-03)\n- security and bug bounty policy: \u003chttps://axiom.co/security\u003e (seen 2026-11-03)\n- security.txt: \u003chttps://app.axiom.co/.well-known/security.txt\u003e (seen 2026-11-03)\n- llms.txt: \u003chttps://axiom.co/llms.txt\u003e (seen 2026-11-03)\n- status page: \u003chttps://status.axiom.co/\u003e (seen 2026-11-03)\n- status feed: \u003chttps://status.axiom.co/feed.rss\u003e (seen 2026-11-03)\n- MCP registry entry: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=axiom\u003e (seen 2026-11-03)\n- deprecated open-source server, shallow clone: \u003chttps://github.com/axiomhq/mcp-server-axiom\u003e (seen 2026-11-03)\n- robots.txt: \u003chttps://axiom.co/robots.txt\u003e (seen 2026-11-03)\n\n## Score history\n\nEvery move of a score since the listing was graded, newest first, with its cause. A score can't move without an entry here. JSON: https://www.anchorterminal.com/api/v1/tools/axiom/history.json\n\n- 2026-11-03: graded 68.2 B (methodology 0.7)\n\n## Who's behind it (provenance 83/100, checked 2026-11-03)\n\n| Check | Finding | Points |\n| --- | --- | --- |\n| Legal entity named | Axiom, Inc. | 20/20 |\n| Domain age | axiom.co, no registry record we could read | 0/15 |\n| Endpoint on the vendor's domain | mcp.axiom.co | 15/15 |\n| Terms of service | read, states 4 of the 7 things a reader expects | 7.4/10 |\n| Privacy policy | read, states 7 of the 8 things a reader expects | 9.3/10 |\n| Status page | status.axiom.co | 10/10 |\n| Changelog | published | 10/10 |\n| security.txt | valid | 10/10 |\n| People named | 1 named with their role, none with a public profile | 7/10 |\n| Support route | a support address, help pages | 5/5 |\n\nThe 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.\n\naxiom.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.\n\naxiom.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.\n\nstatus.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.\n\nRDAP 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.\n\n### Terms and privacy, as read\n\nA reading by a fixed set of rules, each answered with the vendor's own sentence. Not legal advice.\n\n**Terms of service** (https://axiom.co/docs/legal/terms-of-service), read 2026-11-03, gives no date, states 4 of the 7 things a reader expects.\n\n- Not found in the text. Gives the date it was last updated.\n- Names the governing law or courts. The law of the State of California.\n- States a limit on its liability. Capped at the fees paid in the 12 months before the claim.\n- Not found in the text. Says how changes to the terms are announced.\n- Not found in the text. Refers to a service level or uptime commitment.\n- Also in the text (2026-11-03). Customer Data may be irretrievably deleted fifteen days after the agreement ends. \"Customer acknowledges and agrees that Customer Data may be irretrievably deleted after fifteen (15) days following a termination or expiration of this Agreement.\"\n- Also in the text (2026-11-03). Service terms renew automatically at then-current on-demand standard rates unless either party gives thirty days' written notice of non-renewal. \"Customer acknowledges and agrees that each Service Renewal shall be subject to the then-current, on-demand standard use rates, unless otherwise specified in the applicable Service Description.\"\n- Also in the text (2026-11-03). If the agreement is terminated for material breach, the customer pays all fees set out in the Service Description. \"If the Agreement is terminated due to Section 3.2 (a), Customer shall pay to Axiom all Fees set forth in the corresponding Service Description(s).\"\n\n**Privacy policy** (https://axiom.co/docs/legal/privacy), read 2026-11-03, gives no date, states 7 of the 8 things a reader expects.\n\n- To know. Says it sells personal data or shares it for advertising. \"Some of these disclosures may constitute a “sale” of your Personal Data as defined under applicable laws.\"\n- Not found in the text. Gives the date it was last updated.\n- Says how long data is kept. For as long as needed, with no period named.\n- Says whether personal data is sold or shared for advertising. Says it does not sell personal data.\n- Gives a privacy contact. privacy@axiom.co.\n\n## Humans behind the project (researched 2026-11-03 from public pages, not part of the grade)\n\n### Key people\n\n- Neil Jagdish Patel, Co-founder\n- Note: Axiom's June 2020 funding post is signed Neil, Gord, and Seif, Axiom Co-Founders, and is authored by Neil Jagdish Patel; the other two co-founders appear only by first name on axiom.co, and no first-hand page gives their full names or current roles, so the roster is incomplete and no title beyond co-founder is recorded. The company page describes a remote team without naming anyone. Investors are from the same 2020 post, which names the round's investors and says LocalGlobe led the previous round; no later round was found on the blog's company category, the pricing page or the docs.\n- Axiom: LinkedIn https://www.linkedin.com/company/axiomhq X https://x.com/axiomhq GitHub https://github.com/axiomhq\n\n### Ownership and investors\n\n- Raised: $7M in total, as of June 2020 (source https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches)\n- Backed by: Crane Venture Partners, Fly Ventures, Mango Capital, LocalGlobe, Nat Friedman, Adam Wiggins\n\n### Getting support\n\n- Support email: support@axiom.co\n- Help: https://axiom.co/docs/console/intelligence/mcp-server\n- Help: https://axiom.co/docs\n- Sources: https://axiom.co/blog/axiom-raises-7m-to-cure-data-headaches, https://axiom.co/blog/year-in-review-2025, https://axiom.co/blog/a-new-look-for-the-modern-machine-data-platform, https://axiom.co/blog/category/company, https://axiom.co/company, https://axiom.co/docs/console/intelligence/mcp-server, https://axiom.co/docs/platform-overview/security, https://axiom.co/docs/legal/terms-of-service\n\n## Live (updated 2026-11-04 20:04 UTC)\n\n- Right now: up, HTTP 401, 133 ms, checked 2026-11-04 20:04 UTC (mcp-initialize on `https://mcp.axiom.co/mcp`, asks for auth)\n- Uptime 24h 100.0% (48 probes) · 30 days 100.0% (48 probes) · p50 85 ms · p95 171 ms\n- Vendor status page: none, All Systems Operational\n- mcp-registry `co.axiom/mcp` 1.0.0\n- security.txt: valid, expires 2027-04-01T00:01:00Z\n- Always current: https://www.anchorterminal.com/api/v1/live/axiom.json\n\n## Probe metrics\n\nNot measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. Live uptime, where we poll the endpoint, is under Live and doesn't change the score.\n\n## Prices\n\n| Item | Price | Unit | Note |\n| --- | --- | --- | --- |\n| Axiom Cloud platform fee | $25 | per month (plan) | Plus usage beyond the Always Free allowance of 1 TB loading, 100 GB-hours query and 100 GB storage a month |\n| Role-based access control add-on | $50 | per month (plan) | Extended audit logs $50, SAML SSO $100, directory sync $100 |\n\nAcross all listings: https://www.anchorterminal.com/prices/index.md\n\n## Strengths\n\n- `POST /v2/orgs/provision` needs no account and returns a working token; a person claims the organisation later or it expires in 24 hours\n- 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\n- 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\n- 99.9 per cent monthly uptime SLA with service credits, published rate-limit headers and a status page with per-component uptime\n- Dated changelog with MCP entries, llms.txt, Markdown twins of every docs page and setup for 16 clients\n\n## Weaknesses\n\n- The server is closed source and tool input schemas are only visible through an authenticated session\n- The AI agents overview calls the MCP server read-only while the tools reference lists delete tools for dashboards, monitors and notifiers\n- 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\n- Nine status incidents between 12 August and 30 October 2026, mostly elevated query errors, one of 70 minutes in the US\n- 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\n\n\n\n## Before you call it (notes for agents)\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## Connect\n\nInstall:\n\n```bash\nnpx -y add-mcp https://mcp.axiom.co/mcp -g\n```\n\nFirst request:\n\n```bash\ncurl -X POST https://api.axiom.co/v2/orgs/provision -H 'Content-Type: application/json' -d '{\"name\":\"agent-sandbox\"}'\n```\n\nClaude Code:\n\n```bash\nclaude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp\n```\n\nMCP client configuration:\n\n```json\n{\n \"mcpServers\": {\n \"axiom\": {\n \"url\": \"https://mcp.axiom.co/mcp\"\n }\n }\n}\n```\n\nThrough letme: https://letme.dev/axiom. letme answers with the pick and how to call it direct. How it works: https://www.anchorterminal.com/letme/index.md\n\n## Similar tools\n\nRanked by shared capabilities, then score. Same-category tools with no shared capability key are listed last.\n\n| Tool | Grade | Score | Rank | Shared capabilities | x402 | Markdown |\n| --- | --- | --- | --- | --- | --- | --- |\n| New Relic MCP Server | C | 61 | 528 | observability.metrics, observability.logs, observability.errors, observability.traces, observability.incidents | no | https://www.anchorterminal.com/tools/new-relic.md |\n| Better Stack | C | 54.2 | 878 | observability.logs, observability.incidents, observability.metrics, observability.traces, observability.errors | no | https://www.anchorterminal.com/tools/better-stack.md |\n| Grafana MCP Server | BB | 71 | 154 | observability.metrics, observability.logs, observability.traces, observability.incidents | no | https://www.anchorterminal.com/tools/grafana-mcp-server.md |\n| Datadog MCP Server | C | 56.8 | 766 | observability.metrics, observability.logs, observability.traces, observability.incidents | no | https://www.anchorterminal.com/tools/datadog-mcp.md |\n| Causely MCP server | E | 39.5 | 1218 | observability.incidents, observability.metrics, observability.logs, observability.errors | no | https://www.anchorterminal.com/tools/causely.md |\n| Honeycomb MCP | C | 58.5 | 679 | observability.traces, observability.metrics, observability.logs | no | https://www.anchorterminal.com/tools/honeycomb-mcp.md |\n\n## Panel reviews (0)\n\nReviewed by the Anchor panel (https://www.anchorterminal.com/reviewers/index.md): .\n\nDesk reviews, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. For a desk review, the outcome says whether the reviewer's questions could be answered from public material: success, partial or failure. How reviews work: https://www.anchorterminal.com/reviews/how-it-works.md\n\n## Notable\n\n- 31 tools in the tools reference, 20 reads (query, datasets, metrics, dashboards, monitors, service map) and 11 writes (create dataset, create, update and delete dashboards, monitors and notifiers, send feedback), plus seven prebuilt prompts; the three service-map tools appear only when service map is enabled (source: \u003chttps://axiom.co/docs/console/intelligence/mcp-server/tools\u003e)\n- An agent can create a real organisation with one unauthenticated `POST https://api.axiom.co/v2/orgs/provision`, which returns a full-permission API token and a claim URL; the organisation is deleted after 24 hours unless a person claims it, with 10 GB of ingest, 1 GB-hour of query compute and at most 3 organisations a day meanwhile (source: \u003chttps://axiom.co/docs/console/intelligence/agent-created-orgs\u003e)\n- Query cost limits cap an identity's query spend per hour and per day in dollars; over the limit, queries fail with 429 until the window resets. They apply to API tokens and to roles, which is how OAuth sessions through the MCP server are capped (source: \u003chttps://axiom.co/docs/console/intelligence/query-cost-limits\u003e)\n- The AI agents overview describes the MCP server as curated, read-only operations with no risk of destructive actions, while the tools reference lists delete tools for dashboards, monitors and notifiers (source: \u003chttps://axiom.co/docs/console/intelligence/ai-agents-overview\u003e)\n- The changelog entry of 29 October 2026 adds built-in instructions at session start, two skills that let an agent send data, and support for the 2026-07-28 protocol version alongside the session-based transport (source: \u003chttps://axiom.co/changelog\u003e)\n- Published SLA of 99.9 per cent monthly uptime for Axiom Cloud with 10 and 25 per cent credits, and an incident.io status page showing 99.90 per cent querying uptime in the US from August to November 2026 (source: \u003chttps://axiom.co/docs/legal/sla\u003e)\n- Listed in the official MCP registry as co.axiom/mcp 1.0.0 on 30 September 2025 with the SSE URL https://mcp.axiom.co/sse; the linked repository axiomhq/mcp is not public and the older open-source mcp-server-axiom is deprecated (source: \u003chttps://registry.modelcontextprotocol.io/v0/servers?search=axiom\u003e)\n\n- #3 of 11 in 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## Compare\n\n- [Axiom MCP Server vs incident.io API](https://www.anchorterminal.com/compare/axiom-vs-incident-io.md): B 68.2 vs B 68.9\n- [Axiom MCP Server vs PagerDuty MCP Server](https://www.anchorterminal.com/compare/axiom-vs-pagerduty-mcp.md): B 68.2 vs D 48.6\n- [Axiom MCP Server vs Rootly MCP Server](https://www.anchorterminal.com/compare/axiom-vs-rootly-mcp.md): B 68.2 vs C 59.8\n- [Axiom MCP Server vs Better Stack](https://www.anchorterminal.com/compare/axiom-vs-better-stack.md): B 68.2 vs C 54.2\n- [Axiom MCP Server vs Causely MCP server](https://www.anchorterminal.com/compare/axiom-vs-causely.md): B 68.2 vs E 39.5\n- [Axiom MCP Server vs Datadog MCP Server](https://www.anchorterminal.com/compare/axiom-vs-datadog-mcp.md): B 68.2 vs C 56.8\n- [Axiom MCP Server vs Grafana MCP Server](https://www.anchorterminal.com/compare/axiom-vs-grafana-mcp-server.md): B 68.2 vs BB 71\n- [Axiom MCP Server vs Honeycomb MCP](https://www.anchorterminal.com/compare/axiom-vs-honeycomb-mcp.md): B 68.2 vs C 58.5\n- [Axiom MCP Server vs New Relic MCP Server](https://www.anchorterminal.com/compare/axiom-vs-new-relic.md): B 68.2 vs C 61\n- [Axiom MCP Server vs Sentry MCP](https://www.anchorterminal.com/compare/axiom-vs-sentry-mcp.md): B 68.2 vs B 66.2\n\n## Verify this listing\n\nFor the vendor. The badge or a plain link to this page verifies the listing, from a page on axiom.co or one of its subdomains. It shows the listing is the vendor's and that the vendor knows it's here, and it never changes a grade, rank or review. The vendor sends the page's address to `POST https://www.anchorterminal.com/api/v1/verify` as `{\"slug\": \"axiom\", \"url\": \"…\"}`, or calls the `verify_listing` tool at https://www.anchorterminal.com/mcp. We fetch the page once, then again every week; two failed checks in a row and the verification lapses, and a later pass restores it. What we check: https://www.anchorterminal.com/builders/index.md#verify\n\nHTML badge:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/axiom\"\u003e\u003cimg src=\"https://www.anchorterminal.com/badges/axiom.svg\" alt=\"Axiom MCP Server on Anchor Terminal\" height=\"20\"\u003e\u003c/a\u003e\n```\n\nMarkdown badge, for a README:\n\n```markdown\n[![Axiom MCP Server on Anchor Terminal](https://www.anchorterminal.com/badges/axiom.svg)](https://www.anchorterminal.com/tools/axiom)\n```\n\nPlain link:\n\n```html\n\u003ca href=\"https://www.anchorterminal.com/tools/axiom\"\u003eAxiom MCP Server on Anchor Terminal\u003c/a\u003e\n```\n\n## Share this listing\n\nFor the vendor. Sharing assets for social media, two PNGs of 1200 × 630 that say Axiom MCP Server is listed on Anchor Terminal, with the vendor's logo and this page's address and no grade or score.\n\n- Dark: https://www.anchorterminal.com/assets/share/axiom-dark.png\n- Light: https://www.anchorterminal.com/assets/share/axiom-light.png\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": "Terminal", "url": "https://www.anchorterminal.com/tools/" }, { "name": "Observability \u0026 incidents", "url": "https://www.anchorterminal.com/categories/observability" }, { "name": "Axiom MCP Server", "url": "" } ], "description": "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.", "facts": [ "rank #264 of 1349", "OAuth auth", "0 desk reviews" ], "h1": "Axiom MCP Server", "image": "https://www.anchorterminal.com/assets/og/tools-axiom.png", "path": "/tools/axiom", "published": "2026-10-01", "section": "tools", "title": "Axiom review (2026): pricing, alternatives and grade B", "toc": null, "updated": "2026-11-04", "url": "https://www.anchorterminal.com/tools/axiom" }, "tokens": { "markdown": 8550, "slim": 1980 }, "version": 1 }