Vike Data API
io.vikePublished by vike.ioOfficial publisherv1.1.3Updated Oct 30, 2026
Crypto data for AI agents: on-chain wallets and tokens, Hyperliquid, HL Cohorts and Polymarket.
Overview
Hosted Vike MCP server giving assistants crypto data on on-chain wallets and tokens, Hyperliquid perps, HL Cohorts and Polymarket.
- What you can do
- Query on-chain wallets and tokens on Ethereum, BNB Chain, Base and HyperEVM: flows, balances, PnL, counterparties, holders, transfers and a token screener
- Inspect Hyperliquid perps: positions, fills, closed trades, orders, TWAPs, deposits and withdrawals, liquidations, vaults, market stats, funding and open interest
- Read HL Cohorts hourly long/short positioning by wallet cohort
- Explore Polymarket markets, order books, trade tape, settlements, wallet profiles, leaderboards and smart-money flows
- Search across tokens, wallets, traders, vaults, builders and markets
- List live stream channels and filters, validate a filter, read past stream events and see your own connections
- When to use it
- Useful when an assistant needs crypto market and on-chain research: wallet and token due diligence, Hyperliquid perp and cohort analysis, or Polymarket market and flow lookups, without building your own data pipeline.
- Requirements
- Remote Streamable HTTP endpoint at data.vike.io/mcp; no local install. Authentication is required: OAuth 2.1 sign-in, or a Vike API key sent in the X-API-KEY header, created from a Vike account. Network access to the endpoint and to the stream host for live streams.
Installation
In SourceWeft
- Open Vike Data API in the dashboard and add it to a workspace.
- Connect the required credentials. They are stored privately and never shown on public pages.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.vike%2Fdata/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.
{
"mcpServers": {
"vike-data-api": {
"type": "http",
"url": "https://data.vike.io/mcp"
}
}
}README
Vike Data API — remote MCP server
[Vike]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, fills and closed trades, orders and order clusters, TWAPs, deposits and withdrawals, leverage changes, liquidations, leaderboards, builders, vaults, market stats, hourly funding and open interest, HYPE holders, candles and the Parquet archive.
- 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.
- Search across all of the above: tokens, wallets, traders, vaults, builders and markets.
- Live streams (
wss://stream.vike.io): list the channels and their filters, check a filter before subscribing, read past stream events, and see your own connections.
Connect
Claude (claude.ai, Claude Desktop): Settings → Connectors → Add custom connector → URL
https://data.vike.io/mcp, then sign in.
Claude Code:
Cursor: install the vike-data plugin from this repository, or add to ~/.cursor/mcp.json:
Without headers, Cursor signs in with OAuth.
VS Code (GitHub Copilot): .vscode/mcp.json:
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
License
MIT for the files in this repository. Use of the API is governed by https://vike.io/terms.
Source: README.md at commit 2b4811b
Tools
0Version history
3- v1.1.3LatestOct 30, 2026
- v1.1.1Oct 26, 2026
- v1.0.0Oct 24, 2026
Score
85% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
- Auth declaredRequired10 pts
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
