mcpbeat Sign in

Vike MCP Server

answering

Vike is answering right now. Last checked 4 min ago.

Crypto data for AI agents: on-chain wallets and tokens, Hyperliquid, HL Cohorts and Polymarket.

Uptime history 25 hours of history
25 hours agonow
100.0%
Uptime 24h
90 of 90 checks
—
Tools
hidden behind auth
416 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Vike every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 4 min ago.

run in your terminal
claude mcp add data --transport http https://vike.io/mcp
Settings → Connectors → Add custom connector, then paste this address
https://vike.io/mcp
~/.codex/config.toml
[mcp_servers.data]
url = "https://vike.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "data": {
      "url": "https://vike.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "data": {
      "type": "http",
      "url": "https://vike.io/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://vike.io/mcp streamable-http sign-in 186 ms 4 min ago

Alternatives to Vike

same job, measured the same way
Crypto Market Data
by zaffy18

Live crypto market data and Hyperliquid wallet reports for AI agents, paid per call with x402.

15 tools answering
Coinversaa
by coinversaa

Crypto intelligence for AI agents. Hyperliquid trader analytics, cohorts, and live market data.

77 installs/wk local only
santyvv-data — market & on-chain data
by santyvv

Market and on-chain crypto data for AI agents. Pay per call in USDC on Base (x402).

9 installs/wk 8 tools answering
Liquid Agent
by liquidagent-api

Money tools for AI agents over x402: USDC bridge to 16 chains, Polymarket data, stocks, USDC gas.

32 tools answering
Fillgate
by mineloop99

Fee-carrying trading tools for AI agents: Jupiter Ultra, Polymarket CLOB v2, Hyperliquid perps.

25 installs/wk local only
GDEX Trading
by gemachdao

GDEX (gdex.pro) trading for AI agents: spot, perps and HyperLiquid on Solana, EVM and more chains

129 installs/wk local only
V
Ventis
by ops119

Crypto data for AI agents: prices, Solana wallets, token risk, swap quotes. Pay per call via x402.

2 tools answering
C
chainpulse — real-time crypto + prediction market data for AI agents
by fastdb-md

Crypto prices, gas, DeFi TVL, and live Polymarket odds. x402 pay-per-call, $0.001, no API key.

7 tools answering

Vike — questions

Answers built from our own checks of this server.

Why is there no tool list for Vike?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Vike working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 90 checks got a reply (100.0%), average response time 416 ms. The bar chart above shows every period we have measured.
How do I connect Vike?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Vike?
No API key is involved. Vike answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Vike?
It answers our handshake in 416 ms on average, which is faster than 33% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.