原型 · 预览版:收录官方注册中心里的全部服务器,每 30 分钟同步一次。使用 Google 登录即可撰写评价。原型 · 每 30 分钟更新
PopNx MCP为使用 AI 的人准备的 MCP 服务器 · 用大白话讲清楚

Vike Data API

作者:vike-io版本 1.1.4i★ 0i在云端运行
注册名称io.vike/data

安装方法

What it does

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

  • Connects 在云端运行
  • Account or key Works without a key · add X-API-KEY if you have one (often raises limits)
  • Category 加密货币与区块链

安装

选择你使用的 AI 应用,然后复制设置。

通过 4/4 项检查 · 你的提问会经过开发者的服务器(data.vike.io) · ✓ 命令已检查 2026年11月13日

第一步:你用哪个 AI?

选择你用的应用,步骤会显示在下方。

可连接 Claude · 约 2 分钟

不需要密钥,不用安装程序 · 在 claude.ai 或桌面应用设置一次,即可在聊天中使用 · 免费账户可添加 1 个 · Team/Enterprise 方案由所有者(Owner)添加

  1. 打开 Claude 的 Connectors 页面

    CustomizeConnectors

    CustomizeConnectors1Add2https://…3Add4
  2. 点击“Add” → “Custom” → “Web”,填写这 2 项

    把这里的内容复制到 Claude 中同名的输入框,然后点击 Continue

    Name · 名称Vike Data API
    Remote MCP server URL · 地址https://data.vike.io/mcp

    在 Claude 检测到的登录设置页点击 Continue · Authentication 按作者说明选择(Sign in now、Sign in when needed 或 No sign in),然后点击 Add

  3. 在聊天中开启

    +ConnectorsVike Data API

  4. 试一试

    用 Vike Data API 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude 说正在使用 Vike Data API,或回答中出现 Vike Data API 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

能否连接 ChatGPT 取决于方案

完整 MCP:网页版 ChatGPT Business、Enterprise 或 Edu · Pro:以读取/获取权限连接,修改数据的工具可能用不了 · Plus:官方文档尚未确认,如果在插件页看到添加自定义 MCP 的选项可以试试 · 仅限网页

  1. 在网页版 ChatGPT 打开添加 MCP 的页面

    Plugins+Add custom MCP server

    ChatGPTPlugins1+2https://…3Create4
  2. 填写名称和地址

    输入名称,在 Connection 下粘贴地址,勾选风险提示,然后点击 Create as a plugin

    Name · 名称Vike Data API
    Connection · 地址https://data.vike.io/mcp
  3. 在聊天中选择 Vike Data API

    开启新聊天,输入前先从插件列表中选择 Vike Data API

  4. 试一试

    用 Vike Data API 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 ChatGPT 说正在使用 Vike Data API,或回答中出现 Vike Data API 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 OpenAI 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Claude Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 打开终端

    Mac:按 Command+空格,输入 Terminal · Windows:打开 PowerShell

  2. 粘贴这条命令并按 Enter

    claude mcp add --transport http --scope user data https://data.vike.io/mcp
  3. 在 Claude Code 中输入 /mcp

    应能看到 Vike Data API 在列表中并显示已连接

  4. 试一试

    用 Vike Data API 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Claude Code 说正在使用 Vike Data API,或回答中出现 Vike Data API 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Anthropic 帮助页面核实 · 你的界面可能因版本略有不同

可连接 Cursor · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 Cursor

    在 Cursor 中打开

    Cursor 会请你确认安装,点击 Install

  2. 在 Cursor 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Vike Data API 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 Cursor 说正在使用 Vike Data API,或回答中出现 Vike Data API 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 Cursor 帮助页面核实 · 你的界面可能因版本略有不同

可连接 VS Code · 约 2 分钟

不需要密钥,不用安装程序

  1. 点击这个按钮打开 VS Code

    在 VS Code 中打开

    VS Code 会请你确认安装,点击 Install

  2. 在 VS Code 中以 Agent 模式打开 AI 聊天

  3. 试一试

    用 Vike Data API 告诉我你能帮我做什么,然后做一件给我看

    ✓ 如果 VS Code 说正在使用 Vike Data API,或回答中出现 Vike Data API 的工具名称,就表示连接成功

菜单名称已于 2026年11月11日 对照 VS Code 帮助页面核实 · 你的界面可能因版本略有不同

其他支持 MCP 的应用(如 Windsurf、Zed、Gemini CLI)添加方式各不相同,请在应用列表中查看

