Axiom MCP Server
co.axiom/mcp
answering
Axiom is answering right now. Last checked 1 min ago.
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
The linked repository no longer exists on GitHub — it was deleted or made private.
Uptime history
39 hours of history
39 hours agonow
100.0%
Uptime 24h
184 of 184 checks
—
Tools
hidden behind auth
48 ms
Response time
average over 24h
API key or OAuth
Access
sse
Connect this server
Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.
run in your terminal
claude mcp add mcp --transport http https://mcp.axiom.co/sse~/Library/Application Support/Claude/claude_desktop_config.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.axiom.co/sse"
}
}
}~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mcp.axiom.co/sse".cursor/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.axiom.co/sse"
}
}
}.vscode/mcp.json
{
"mcpServers": {
"mcp": {
"url": "https://mcp.axiom.co/sse"
}
}
}This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.
Endpoints
| URL | Transport | State | Latency | Checked |
|---|---|---|---|---|
| https://mcp.axiom.co/sse | sse | needs key | 41 ms | 1 min ago |
| https://mcp.axiom.co/mcp | streamable-http | needs key | 45 ms | 1 min ago |
Axiom — questions
Answers built from our own checks of this server.
Why is there no tool list for Axiom?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Axiom working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 184 of 184 checks got a reply (100.0%), average response time 48 ms. The bar chart above shows every period we have measured.
Is Axiom still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect Axiom?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You will need your own key or an OAuth login: it refuses anonymous clients.
Does Axiom need an API key?
Yes. Every time we knock, Axiom answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is Axiom?
It answers our handshake in 48 ms on average, which is faster than 98% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.