https://mcp.0xarchive.io/mcp. Add it as a remote HTTP MCP server, then use Claude Code’s built-in OAuth flow. Nothing runs locally.
Claude Code recipe
1
Add the hosted MCP server
Register the hosted endpoint with Claude Code’s HTTP transport:This command uses Claude Code’s remote HTTP MCP configuration. Do not configure a static API key, an API-key bearer header, or any static Authorization header.
2
Complete OAuth consent
Start Claude Code’s built-in OAuth flow and approve the
mcp:market.read scope. The authorization server is https://auth.0xarchive.io; Claude Code manages the resulting OAuth access token.3
Ask for one bounded call
Start with one venue family, one symbol, one data family, and one small window. Ask Claude to name the exact advertised tool and input schema before it calls; do not infer a tool name from a REST route.
What Claude should know
Task checklist
After the server is connected, give Claude a narrow tool-calling checklist.
If Claude cannot call a named 0xArchive tool, repeat the client’s OAuth consent flow and verify that
mcp:market.read was granted before asking it to analyze data. If it can call tools but cannot name the venue family, keep the task in clarification mode.
Use another surface when
Use CLI if the job is a shell command or CI task. Use Skill if the Claude environment uses localSKILL.md workflows instead of MCP tools. Use OpenAPI and SDKs for generated application code. Use REST API when you need raw HTTP behavior; those API-key surfaces are separate from hosted MCP OAuth.
Security
Claude Code manages the hosted MCP OAuth access token. Do not paste OAuth tokens, API keys, or other credentials into prompts, checked-in MCP config, logs, or command arguments. The hosted MCP endpoint requires no 0xArchive API key and does not advertise account, key, or billing tools. Treat any state-changing tool exposed by another server as a separate, approval-gated surface.Plans and limits
Free gets the full catalog; paid plans raise your limits
Every tier, including Free, gets the full published catalog; whether a result is served still depends on the route, venue family, symbol, and schema. Tiers govern credits, request windows, rate limits, concurrency, WebSocket scale, standard replay speed, and Free’s rolling 30-day history window. They do not change route access; Build and above keep the full retained archive.