MCP server

Point an MCP-capable client at one URL and it can pull 0xArchive market data through typed tools instead of guessing endpoints. The server is hosted at https://mcp.0xarchive.io/mcp. There is nothing to install and nothing to run locally.

MCP is a protocol/tool surface, not a coding agent. Claude Code, Codex, Cursor, Windsurf, and similar clients connect to it when their setup supports MCP.

Connect

The server speaks streamable HTTP. Authenticate with your 0xArchive API key as a bearer token. Store the key as OXARCHIVE_API_KEY and pass it in the Authorization header.

claude mcp add --transport http 0xarchive \
  https://mcp.0xarchive.io/mcp \
  --header "Authorization: Bearer $OXARCHIVE_API_KEY"

{
  "mcpServers": {
    "0xarchive": {
      "type": "http",
      "url": "https://mcp.0xarchive.io/mcp",
      "headers": {
        "Authorization": "Bearer ${OXARCHIVE_API_KEY}"
      }
    }
  }
}

curl -X POST https://mcp.0xarchive.io/mcp \
  -H "Authorization: Bearer $OXARCHIVE_API_KEY" \
  -H "Content-Type: application/json" \
  -H "Accept: application/json, text/event-stream" \
  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"app","version":"1.0.0"}}}'

A successful initialize returns serverInfo of { "name": "0xarchive" } and a tools capability. A 401 means the bearer token is missing or wrong; fix the key before asking for data.

Hermes Agent

Hermes Agent can connect to the hosted server without editing YAML. Run the exact command below in the Hermes CLI:

hermes mcp add 0xarchive --url https://mcp.0xarchive.io/mcp --auth header

When Hermes asks Enable all N tools? [Y/n/select], enter select, review the checklist, and enable only the tools you intend to use. All discovered tools begin selected, so deselect any tool you do not want exposed to the agent. Enter the API key only in the CLI’s masked prompt. Then verify the connection:

hermes mcp test 0xarchive

Confirm that representative read tools are discovered before asking a safe market-data question. If the test returns 401 for an invalid or rotated key, update MCP_0XARCHIVE_API_KEY in the file returned by hermes config env-path, then rerun the test without printing the key. Never put credentials in chat, logs, or command arguments. A host should never ask the user to paste a key into chat or a command argument.

OAuth

Clients that manage their own consent can use OAuth instead of a static key. Discovery starts at https://mcp.0xarchive.io/.well-known/oauth-protected-resource, which points at the authorization server https://auth.0xarchive.io. OAuth discovery currently advertises only mcp:market.read:

Scope	Grants
`mcp:market.read`	Read market data: summaries, order books, trades, candles, funding, open interest, liquidations, instruments, and data quality

A bearer API key is the fastest path. OAuth is there when the client handles token refresh and consent itself.

What the tools do

Read tools cover the same route families as the REST reference: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, Lighter, and data quality. They are read-only and safe to call without approval.

Prompt shape	Tool family
”Get a BTC market summary on Hyperliquid.”	`get_summary`
”Fetch ETH one-hour candles for the last 24 hours.”	`get_candles`
”Compare current BTC funding on Hyperliquid and Lighter.”	`get_funding_current` and `get_lighter_funding_current`
”Summarize `km:US500` on HIP-3.”	HIP-3 summary tools
”List active HIP-4 outcome markets.”	HIP-4 outcome tools
”Show recent data incidents or coverage gaps.”	Data quality and incident tools

The current hosted server does not advertise account creation, key management, billing, or subscription tools. Use the 0xArchive website and documented account surfaces for those workflows.

When to use the MCP server

Use the MCP server when	Use another interface when
An MCP-capable client should call typed tools directly	You only need one shell command; use CLI
You want the same connection shared across agent sessions	You are generating an app client; use OpenAPI or SDKs
You want route selection, execution, and inspection in one client	The host only supports `SKILL.md`; use Skill
The host supports remote HTTP MCP	You need raw HTTP behavior; use REST API

For live streaming, use WebSocket. The MCP server covers REST-shaped and historical workflows.

Security

Keep API keys out of prompts and checked-in config. Pass the bearer token through the host’s secret store or an environment variable, never in shared chat text or a browser URL. Review the discovered read-only tool list before enabling it in an agent host.

Moving off the self-hosted package

Earlier versions ran a local stdio package, @0xarchive/mcp-server, launched with npx. That package is retired as of August 6, 2026 and is no longer developed. Its repository is archived and read-only, and the package stays published, so existing self-hosted setups keep working. It will not receive new tools or data sources. The hosted endpoint replaces it. There is nothing to install, and auth is a bearer token rather than a local environment variable. If you still run the local stdio server, point your client at https://mcp.0xarchive.io/mcp and drop the npx command. Run tool discovery after connecting and use the tool names returned by the hosted server.

Next step

Use Choose an interface to weigh the MCP server against CLI, Skill, SDKs, and OpenAPI. Use Coding agents for prompt and recovery rules once the connection is live.

Get started

Market data

Get connected

Plans & limits

Connect

Hermes Agent

OAuth

What the tools do

When to use the MCP server

Security

Moving off the self-hosted package

Next step

​Connect

​Hermes Agent

​OAuth

​What the tools do

​When to use the MCP server

​Security

​Moving off the self-hosted package

​Next step

Connect

Hermes Agent

OAuth

What the tools do

When to use the MCP server

Security

Moving off the self-hosted package

Next step