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 and uses OAuth onboarding. Use the client’s built-in OAuth flow to obtain an OAuth bearer access token; do not add a genericAuthorization header or an 0xArchive API key. The hosted MCP endpoint requires no 0xArchive API key.
The protected-resource metadata for https://mcp.0xarchive.io/mcp names the authorization server https://auth.0xarchive.io and lists the scopes the server offers. It advertises exactly the scopes its enabled tools need and nothing beyond them, so that metadata, and the consent screen your client shows you, are the live answer to what this server can do. If a scope is not listed there, the tools behind it are not enabled on the server you are connected to.
Read the live scope list
Two further scopes,
mcp:webhooks.read and mcp:webhooks.write, are offered alongside it when the webhook configuration tools are enabled on the server, and are absent from the metadata when they are not. mcp:webhooks.write changes account state, so a client is right to present it as a change rather than a read.
Hermes Agent
Hermes Agent is an MCP-capable client. Use Hermes’s built-in OAuth flow for the hosted URL. Exact setup syntax depends on the installed Hermes release, so follow the current client prompts. The OAuth bearer access token stays in Hermes’s credential handling, and no 0xArchive API key is required. When the client presents tool selection, enterselect, 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. Confirm that representative read-only tools are discovered before asking a safe market-data question. If authorization fails, repeat the client’s OAuth consent flow and verify that mcp:market.read was granted; do not switch to an API-key header.
What the tools do
Read-only market-data tools are organized around the documented venue families: Hyperliquid core, Hyperliquid Spot, HIP-3, HIP-4, Lighter, and data quality. They do not submit orders or change account state, but the host should still expose only the exact tools and input schemas it discovered. Lighter tools cover both Lighter deployments:get_lighter_* tools read Lighter mainnet and get_rh_lighter_* tools read Lighter on Robinhood Chain. The account positions tools (get_account_positions, get_account_positions_history, get_account_position_changes, get_market_positions, get_market_positions_summary, and get_lighter_accounts) read the Account positions routes and take a venue of hyperliquid, hip3, lighter, or rh-lighter. Plan tiers govern capacity and request windows, not access to a higher-tier route catalog; availability remains specific to the route, venue family, symbol, and schema.
For current funding requests, call the Hyperliquid and Lighter tools separately. Preserve the source units and timestamp from each response.
Whatever the metadata lists, the server does not advertise account creation, API key management, or billing and plan changes. Use the 0xArchive website and documented account surfaces for those workflows.
When to use the MCP server
For live streaming, use WebSocket. The MCP server covers REST-shaped and historical workflows.