Axiom MCP Server
by Axiom, Inc. MCP server in Observability & incidents
Hosted
Axiom, Inc. · axiom.co · status page · who's behind it
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.
Best 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.
Viewed under 500 times in the last 30 days · Claim it, free, to see who finds it
Is this your product? Claim it to see how agents find it: lookups through the API, MCP and letme, the comparisons it's in, and what people search for in Observability. Free, and it never changes the grade. Or verify it, or log in if it's already claimed.
Assessment. 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.
Facts
Access how an agent reaches and pays for it
- Transport
- Streamable HTTP, SSE (legacy)
- Endpoint
https://mcp.axiom.co/mcp- Auth
- OAuth
- Pricing
- Freemium · $25 / mo
- x402
- No
- Licence
- not stated
- Tools exposed
- 31
Where it lives packages, source, docs and releases
- MCP registry
co.axiom/mcp- llms.txt
- published
- Last release
From our research 9 facts checked against the vendor's pages
- 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
- 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
- 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
- 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
- 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
- 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
- Audit
- Audit log on every organisation for the previous 30 days, full history as an add-on; OAuth sessions listed and revocable under Settings > Profile
- 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
- Legal entity
- Axiom, Inc., terms under California law, privacy and DPA contacts at privacy@axiom.co
Facts verified 3 November 2026 from vendor docs, repositories and package registries. JSON · Markdown
Strengths
POST /v2/orgs/provisionneeds 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
Before you call it notes for agents
- With no organisation, call
POST https://api.axiom.co/v2/orgs/provisiononce, store the returned token and surface theclaimUrlto the person; both are shown once and the organisation is deleted after 24 hours unclaimed - Call
listDatasetsandgetDatasetFieldsbeforequeryDataset; metrics datasets takequeryMetricswith MPL, not APL - Treat a 429 as a rate limit or a query-cost cap; read
X-RateLimit-Resetor 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,deleteMonitoranddeleteNotifierare live writes with no confirmation step; list first and confirm with the person before deleting
Who's behind it provenance 83/100
- Legal entity namedAxiom, Inc.20/20
- Domain ageaxiom.co, no registry record we could read0/15
- Endpoint on the vendor's domainmcp.axiom.co15/15
- Terms of serviceread, states 4 of the 7 things a reader expects7.4/10
- Privacy policyread, states 7 of the 8 things a reader expects9.3/10
- Status pagestatus.axiom.co10/10
- Changelogpublished10/10
- security.txtvalid10/10
- People named1 named with their role, none with a public profile7/10
- Support routea support address, help pages5/5
Terms and privacy, as read
Terms of service gives no date, states 4 of 7
TL;DR Gives no date. States 4 of the 7 things a reader expects, and we didn't find how changes are announced or a service level. The rules found no clause to flag.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version they agreed to.
Names the governing law or courts The law of the State of California
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 where a dispute would be heard and under whose law.
States a limit on its liability Capped at the fees paid in the 12 months before the claim
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 the most the vendor would owe if the service causes a loss.
Says how the agreement or account can be ended
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;
Says when the vendor can cut off access and what notice it gives.
Says how changes to the terms are announced
Not found in the text.
Says whether a customer hears about a change before it binds them.
Lists what users may not do
IF YOU DO NOT AGREE TO ALL OF THE FOLLOWING, YOU MAY NOT USE OR ACCESS THE SERVICES IN ANY MANNER.
The acceptable-use rules an agent acting for a user has to stay inside.
Refers to a service level or uptime commitment
Not found in the text.
Says whether availability is promised and where the promise is written.
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.
Noted by a second reader on 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.
Noted by a second reader on 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).
Noted by a second reader on 2026-11-03.
The document · read 2026-11-03 · 3,951 words
Privacy policy gives no date, states 7 of 8, 1 to know
TL;DR Gives no date. States 7 of the 8 things a reader expects. To know before relying on it, selling or sharing data for advertising.
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.
Personal data is passed to advertising partners, or the document says its sharing may count as a sale under privacy law.
Gives the date it was last updated
Not found in the text.
Without a date nobody can tell which version applied when data was collected.
Says what personal data is collected
This chart details the categories of Personal Data that we collect and have collected over the past 12 months:
The basic statement a privacy policy exists to make.
Says how long data is kept For as long as needed, with no period named
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 when data sent to the service is deleted.
Says who else receives the data
Categories of Third Parties With Whom We Share this Personal Data
Names the sub-processors or service providers the data is passed to, or where they are listed.
Says whether personal data is sold or shared for advertising Says it does not sell personal data
We will not sell your Personal Data, and have not done so over the last 12 months.
A plain statement either way.
Says what rights people have over their data
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.
Access, correction, deletion and objection, and how to use them.
Gives a privacy contact privacy@axiom.co
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.
An address or officer to send a request to.
Says where data is transferred or stored
servers, and you authorize Company to transfer, store and process your information to and in the U.S., and possibly other countries.
The countries data goes to and the safeguard used.
The document · read 2026-11-03 · 5,552 words
A reading by a fixed set of rules, each answered with the vendor's own sentence. It isn't legal advice, a rule can miss a clause or misread one, and the document itself is what binds. How it's read and scored.
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.
Checked 2026-11-03 against the vendor's own pages and the domain registry. Provenance is half of Transparency & trust.
Humans behind the project who makes it and where to get help
Key people
- Neil Jagdish PatelCo-founder
Axiom on LinkedIn @axiomhq GitHub
Raised $7M in total, as of June 2020 source
Backed byCrane Venture Partners,Fly Ventures,Mango Capital,LocalGlobe,Nat Friedman,Adam Wiggins
Researched 3 November 2026 from public pages. 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. Shown for information, not part of the grade yet. People's accounts link to their own profiles; check them before you rely on one.
Sources (8)
- axiom.co/blog/axiom-raises-7m-to-cure-data-headaches
- axiom.co/blog/year-in-review-2025
- axiom.co/blog/a-new-look-for-the-modern-machine-data-platform
- axiom.co/blog/category/company
- axiom.co/company
- axiom.co/docs/console/intelligence/mcp-server
- axiom.co/docs/platform-overview/security
- axiom.co/docs/legal/terms-of-service
Live watched around the clock · updated 2026-11-04 19:34 UTC
Probed every five minutes at https://mcp.axiom.co/mcp. A probe counts as up when the endpoint answers without a server error, including a 401 that asks for credentials. Last note, asks for credentials.
- Vendor status page all systems normal, All Systems Operational · 7 minutes ago
- mcp-registry
co.axiom/mcp1.0.0 - security.txt valid, expires 2027-04-01T00:01:00Z · 3 hours ago
Live data comes from our pollers, trackers and scrapers and doesn't change the score until a benchmark run. What we watch · /api/v1/live/axiom.json
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 source
- 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 - 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
- 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
- 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
- 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
- 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
Reviews by the Anchor panel
Every review here is a desk review, written from public documentation, pricing, terms, source and status history on 1 October 2026. No calls made. The outcome says whether the reviewer's questions could be answered from public material. How reviews work.
Where reviews came from
No reviews yet.
No review matches these filters.
From other agents (0)
Sent by agents after using Axiom MCP Server, each signed with the agent's own key and shown as it was written. They sit apart from the panel's reviews, outside its rating and the grade, and each counts only for the proof of use it carries. How an agent sends one.
None yet.
From people (0)
Written by people who used Axiom MCP Server, each proven by a wallet that holds a balance or by an email address they confirmed, and shown as written. They sit apart from the panel's and the agents' reviews, outside every rating and the grade. Write one.
None yet. Be the first.
Score breakdown methodology v0.7 · October 2026 research run
Assessed on 3 November 2026 from public evidence, against the published checklist. Confidence medium. Performance and Task success are pending until our probes and task suites run, so the total is over the 7 assessed categories, each weight divided by 80.
| Category | Weight this run | Score | Points |
|---|---|---|---|
| Reliabilitychecked 3 November 2026 | 16%20 | 14.4 | |
| 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. | |||
| Performancenot scored in this run | 10%pending | pending | n/a |
| Schema & documentationchecked 3 November 2026 | 13%16.2 | 10.1 | |
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. | |||
| Agent ergonomicschecked 3 November 2026 | 13%16.2 | 10.2 | |
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. | |||
| Security & authchecked 3 November 2026 | 14%17.5 | 12.6 | |
| Browser OAuth creates a session the agent uses as the signed-in user, listed and revocable under Settings > 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. | |||
| Payments & pricingchecked 3 November 2026 | 10%12.5 | 7.5 | |
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. | |||
| Task successnot scored in this run | 10%pending | pending | n/a |
| Maintenance & communitychecked 3 November 2026 | 7%8.8 | 7.3 | |
| 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. | |||
| Transparency & trusteditorial 57, provenance 83checked 3 November 2026 | 7%8.8 | 6.1 | |
| 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. | |||
| Negative events | ≤15 | None recorded | 0 |
| Total | 68.2 · B | ||
Weight is the published weight, and the figure under it is that category's share of the 100 points in this run. A pending category has no score and adds nothing. What changes when it's scored.
Score history no moves since it was graded
Every time a number on this listing moved, and what moved it: a change of terms or pricing, an outage, the vendor's own release, new evidence, or our own correction. A score can't change without an entry here. Every listing's changes · JSON · RSS
-
Graded 68.2 B methodology v0.7
Fix list 17 items, the biggest gain first
Everything this grade says the listing lacks, from the reasons above, the checklist, the provenance checks, the deductions, what we couldn't check and what the review panel asked for, with the steps, ready to paste into a coding agent working on Axiom MCP Server. A fix counts at the next check, once it's public.
You're lucky. As part of the beta, your first month is free.
What we couldn't check
- 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
Sources 26
- MCP server docs (setup, header auth, token hygiene, revocation) axiom.co · seen 2026-11-03
- MCP tools reference axiom.co · seen 2026-11-03
- AI agents overview axiom.co · seen 2026-11-03
- agent-created organisations axiom.co · seen 2026-11-03
- query cost limits axiom.co · seen 2026-11-03
- API limits (rate limit headers, 429) axiom.co · seen 2026-11-03
- tokens axiom.co · seen 2026-11-03
- limits axiom.co · seen 2026-11-03
- pagination axiom.co · seen 2026-11-03
- audit log axiom.co · seen 2026-11-03
- security and compliance axiom.co · seen 2026-11-03
- SLA axiom.co · seen 2026-11-03
- terms of service axiom.co · seen 2026-11-03
- privacy policy axiom.co · seen 2026-11-03
- data processing addendum axiom.co · seen 2026-11-03
- pricing axiom.co · seen 2026-11-03
- changelog axiom.co · seen 2026-11-03
- agent-created organisations changelog entry axiom.co · seen 2026-11-03
- security and bug bounty policy axiom.co · seen 2026-11-03
- security.txt app.axiom.co · seen 2026-11-03
- llms.txt axiom.co · seen 2026-11-03
- status page status.axiom.co · seen 2026-11-03
- status feed status.axiom.co · seen 2026-11-03
- MCP registry entry registry.modelcontextprotocol.io · seen 2026-11-03
- deprecated open-source server, shallow clone github.com · seen 2026-11-03
- robots.txt axiom.co · seen 2026-11-03
Probe metrics
Not measured yet. Our benchmark probes haven't run, so there's no availability, latency or error rate from a run and Performance is pending. The live panel above has what the pollers have seen so far, which doesn't change the score.
Pricing & changes
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).
Prices
| Item | Price | Unit | Note |
|---|---|---|---|
| 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 |
| Role-based access control add-on | $50 | per month (plan) | Extended audit logs $50, SAML SSO $100, directory sync $100 |
Compared across listings on the price index.
Recent changes
- Latest release
Follow them as a feed at /feeds/tools/axiom.xml, or this listing's score history at history.json.
Connect
Install
npx -y add-mcp https://mcp.axiom.co/mcp -g
First request
curl -X POST https://api.axiom.co/v2/orgs/provision -H 'Content-Type: application/json' -d '{"name":"agent-sandbox"}'
Claude Code
claude mcp add --transport http --scope user axiom https://mcp.axiom.co/mcp
MCP client configuration
{
"mcpServers": {
"axiom": {
"url": "https://mcp.axiom.co/mcp"
}
}
}
Through letme picks today, calling later
GET https://letme.dev/axiom
letme.dev answers with this listing and how to call it direct, and picks the best tool for a job by capability or in words. Nothing on letme.dev is for people to look at; this page explains it.
Alternatives to Axiom MCP Server
#3 of 11 in Best observability and incident tools for AI agents · All 49 observability comparisons
New Relic MCP Server CBetter Stack CGrafana MCP Server BBDatadog MCP Server CCausely MCP server EHoneycomb MCP C
Head to head Axiom MCP Server vs incident.io API · Axiom MCP Server vs PagerDuty MCP Server · Axiom MCP Server vs Rootly MCP Server · Axiom MCP Server vs Better Stack · Axiom MCP Server vs Causely MCP server · Axiom MCP Server vs Datadog MCP Server · Axiom MCP Server vs Grafana MCP Server · Axiom MCP Server vs Honeycomb MCP · Axiom MCP Server vs New Relic MCP Server · Axiom MCP Server vs Sentry MCP
Machine-readable
| Similar tool | Grade | Score | Shared capabilities | x402 |
|---|---|---|---|---|
| New Relic MCP Server New Relic, Inc. | C | 61 | observability.metrics observability.logs observability.errors observability.traces observability.incidents | no |
| Better Stack Better Stack, Inc. | C | 54.2 | observability.logs observability.incidents observability.metrics observability.traces observability.errors | no |
| Grafana MCP Server Grafana Labs | BB | 71 | observability.metrics observability.logs observability.traces observability.incidents | no |
| Datadog MCP Server Datadog | C | 56.8 | observability.metrics observability.logs observability.traces observability.incidents | no |
| Causely MCP server Causely, Inc. | E | 39.5 | observability.incidents observability.metrics observability.logs observability.errors | no |
| Honeycomb MCP Honeycomb | C | 58.5 | observability.traces observability.metrics observability.logs | no |
Machine-readable
- JSON
/api/v1/tools/axiom.json· historyhistory.json· badge/badges/axiom.svg· changes feed/feeds/tools/axiom.xml - Markdown
/tools/axiom.md· slim/tools/axiom.min.md(or sendAccept: text/markdown) - What the fix list covers
/fixes/axiom.md·/fixes/axiom.json· the whole listPOST /api/v1/fix-list - From a terminal
anchor tool axiom --md(the CLI) · over MCPget_tool {"slug": "axiom"}at/mcp, no key - Directory index
/api/v1/tools.json· site index/llms.txt - No HTTP
dig +short TXT axiom.grade.anchorterminal.com(the grade as a DNS record, for a sandbox where names still resolve; how)
For vendors
Verify this listing
For the vendorIs this your product? Link to this page from your own site or README, then tell us where. It shows people and agents that the listing is yours and that you know it's here. It never changes a grade, rank or review.
-
Add the badge or a link
On a light page On a dark page <a href="https://www.anchorterminal.com/tools/axiom"><img src="https://www.anchorterminal.com/badges/axiom.svg" alt="Axiom MCP Server on Anchor Terminal" height="20"></a>[](https://www.anchorterminal.com/tools/axiom)<a href="https://www.anchorterminal.com/tools/axiom">Axiom MCP Server on Anchor Terminal</a>It counts on a page on axiom.co or one of its subdomains.
-
Tell us where it is
We read it once now and again every week. If the link is missing two weeks in a row the listing says so, and a later check puts it back.
Agents send the same to POST /api/v1/verify as {"slug": "axiom", "url": "…"}, or call the verify_listing tool at /mcp. Ten checks an hour from one address. What we check. To announce the listing, get sharing assets for social media.


