HyperSignal MCP について
HyperSignal MCPは、AIエージェントや取引ワークフロー向けにHyperliquidの市場分析、ウォレットリスクレポート、アラート、署名付きシグナルを提供します。ローカルでの注文執行も選択できますが、リモートサーバーでは取引ツールを利用できません。
主な機能
- 01市場・オーダーブック・ローソク足データ
- 02大口保有者のポジションと清算分析
- 03資金調達率・HIP-3・ボールトのスクリーニング
- 04ポートフォリオリスクとトレーダーレポート
- 05定期アラートと検証可能なシグナル記録
- 06オプションのローカル取引ツール
活用シーン
- 01市場状況と資金調達率の確認
- 02ウォレットのエクスポージャーと清算リスクの評価
- 03大口保有者の変化や資金調達率の閾値を追跡
- 04ローカルでHyperliquid注文をプレビューまたは送信
MCP 対応
MCPサーバーはstdioまたはStreamable HTTPで分析ツール、リソース、プロンプトを公開します。プレミアムツールにはAPIキーまたはx402決済を使用し、取引ツールはローカルstdio専用です。
設定
リモートサーバーはインストール不要です。クライアントを選んで設定をコピーするか、ワンクリックで導入できます。
https://hypersmash.fly.dev/mcpclaude mcp add --transport http johnsmithxy1mmm-sys-hypersignal https://hypersmash.fly.dev/mcp{"mcpServers":{"johnsmithxy1mmm-sys-hypersignal":{"type":"http","url":"https://hypersmash.fly.dev/mcp"}}}Cursor で開く{"servers":{"johnsmithxy1mmm-sys-hypersignal":{"type":"http","url":"https://hypersmash.fly.dev/mcp"}}}VS Code で開く{"mcpServers":{"johnsmithxy1mmm-sys-hypersignal":{"type":"http","url":"https://hypersmash.fly.dev/mcp"}}}{"mcpServers":{"johnsmithxy1mmm-sys-hypersignal":{"serverUrl":"https://hypersmash.fly.dev/mcp"}}}コマンドはターミナルで実行し、JSON は各クライアントの MCP 設定に貼り付けて再起動します。認可が必要なサーバーは初回接続時にログインを求めます。
https://hypersmash.fly.dev/mcp認証が必要ツール
README(原文)English
プロジェクトの README よりこの README の日本語訳はまだありません。以下は英語の原文です。日本語の紹介はページ上部をご覧ください。
HyperSignal MCP
Monetized MCP server for Hyperliquid analytics & signals. Gives AI agents (Claude, Cursor, ChatGPT, autonomous trading agents) the Hyperliquid analytics that free open-source MCP servers don't have — whale-cohort signals, liquidation maps, funding screeners, HIP-3 analytics, and ready-made risk reports — plus an optional local trading tier that attaches a builder code to orders.
⚠️ Analytics, not investment advice. Trading tools place real orders and are irreversible.
Tiers & tools
Free (open-source parity — the hook)
| Tool | What it returns |
|---|---|
hl_get_markets | Perp markets: mark/oracle price, hourly + annualized funding, OI, 24h volume; filter/sort |
hl_get_orderbook | L2 book (top-N levels), spread, mid |
hl_get_candles | OHLCV candles by interval/range or lookback |
hl_get_funding_history | Funding history + avg/cumulative |
hl_get_account | Positions, equity, margin, liquidation prices for any address |
hl_get_open_orders | Open resting orders for any address |
Premium (the differentiator — metered)
| Tool | What it returns |
|---|---|
hl_whale_positions | Aggregated cohort positioning by coin: net long/short, wavg entry, 1h/24h change |
hl_whale_flow_alerts | Recent large cohort position shifts above a USD threshold |
hl_liquidation_map | Liquidation clusters (notional-at-risk by distance from mark), nearest cascades |
hl_funding_screener | Every perp screened by annualized funding + cross-venue spreads |
hl_hip3_analytics | HIP-3 (builder-deployed / RWA / equity) perp metrics + external basis |
hl_portfolio_risk | Liquidation distance, effective leverage, concentration, stress scenarios, PnL Sharpe |
hl_vault_screener | Vaults by APR, max drawdown, Sharpe/Sortino, age, TVL, leader share |
hl_trader_report | Wallet breakdown: winrate, avg R, PnL curve, scalp/swing style, top coins |
Agent-native (v0.3) — the differentiators
| Tool | Tier | What it does |
|---|---|---|
hl_create_alert / hl_list_alerts / hl_delete_alert | premium | Register/manage standing alerts (funding threshold, price move, whale net-flip). The server evaluates them on a schedule — it watches the market for your agent. |
hl_poll_alerts | premium | Retrieve fired alert events since your last poll (at-least-once), each with a signed signal payload. |
hl_signal_track_record | premium | Transparent, verifiable performance of emitted signals: hit-rate and avg/median direction-adjusted forward return per signal type. |
hl_request_free_key | free | Self-serve API key — one call, no signup, grants 100 premium calls/month. Send it as X-API-Key. This is the intended first call for any new agent: premium tools point at it by name when they need a key. |
hl_buy_pro | paid ($29, x402) | Buy 30 days of Pro over x402 (USDC on Base): a new key, or the key in X-API-Key renewed (a free key is upgraded in place). Remote server only. |
hl_signal_pubkey | free | Ed25519 public key to independently verify any signal's authenticity + timestamp. |
hl_admin_stats | free (own gate) | Operator only — requires adminSecret matching HYPERSIGNAL_ADMIN_SECRET. Per-key usage this billing period, top tools, active alerts, signal track record, x402 payment counts. |
hl_smart_money_score | premium | Rank a cohort by a smart-money screening score (risk-adjusted perf + winrate + reward/risk + size + activity) with behavioral labels (whale, sharp, scalper, market_maker_like, high_conviction, …). A descriptive screener over past results — see hl_score_calibration before treating it as a forecast. |
hl_score_calibration | free | Out-of-sample evidence for the smart-money score: Spearman rank correlation between score and the realized forward return each wallet went on to earn (forward PnL over account value when sampled), p-value, and mean forward return per score quartile. Free on purpose — a claim about predictive power should be checkable before you pay for it. The server scores its own cohort daily, so this fills in whether or not anyone is calling the paid tool. |
hl_coordination_scan | premium | Find wallets holding near-identical exposure (cosine similarity) — likely the same entity / copy-bot / coordinated group; returns clusters + strongest pairs. |
hl_polymarket_divergence | premium | Compare Polymarket price-threshold odds against the probability implied by Hyperliquid price + realized vol — a cross-market mispricing edge no other MCP offers. Also audits the market's own price ladder for logically impossible orderings (a further threshold priced above a nearer one), collapses duplicate contract listings, reports each estimate's volatility-sensitivity range, and flags extreme tails where a diffusion model is blind to jump risk. |
Every emitted signal is cryptographically signed and scored against forward price — a track record that can't be cherry-picked. Persistence (alerts, positioning snapshots, signals) is SQLite-backed and survives restarts.
Public proof, no key needed: the hosted server runs its own standing alerts (funding extremes on the top 10 perps by open interest, whale-cohort flips on BTC/ETH) and publishes their track record together with the score calibration and the signing key at /track-record (JSON). The same data is available to MCP clients as resources (hypersignal://about, ://track-record, ://calibration, ://signal-pubkey), plus three prompts: whale_briefing, wallet_risk_check, funding_carry_scan.
Trading (optional, local stdio only, builder code, maximum warnings)
| Tool | What it does |
|---|---|
hl_place_order | Limit/market order via your agent wallet, builder code attached |
hl_cancel_order | Cancel by coin + order id |
hl_close_position | Reduce-only market close |
hl_approve_builder_fee_guide | Read-only — generates the approveBuilderFee payload/instructions for your main wallet |
hl_twap_order | Slice a position into evenly-spaced child orders (TWAP) to minimize impact, builder code on each child |
hl_copy_wallet | Mirror a target wallet's positioning scaled to your equity (copy-trading), builder code attached |
hl_execution_status | Progress of running TWAP/execution plans |
hl_cancel_execution | Stop a running plan; slices not yet fired are dropped. A plan also stops by itself after 3 failed slices in a row |
Trading defaults to dry-run (previews the exact signed action without sending). Submitting
requires HL_ENABLE_TRADING=true + HL_AGENT_PRIVATE_KEY (env only) + confirm=true + dryRun=false.
Every non-reduce-only order (including each TWAP slice and copy-trade leg) is capped at HL_MAX_ORDER_NOTIONAL_USD
(default $10,000), which only the operator can raise.
HIP-3 coins (xyz:XYZ100) trade on their builder dex, which keeps its own collateral (enable the unified account
or transfer collateral to it) and may charge higher fees. Live HIP-3 orders also need HL_ENABLE_HIP3_TRADING=true:
turn it on after a testnet run. Copy-trading mirrors main-dex positions only.
Trading tools are never exposed on the remote HTTP server.
Try it on the hosted server
Nothing to install. Free tools work without a key. For the premium tools, call hl_request_free_key
once: it returns a key with 100 premium calls a month, no signup.
Claude Code:
claude mcp add --transport http hypersignal https://hypersmash.fly.dev/mcp --header "X-API-Key: <your key>"
Cursor (.cursor/mcp.json):
{ "mcpServers": { "hypersignal": { "url": "https://hypersmash.fly.dev/mcp", "headers": { "X-API-Key": "<your key>" } } } }
Without a key the free tools still work; add the key after hl_request_free_key has issued one.
Install
Requirements
Node 20 or 22 LTS (Node 24 has no prebuilt better-sqlite3 binaries and requires a C++ toolchain — use LTS).
npm install && npm run build.
Local (stdio) — free + trading, for Claude Desktop / Claude Code / Cursor
Claude Desktop (claude_desktop_config.json), from npm:
{
"mcpServers": {
"hypersignal": {
"command": "npx",
"args": ["-y", "hypersignal-mcp"],
"env": {
"HL_NETWORK": "mainnet",
"HL_BUILDER_ADDRESS": "0xYourBuilderAddress",
"HL_ENABLE_TRADING": "false"
}
}
}
}
From a clone instead: "command": "node", "args": ["/absolute/path/to/HyperliquidMCP/dist/server-stdio.js"].
Cursor (.cursor/mcp.json) uses the same command/args/env shape.
Inspect locally:
npm run build && npm run inspect # @modelcontextprotocol/inspector
Remote (Streamable HTTP) — free + premium, monetized
cp .env.example .env # fill in keys / builder / x402
docker compose up -d # serves POST /mcp on :8080, GET /healthz
Point an MCP HTTP client at https://your-host/mcp and send X-API-Key: <key> (or Authorization: Bearer <key>).
Node's built-in
fetchonly honorsHTTPS_PROXYwhenNODE_USE_ENV_PROXY=1(Node ≥ 22.21). Behind an egress proxy, set that env var.
Pricing
| Tier | Limit | Price |
|---|---|---|
| anonymous (no key) | free tools only | — |
| free key | 100 premium calls/month | $0 |
| pro key | unlimited premium calls | $29 per 30 days |
| x402 pay-per-call | per premium call | $0.01 USDC on Base |
How to get each
- Free key: call
hl_request_free_key. Instant, no signup. - x402 pay-per-call: on the hosted server a premium call without a key answers with x402 payment
requirements (0.01 USDC on Base, exact scheme); an x402-capable client signs the payment, retries with
the
X-PAYMENTheader, and the call runs. The payment is settled only after the tool has delivered, so a failed call costs nothing. - Pro: call
hl_buy_pro. It answers with x402 payment requirements ($29 in USDC on Base); an x402-capable client pays and retries with theX-PAYMENTheader, and the answer carries your Pro key, valid for 30 days (shown once: keep it). Call it again with your key inX-API-Keyto add 30 days to its end; a free key is upgraded in place and keeps its alerts. The key is activated before the payment is settled and a renewal only after, so a payment that fails costs nothing. Payments are final, there are no automatic refunds: if something went wrong, open an issue with the time of the payment. Without an x402 client, open an issue titled "Pro key request" instead and say how to reach you; never post a key in an issue. When a Pro key runs out it works like no key (free tools, x402 per call) and the error says how to renew; its alerts keep running for now.
For operators
- API keys: provision via
HYPERSIGNAL_PRO_KEYS/HYPERSIGNAL_FREE_KEYS(comma-separated raw keys, hashed before storage in SQLite; they never expire). Bought keys live in the same table with an end date, and every purchase is recorded inpro_purchases. Usage counters are per key, per month. A key removed from these lists is revoked on the next start, as long as at least one key stays listed: two empty lists read as a lost secret and revoke nothing. - x402: when a request has no key/quota and
X402_ENABLED=true, premium tools return an x402 payment-required response with requirements; after facilitator verification+settlement the call runs. Without a facilitator it fails closed (never fabricates a payment). - Apify:
apify-actor/re-exports the best-selling premium tools as a pay-per-event Actor. It is private for now.
🔌 Builder code (connect our terminal config)
Route your Hyperliquid orders through HyperSignal's builder code to support the project:
set HL_BUILDER_ADDRESS and (optionally) HL_BUILDER_FEE_TENTHS_BPS (tenths of a bp; default 5 = 0.5 bp,
Hyperliquid perp cap is 10 bp). One-time approval from your main wallet:
hl_approve_builder_fee_guide → gives you the exact approveBuilderFee payload + steps
The server never sees your main key; you sign the approval yourself.
Architecture
src/
core/ Hyperliquid Info client, WS mids feed (+REST fallback), LRU+TTL cache, rate limiter, retries
hl/ typed endpoints, market/account/whale normalization, cohort resolution
tools/ one file per tool (Zod input + outputSchema + annotations); free / premium / trading
billing/ SQLite keys + monthly counters, tiers, x402 (fail-closed)
trading/ L1 action signing (viem + msgpack), dry-run-first exchange service
server-core.ts builds an McpServer for a tier set + billing gate
server-stdio.ts local entrypoint (free + trading)
server-http.ts remote entrypoint (free + premium, stateless JSON)
apify-actor/ thin pay-per-event wrapper
evals/ 10 read-only, time-stable eval questions
docs/ PHASE0 research report, GTM checklist
Design rules enforced: no secrets outside .env; trading never remote; every external call has a
timeout + 3 exponential retries + graceful degradation; responses are aggregated/paginated/truncated;
premium/trading tools carry financial disclaimers; only Hyperliquid endpoints verified in Phase 0.
Development
npm run dev:stdio # tsx, no build
npm run dev:http
npm run typecheck # strict, no `any`
npm test # offline unit tests (signing, stats, aggregation, cache)
npm run build
License
MIT. Not affiliated with Hyperliquid. Use at your own risk.
コメント
AI アプリケーションが外部のツールやデータソースに統一的な方法で接続するためのオープンなプロトコルです。クライアントはモデルとの対話を担い、MCP サーバーはツール・リソース・プロンプトテンプレートを提供します。標準メッセージでやり取りするため、1 つのサーバーを複数のクライアントで再利用できます。