About Vike Data API
Vike Data API is a hosted crypto-data service for AI agents, covering on-chain activity, Hyperliquid markets, HL Cohorts, and Polymarket. It provides a remote endpoint with OAuth 2.1 or API-key authentication.
Key features
- 01Inspect on-chain wallets and tokens
- 02Query Hyperliquid positions and markets
- 03View hourly HL Cohorts positioning
- 04Explore Polymarket markets and flows
Use cases
- 01Review wallet flows, balances, and PnL
- 02Analyze Hyperliquid perps and cohorts
- 03Explore Polymarket order books and trades
MCP support
The hosted MCP server exposes crypto data tools for on-chain wallets and tokens, Hyperliquid, HL Cohorts, and Polymarket. Clients connect over Streamable HTTP and authenticate with OAuth 2.1 or a Vike API key.
Configuration
Remote servers need no local install. Pick your client, then copy the config or install in one click.
https://data.vike.io/mcpclaude mcp add --transport http io-vike-data https://data.vike.io/mcp{"mcpServers":{"io-vike-data":{"type":"http","url":"https://data.vike.io/mcp"}}}Open in Cursor{"servers":{"io-vike-data":{"type":"http","url":"https://data.vike.io/mcp"}}}Open in VS Code{"mcpServers":{"io-vike-data":{"type":"http","url":"https://data.vike.io/mcp"}}}{"mcpServers":{"io-vike-data":{"serverUrl":"https://data.vike.io/mcp"}}}Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.
https://data.vike.io/mcpAuth requiredTools
Details
From the project READMEVike Data API — remote MCP server
Crypto data for AI agents: on-chain wallets and tokens, Hyperliquid, HL Cohorts and Polymarket.
- Endpoint:
https://data.vike.io/mcp(Streamable HTTP) - Auth: OAuth 2.1 sign-in, or a Vike API key in the
X-API-KEYheader (create a key) - Docs: https://vike.io/docs/ai/data/
- MCP Registry:
io.vike/data
The server is hosted by Vike. This repository holds only the connection manifests: a Cursor
plugin, the registry server.json, and install notes for agents. There is nothing to build or run.
What the tools cover
- On-chain wallets and tokens on Ethereum, BNB Chain, Base and HyperEVM: wallet flows and balances, PnL history, counterparties, first funder, exchange usage, entity labels and risk flags, token holders, transfers and a token screener.
- Hyperliquid perps: wallet positions and fills, liquidations, leaderboards, builders, market stats and candles.
- HL Cohorts: hourly long/short positioning of each Hyperliquid perp split by wallet cohort.
- Polymarket: markets, order books, trade tape, settlements, wallet profiles, leaderboard and smart-money flows.
Connect
Claude (claude.ai, Claude Desktop): Settings → Connectors → Add custom connector → URL
https://data.vike.io/mcp, then sign in.
Claude Code:
claude mcp add --transport http vike https://data.vike.io/mcp --header "X-API-KEY: $VIKE_API_KEY"
Cursor: install the vike-data plugin from this repository, or add to ~/.cursor/mcp.json:
{
"mcpServers": {
"vike-data": {
"url": "https://data.vike.io/mcp",
"headers": { "X-API-KEY": "YOUR_KEY" }
}
}
}
Without headers, Cursor signs in with OAuth.
VS Code (GitHub Copilot): .vscode/mcp.json:
{
"servers": {
"vike-data": {
"type": "http",
"url": "https://data.vike.io/mcp",
"headers": { "X-API-KEY": "YOUR_KEY" }
}
}
}
Cline: see llms-install.md.
ChatGPT: add a custom connector with the URL https://data.vike.io/mcp and sign in.
Keep keys out of files you commit: use your client's secret store or an environment variable.
Layout
| Path | What it is |
|---|---|
.cursor-plugin/marketplace.json, plugins/vike-data/ | Cursor plugin (mcp.json, a skill, the logo) |
server.json | The official MCP Registry entry (io.vike/data) |
llms-install.md | Install steps an agent (Cline) can follow |
License
MIT for the files in this repository. Use of the API is governed by https://vike.io/terms.
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.