Developer · Remote MCP server
axiom.co
List datasets, schemas, run APL queries, and use prompts for exploration, anomalies, and monitoring.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
co.axiom/mcp- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- SSE (HTTP + Server-Sent Events), Streamable HTTP
- Published
- 2025-09-30
- Updated
- 2025-09-30
- Publisher
- co.axiom
- Namespace
- Namespace verified by the MCP Registry via the domain axiom.co · how
- Repository
- github.com/axiomhq/mcp (folder apps/mcp)
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| SSE (HTTP + Server-Sent Events) | https://mcp.axiom.co/sse | None |
| Streamable HTTP | https://mcp.axiom.co/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mcp.axiom.co/sse(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mcp.axiom.co/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect axiom.co
axiom.co is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.axiom.co/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://mcp.axiom.co/sse. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More developer servers
| Server | Runs |
|---|---|
| aXAgent-native collaboration network: orchestrate a team of long-running agents from any MCP client. | Remote · HTTPLive check: ✗ no handshake |
| AxintProof and repair for Apple coding agents: validate Swift, run Xcode evidence, and repair failures. | Remote & Local · HTTP, stdioLive check: ✓ handshake |
| AXIOMTransactional write gate for coding agents: plan, canonical manifest, checks, two-phase apply. | Local · stdio |
| Axiom - Advanced MathExact symbolic math for LLMs: integrals, equations, matrices, and claim verification via Giac/Xcas. | Local · stdio |
| AxisCoding agents from Claude Code, Cursor and Codex claim jobs and lock files on one shared board. | Remote & Local · HTTP, stdioLive check: sign-in required |
| Axis Iliad - Codebase Intelligence For Agentic CommerceCodebase intelligence for agents: 152 structured artifacts across 21 programs, one call. | Remote · HTTPLive check: ✗ no handshake |
| Axon NeuroAutomataProtein analysis: ESM-2/ESMC embeddings, mutation scoring, landscape scans, ESMFold structure. | Remote · HTTPLive check: sign-in required |
| Azure Boards MCPAzure DevOps Boards work items over MCP (stdio). Requires Bun, org, project, and PAT. | Local · stdio |