查看所有支持 MCP 的应用 →

通过网页连接的应用使用的地址

地址https://data.vike.io/mcp

JSON 设置在下方“开发者专用”中

卡住了?问问正在用 Vike Data API 的人💬 讨论 →
开发者专用:终端命令和 JSON 设置

通过网页连接

Claude Code

claude mcp add --transport http --scope user data https://data.vike.io/mcp

Cursor (~/.cursor/mcp.json)

{
  "mcpServers": {
    "data": {
      "url": "https://data.vike.io/mcp"
    }
  }
}

VS Code (mcp.json)

{
  "servers": {
    "data": {
      "type": "http",
      "url": "https://data.vike.io/mcp"
    }
  }
}

需要你填写的值

  • X-API-KEY 机密 HTTP header
    Vike API key from https://vike.io/account?tab=api-keys. Optional: OAuth 2.1 is also supported.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同,请以 README 为准。

一览

每周下载量i
不在 npm/PyPI 上
已验证域名
✓ vike.io
连接方式
在云端运行
传输方式
streamable-http
最新版本i
1.1.4
发布到注册中心i
2026年11月13日
代码最后更新i
2026年11月13日
作者
vike-io
网站
vike.io
注册状态
活跃

哪些应用可以使用它

依据这个服务器的连接方式和各应用自己的文档,检查于 2026年11月10日。

通过互联网连接,适用于

ClaudeChatGPTGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatOpen WebUIRaycast

全部应用及其优缺点 →

它能做什么

