Connect MCP-capable clients to 0xArchive’s hosted MCP server at mcp.0xarchive.io with your API key as a bearer token. Nothing to install.
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.
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.
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.
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 and advertises these scopes:
Scope
Grants
mcp:market.read
Read market data: summaries, order books, trades, candles, funding, open interest, liquidations, instruments, and data quality
mcp:account.bootstrap
Bootstrap an account context for a new client
mcp:account.create
Create an account
mcp:keys.read
List API keys
mcp:keys.revoke
Revoke an API key
mcp:billing.subscribe
Start a subscription
A bearer API key is the fastest path. OAuth is there when the client handles token refresh and consent itself.
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 same server can also create an account, list or revoke keys, and start a subscription. Those tools change account state, so require explicit human approval before an agent calls one. Keep account, key, and billing tools behind a confirmation step in the host.
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. Account, key, and billing tools should stay behind explicit approval in the agent host.
Earlier versions ran a local stdio package, @0xarchive/mcp-server, launched with npx. 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. Tool names are unchanged, so your prompts keep working.
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.
