MCP Overview¶

Vike exposes a Model Context Protocol server that lets AI assistants query blockchain data, perpetual futures analytics, and market data directly.

Protocol¶

Property	Value
Transport	HTTP (POST)
Endpoint	`https://vike.io/mcp`
Protocol	JSON-RPC 2.0
MCP version	2025-03-26

Authentication¶

Vike supports two authentication methods:

1. X-API-KEY header — used by Claude Code, Cursor, Gemini CLI, GitHub Copilot, and raw HTTP clients:

X-API-KEY: vk_your_key_here

Keys are created at vike.io/account (tab: API Keys). Up to 5 active keys per account. Only active keys are accepted; the last-used timestamp is updated on each request.

2. OAuth 2.1 with Dynamic Client Registration (RFC 7591) — used by Claude Desktop. The client registers itself automatically; the user approves access in a browser. No API key is exchanged. Connected apps appear under Account → API Keys → Connected Apps and can be revoked there.

See Getting Started for client-specific setup.

Available tools¶

Tool	Credits	Description
`token_search`	0	Search tokens by name or symbol across chains
`wallet_summary`	2	Aggregate wallet metrics (volume, flows, tx count)
`wallet_discover`	2	Top wallets ranked by various metrics
`token_transfers`	2	Who bought/sold a token in a given period
`token_chart`	1	OHLCV candle data
`perp_funding`	1	Funding rates across CEX exchanges
`perp_spreads`	1	Cross-venue price comparison for perps
`options_flow`	1	Deribit options call/put flow and volume

See Tools for full parameter details and Examples for request/response walkthroughs.

Rate limiting¶

Each account is limited to 100 calls per hour, shared across all API keys and OAuth-connected apps. When exceeded, the server returns a JSON-RPC error:

{
  "jsonrpc": "2.0",
  "id": 1,
  "error": {
    "code": -32000,
    "message": "Hourly rate limit exceeded"
  }
}

Error codes¶

Code	Meaning
-32700	Parse error (invalid JSON)
-32601	Unknown method or tool
-32000	Authentication failure or rate limit