工具名称和描述与服务器在 2026年11月12日 报告的完全一致。这些内容由作者撰写,不是我们写的;我们以纯文本形式显示。

  • token_search

    Search for tokens by name or symbol. Returns matching symbols, names, addresses (0x-prefixed, lower case; pass them straight to token_holders and token_transfers), and logos.

  • wallet_summary

    Get a wallet's aggregate metrics: volume, inflow, outflow, net flow, tx count, tokens traded across time windows (24h/7d/30d/90d/all). Without `chain` it answers for the more recently active of ethereum and bsc, and for base or hyperevm only when the wallet has no priced ethereum

  • wallet_discover

    Find top wallets ranked by volume, inflow, outflow, net flow, tx count, or realized PnL. On base and hyperevm window=all always works; 24h/7d/30d/90d only while those windows were refreshed in the last 2 days, otherwise a 400.

  • token_transfers

    Get who bought and sold a specific token in a given period, ranked by net USD. tab=bought lists the top NET buyers (bought more than sold), tab=sold the top NET sellers, largest first, with quantities and USD values. Wallets that only pass the token through (routers, pools: bough

  • hl_ohlcv

    Historical OHLCV candles for a Hyperliquid market, aggregated from HL's own executed fills, by `view`. `candles` (default): one symbol's bars. Pass `symbol` as the HL asset (BTC, ETH, HYPE); `market` picks perps or HL spot and `dex` picks a builder-deployed HIP-3 perp DEX (defaul

  • polymarket_ohlcv

    Historical OHLCV candles for ONE Polymarket outcome token, from the recorded L2 tape. `token_id` is the ERC-1155 outcome token id — a market's condition_id will NOT work here; read the token ids off `clob_token_ids` from polymarket_market_detail. Prices are probabilities in [0, 1

  • perp_funding

    Perpetual-futures funding rates. Pass `symbol` (e.g. 'BTC') to get current per-venue rates for one asset. Omit `symbol` to get top cross-venue funding-arbitrage opportunities (pre-ranked, normalised to daily %, spreads >= 0.3%). Each arb row includes long_exchange+long_daily_pct,

  • perp_spreads

    Get top cross-venue spread-arbitrage opportunities for perpetual futures. Returns symbols where the price gap between the cheapest and most-expensive exchange is >= 0.5%. Each row includes buy_exchange+buy_price, sell_exchange+sell_price, and spread_pct. Pre-ranked — just cite th

  • alerts_list

    List the current user's alert rules. Returns active alerts by default; pass include_inactive=true to include paused/deleted ones. Also use this to look up an alert_id before editing or deleting. Each row has `alert_type`, `policy` (per_event, cooldown or hysteresis: how often it

  • alerts_create

    Create an alert rule for the current user: an on-chain transfer alert (the default), a Hyperliquid or a Polymarket alert, chosen by `alert_type`. TRANSFER ('transfer'): fires when a transfer on ONE chain (eth, bsc, base or hyperevm) matches: token_symbol if given, min_value_usd i

  • alerts_edit

    Partial update of one of the user's alerts. Only the fields you pass are modified; pass alert_id to identify which one (get it from alerts_list). Use is_active=false to pause an alert without deleting it. `address` replaces the alert's wallet condition (one per alert; same rules

  • alerts_delete

    Delete one of the user's alerts by id. Soft-delete (pauses it, keeps history) by default; pass hard=true to remove permanently. Returns {ok: true} on success.

  • alerts_list_channels

    List the user's enabled email + webhook notification channels. Use before creating an alert to confirm which channels are available (a Hyperliquid or Polymarket alert mails the account address, needs a webhook, or is read with alerts_events). Returns a list of {id, channel_type,

  • alerts_events

    Read the events the current user's alert rules produced, oldest first (the feed behind GET /v1/alerts/events). Page forward by passing the returned `next_cursor` back as `cursor`; an empty page returns the same cursor, so a poller keeps it and asks again. Each event has id, rule_

  • alerts_resend_delivery

    Send one of the user's own alert deliveries again (the same as POST /v1/alerts/deliveries/{id}/resend): the webhook or e-mail of an event that failed, expired or was lost on the receiving side. Take the delivery `id` from the `delivery` list of an event in alerts_events. Works wh

  • hl_perp_top_traders

    Rank top Hyperliquid perp wallets by PnL / ROI / win rate / volume / trade count within a time window. Use for questions like 'top HL traders with win rate > 75%' or 'best HL perp wallets last 7d'. Data comes from the same pipeline that backs vike.io/hyperliquid/wallets. Use win_

  • hl_position_match

    Reverse-lookup a Hyperliquid open position from share-card details (symbol + side + leverage + entry price). Given the info shown on a HL trader's share card, return wallet(s) with matching open positions, ranked by entry-price proximity. Useful for 'whose share card is this?' or

  • hl_cohort_metrics

    Hourly long/short positioning of ONE Hyperliquid perp split by cohort: every bucket of one ladder, every hour, in one call (the matrix behind 'are whales / smart money long or short BTC'). `axis` picks the ladder: `size` (account value), `pnl` (percentile of cumulative realized P

  • hl_segments

    The Hyperliquid cohort vocabulary and its latest-snapshot positioning, by `view`. `cohorts`: the label sets per ladder, the exact spellings every `cohort` parameter accepts. `segments`: the catalogue with bounds, ranks and what each ladder measures (`size` is account value in USD

  • hl_wallet

    One Hyperliquid wallet, by `view`. `summary`: live equity, open positions, both cohort labels, the risk metrics of the window (`win_rate` is a FRACTION from 0 to 1; `max_drawdown_pct` and `pnl_pct` are percents, `pnl_pct` is null under $1 of equity), cumulative realized PnL since

  • hl_wallet_activity

    A Hyperliquid wallet's event history, by `view`. `fills`: raw fills, newest first (`size_usd`, `closed_pnl` in USD; `fee` is in its own `fee_token`). `funding`: funding payments, `payment_usd` signed from the wallet's side (negative = the wallet PAID). `ledger`: deposits, withdra

  • hl_leaderboard

    Rank Hyperliquid wallets with the full risk set, by `view`. `ranking`: precomputed per-window metrics sorted on any of 20 keys (PnL, ROI, win rate, Calmar, profit factor, drawdown, streaks, ...), filtered by cohort and by minimum trades / win rate / volume, cursor-paged. A window

  • hl_liquidations

    Hyperliquid liquidations, by `view`. `fills`: liquidation events, newest first, filtered by symbol, wallet, side and time. Since 2026-08-03 rows are EXACT, the liquidated wallet's own fill from the node (`liq_ts` the fill's millisecond, sizes what it closed, `mark_price` the venu

  • hl_market

    Hyperliquid market positioning, by `view`. `open_interest`: open interest per symbol at the latest snapshot beside the venue's own figure, so the two can be reconciled. `symbol_metrics`: the hourly open-interest, position-count and `bias` series (a fraction from -1 to +1) of ONE

  • hl_builders

    Hyperliquid builder codes (front-ends and bots that attach their address to an order and take a slice of the taker fee), by `view`. `leaderboard`: builders ranked by fee revenue, routed volume, unique users or fills over a window. `stats`: venue-wide builder economics. `profile`:

  • hl_vaults

    Hyperliquid vaults across the platform, by `view`. `list`: one row per vault family (HLP and its sub-vaults are one row) with current TVL, APR (our 30-day share-price return, annualised) and the window's PnL, return, net flow, volume and fills, plus `leverage` (gross notional / e

  • hl_vault

    One Hyperliquid vault by address, by `view`. `profile`: TVL, APR, leverage, leader and top-5 shares, active depositors and all five windows (7d, 30d, 90d, 365d, all). `depositors`: every current depositor (not only the largest 100) with equity, PnL on the current position, all-ti

  • hl_orders

    Hyperliquid standing orders, by `view`. `open`: every order resting at one instant (`at`, default the newest snapshot) for a `symbol` and/or a `wallet`, in key order, with `snapshotTs` and `source`: `l4_5m` = the node's 5-minute order snapshot (from 2026-10-23 21:45 UTC), `state_

  • hl_twaps

    Hyperliquid TWAP orders, one row per status line, newest first. A line is a status CHANGE (`activated`, `waitingForTrigger`, then `finished`, `terminated` or `stopped`), not a slice fill: `executed_size` and `executed_notional_usd` are the cumulative totals when the line was writ

  • hl_ledger

    Hyperliquid deposits, withdrawals, transfers and vault events ACROSS wallets, newest first, with `wallet` and `amount_usd` (USD) on every row; `min_usd` keeps the large ones (most events are small transfers). A transfer between two wallets is one row per affected wallet with the

  • hl_leverage_changes

    Hyperliquid positions whose leverage or margin mode differs between two consecutive complete position snapshots, newest first: one row per wallet and symbol with the previous and the new leverage, margin mode, side, size and entry price. `ts` is when the later snapshot was writte

  • hl_wallet_trades

    One Hyperliquid wallet's CLOSED round-trip trades, newest close first, keyset-paged: per trade the symbol, direction, `open_ts` / `close_ts`, entry and exit price, the largest size held (`max_size_usd`), traded `volume_usd`, `realized_pnl` and `total_fee` in USD and the fill coun

  • hl_stats

    Hyperliquid venue-wide hourly series, newest hour first, by `view`. `ecosystem`: perp equity, open interest and position counts per hour. `volume`: traded perp notional per hour, of the whole venue (builder-DEX perps included; spot and outcome markets left out) or of one `symbol`

  • hl_hype_holders

    The HYPE holder leaderboard: each wallet's spot HYPE balance plus staked HYPE, largest first, valued at one current HYPE price, with its `pnl_cohort` resolved at query time (`label_basis` is `current`; balances are last-known, so a stale balance can sit beside a fresh label) and

  • polymarket_markets

    Polymarket markets, by `view`. `trending` (default): top prediction-market events ranked by 24h volume. Returns market title, slug, category, current Yes/No mid quotes, 24h volume, and end_date. Filter by category (Crypto | Sports | Politics | Pop-Culture | Tech | all). Use for '

  • polymarket_market_detail

    Deep-dive on one Polymarket market by condition_id: question, category, outcomes with their clob_token_ids, 24h and total volume, liquidity, a price series per outcome, the top 30 holders per side, the last 100 trades (with wallets), tape stats and resolution status. There is no

  • polymarket_wallet

    Profile a Polymarket trader: realized P&L (24h / 7d / 30d / all-time), hit-rate on resolved markets, total volume, top categories traded, and recent positions. Use when the user gives a Polymarket wallet address. Also returns `correlated`: up to 8 other wallets that trade the sam

  • wallet_label_provenance

    Full multi-source label cascade for one ETH wallet. Returns labels from several third-party label providers and the heuristic classifier with per-source attribution and a consensus entity/type. Source provider_e covers addresses that are, control or funded Polymarket wallets (cat

  • token_holders

    Top holders of an ERC-20 token by cumulative net inflow USD. Returns wallet, net flow USD, volume USD, tx count, first/last seen dates, and known labels. Use when the user asks 'top holders of X' or 'who holds the most of token Y'. sort='flow' (default) ranks by cumulative net in

  • alerts_register_webhook

    Register an HTTPS webhook as an alert delivery channel for the current user. We POST signed JSON to the URL when alerts fire, and once right now: a signed `test` event whose result comes back as `test` ({ok, status} or {ok, error}); a failing test does not refuse the channel. Eve

  • alerts_rotate_webhook_secret

    Rotate the signing secret of one of the user's webhook channels (ids from alerts_list_channels). A new secret is generated and returned as `secret` (show it to the user now; it is shown again any time on Account -> Alerts -> channels, Show secret). When the channel had a secret,

  • alerts_test_webhook

    Send the signed `test` event to one of the user's webhook channels again (ids from alerts_list_channels), for example after the receiver installed a new secret from alerts_register_webhook or alerts_rotate_webhook_secret. Signed like a real delivery: the current secret and, insid

  • wallet_transactions

    Raw per-wallet transfer list (single transactions, not aggregates). Filter by direction (in/out/all), days back, min USD, and optionally a specific token and, for that token, an amount range in whole tokens. Returns time, tx_hash, from, to, token_address, symbol, amount (whole to

  • wallet_compare

    Compare two wallets: shared counterparties (both wallets transacted with these addresses) + shared tokens (both wallets touched these tokens) within a window. Use when the user asks 'are these two wallets related' / 'what do X and Y have in common'.

  • wallet_trace

    Trace a wallet's money through counterparties. direction=out follows where funds went, in where they came from, both (default) either way. At each hop, expand to the top N counterparties by USD volume in that direction. Returns nodes + edges of the resulting graph. Use when the u

  • wallet_batch_labels

    Bulk label + 30d summary lookup for many addresses in one call. Caps at 100 addresses. Returns one row per input address in input order, with: entity, wallet_type, risk_flag, 30d net flow, 30d volume, 30d tx count, read from `chain`'s own tables. The 30d fields are live and null

  • token_screener

    Discover tokens by activity within a window. Rank by volume, net inflow, holder count, or smart-money inflow. Filters: min volume USD, min holders, smart-money-only. Use when the user asks 'what tokens are trending today' / 'find tokens with smart money accumulating' / 'rising to

  • wallet_counterparties

    Top trading partners of an ETH/BSC/Base/HyperEVM wallet by combined transfer volume. Returns counterparty address, total volume, amount sent/received, tx count, first/last seen, and labels (when known). Use when the user asks 'who does this wallet trade with' / 'main counterparti

  • wallet_pnl_history

    Daily net-flow series for a wallet over the last N days (proxy for daily PnL). Returns per-day net inflow USD + cumulative + gross volume + tx count. NOTE: this is net inflow USD, not true realized PnL (which would require WAC accounting per token). Useful as a directional indica

  • wallet_token_balances

    Current token balances for a wallet on Ethereum, BSC, Base and HyperEVM, read from the chain at request time. Returns per-holding (chain, symbol, balance, USD value, USD price). On base and hyperevm, symbol, name, balance and USD exist only for tokens we map and price (about 170

  • wallet_ens

    Reverse ENS lookup: turn a 0x address into a human-readable name like 'vitalik.eth'. Returns null if the address has no ENS name set. Use whenever you have an address and want to display a friendlier identifier.

  • wallet_first_funder

    The earliest inbound transfers of a wallet, from our own transfer tables, as TWO separate answers: `first_native_in` (the first plain send of the chain's coin to the wallet, at least `min_native` WHOLE coins; `amount` in whole coins, `amount_wei` exact in wei) and `first_token_in

  • wallet_exchange_usage

    Which centralised exchanges a wallet sent to and received from over a window, computed from our transfers joined to the addresses the chain's label table marks as exchanges. Returns `exchanges` [{entity, sent_usd, recv_usd, sent_share, transfers, first_seen, last_seen, addresses,

  • polymarket_market_trades

    ONE Polymarket market's trades WITH the wallet behind each, newest first, paged: who traded, which side, how many shares and at what price, from 2026-01-01 to a few minutes ago, read from the on-chain trade tape. Takes the market's `condition_id` (0x plus 64 hex digits, from poly

  • polymarket_smart_money

    Detect smart-money signals on Polymarket. Two modes: 'flows' = markets with the largest net cohort inflow in the last N hours; 'mispricings' = markets where cohort bought meaningfully below current mid (potential edge). Cohort is wallets with $1k+ realized PnL over 5+ resolved ma

  • polymarket_tape

    Raw Polymarket L2 event tape for ONE time window (at most 24 hours) on one or more outcome tokens, oldest first, from the recorded order-book feed. `token_id` / `token_ids` are ERC-1155 OUTCOME token ids (long decimal strings: read them off `clob_token_ids` in polymarket_market_d

  • polymarket_orderbook

    Order-book snapshot for ONE Polymarket outcome token: the nearest full-book snapshot at or before `ts` (the latest when omitted), flattened to price levels. `token_id` is the ERC-1155 OUTCOME token id (decimal string from `clob_token_ids` in polymarket_market_detail or `outcomes[

  • polymarket_market_stats

    Tape summary for ONE Polymarket outcome token: recorded events (`total_events`), `trades`, `trade_volume` in outcome SHARES (not USD), `snapshots`, and the first / last recorded timestamps (`first_ms` / `last_ms`, epoch ms). `token_id` is the ERC-1155 OUTCOME token id (decimal st

  • polymarket_settlement

    On-chain resolution of ONE Polymarket market, keyed by its `condition_id` (the market's 0x... hex id from polymarket_markets or polymarket_market_detail; an outcome token id matches nothing here). Returns [] or one row {condition_id, slug, question, outcomes, winning_index, winni

  • polymarket_settlements_bulk

    On-chain resolutions of MANY Polymarket markets in one call, oldest resolution first, paged: the list form of polymarket_settlement (same row fields), for 'which markets resolved in this window', 'every settled BTC 5-minute market' or a backtest set. `from_ms` is inclusive and `t

基础检查i

我们检查的是任何人都能看到的信息;我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月13日

  • ✓ 通过

    作者与仓库一致

    注册名称已通过域名 vike.io 验证(注册中心会核实域名所有权)

  • ✓ 通过

    仍在维护

    代码最后更新于今天

  • – 不适用

    有许可证

    不适用:由 vike.io 的所有者自己运行的云端服务器,你不会运行仓库里的代码

  • ✓ 通过

    端点有响应

    在 179 毫秒内响应(HTTP 200)

  • – 不适用

    使用 OAuth 登录

    无需登录

  • ✓ 通过

    工具描述中没有隐藏指令

    已读取 60 个工具描述,未发现针对 AI 的隐藏指令

讨论

提问、分享技巧或报告无法使用。按“有帮助”数量排序。

还没有帖子,欢迎第一个提问或分享。

此处内容由用户撰写,不代表 PopNx 团队。

使用 Google 登录后发帖

用户评价

还没有评价

用 Google 登录后写评价

与“加密货币与区块链”中的其他服务器比较i

  • 星标数多于此分类中其他 1669 个服务器的 0%
  • 发布到注册中心的时间比此分类中其他 1669 个服务器的 99% 更新
  • 基础检查结果等于或优于此分类中其他 1669 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时,星标数才计入。

常见问题

Vike Data API 安全吗?

它在 4 项适用的基础检查中通过了 4 项。我们没有阅读代码。在添加密钥或令牌之前,请先看看这个服务器要求哪些权限,并使用只具备所需权限的密钥。

它需要哪些密钥或代码?

注册中心没有列出必需的密钥,不过有些服务器会在首次使用时要求你登录。

它在我的电脑上运行还是在云端?

它在作者的云端运行。通过互联网连接,无需安装,但你发送的内容会经过作者的服务器。

它还在维护吗?

GitHub 仓库最后更新于今天,最新版本(1.1.4)于今天进入注册中心。

哪些应用可以使用它?

支持 MCP 的应用,例如 Claude Desktop、Claude Code、Cursor 和 VS Code。它通过 URL 连接,因此也能用于接受远程 MCP 的应用,例如网页版 ChatGPT(Business 及以上为完整 MCP;Pro 为只读)。

有什么可以替代它?

同一分类中有:Solana MCP by Vybe, Oracle3 prediction-market arbitrage checks, Polymarket Paper Trader

同类别的其他选择

同一分类中其他作者的服务器,按星标数排序。

如何看卡片:↓ 每周下载量i★ GitHub 星标i三大支柱:评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Solana MCP by Vybe

Solana MCP developer toolkit: wallets, trades, markets, PnL, transfers, onchain, swaps & API tools.

作者:vybenetwork正在增长★ 2647 整个仓库的星标6个月前更新

在云端运行

Oracle3 prediction-market arbitrage checks

Kalshi and Polymarket data, venue fees, no-arbitrage checks and paper execution for AI agents.

作者:YichengYang-Ethan正在增长↓ 35/周★ 56943天前更新

在你的电脑上运行

Polymarket Paper Trader

Polymarket paper trading for AI agents: $10k paper money, real order books, official fees.

作者:agent-next正在增长↓ 226/周★ 50728天前更新

在你的电脑上运行

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

Vike 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-KEY header (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:

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

PathWhat it is
.cursor-plugin/marketplace.json, plugins/vike-data/Cursor plugin (mcp.json, a skill, the logo)
server.jsonThe official MCP Registry entry (io.vike/data)
llms-install.mdInstall 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.