Hyperliquid
NPM · @PIPEWORX/MCP-HYPERLIQUID · 2 COMPONENTS
Hyperliquid MCP — read-only market data from Hyperliquid's public info API.
Available components
Last scanned (3 hours ago)
Scores higher than 76% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hyperliquid). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2115 tokens (~211/item across 10 items; 10 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- Package version: 0.2.0 → 0.2.1 functional
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 29 Oct 26 79
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-hyperliquid@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-hyperliquid |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-hyperliquid/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3637399847 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:37179d2408d96769402865275a1d446b9cde8addf691a90091a59fcc2b5f7d34111eed149945a25df6f53e9b05ae8acde212286c0aca63f5fc1e19873 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hyperliquid_account_history ~171
Account value and PnL history for one Hyperliquid wallet address over a day, week, month or all time -- starting and ending account value, PnL change, trading volume, then a downsampled series. Scope "combined" is perp plus spot; "perp" is perp only. Public on-chain data, keyless. e.g. {address:"0x31dea2516beee92135b96f464eeec3cf292a13f2", period:"week"}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x-prefixed 42-character wallet address. |
| period | string | – | Window (default "week"). |
| scope | string | – | "combined" (default) = perp + spot; "perp" = perp only. |
No output schema declared.
No examples provided.
hyperliquid_account_state ~202
Perpetuals account state for one Hyperliquid wallet address -- two separate flags (account_has_balance: non-zero account value, idle dust included; account_has_open_perp_positions: a position is open or notional / margin is non-zero), then account value, total notional, margin used, withdrawable, cross-maintenance margin, and every open perp position (coin, signed size where negative = short, entry price, position value, unrealized PnL, ROE, liquidation price, leverage, margin used, cumulative funding). Public on-chain data, keyless. Use for "what is this Hyperliquid wallet's position / margin / leverage". Returns aggregates first, positions last. e.g. {address:"0x31dea2516beee92135b96f464eeec3cf292a13f2"}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x-prefixed 42-character wallet address. |
No output schema declared.
No examples provided.
hyperliquid_asset_context ~183
Live perp market context for one contract — current funding rate, open interest, mark price, oracle price, mid price, 24h premium, and 24h notional + base volume — from Hyperliquid's public info API ({"type":"metaAndAssetCtxs"}, matched to the requested coin by universe index). This is the single call that answers "what is BTC perp funding right now" or "what is Hyperliquid's open interest in ETH" — the live numbers next to kalshi_* and polymarket_* for anyone pricing crypto-adjacent prediction markets. For a HISTORY of funding rates rather than the current one, use hyperliquid_funding_history.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Perp symbol, e.g. "BTC", "ETH", "SOL". See hyperliquid_perp_meta for the full list. |
No output schema declared.
No examples provided.
hyperliquid_candles ~379
OHLCV candles for one Hyperliquid perp or spot symbol, from Hyperliquid's public info API ({"type":"candleSnapshot"}). Each candle: open/high/low/close/volume (base units), trade count, and the interval's start/end timestamps. Pass `lookback_hours` for a window ending now (default 24h), or an explicit `start_time`/`end_time` (ISO date/datetime or unix seconds/milliseconds) for a specific historical window — Hyperliquid retains candle history well beyond 24h. `interval` accepts Hyperliquid's own granularities: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 3d, 1w, 1M.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Perp symbol (e.g. "BTC") or spot pair id/name (e.g. "@0" or "PURR/USDC"). |
| end_time | string | – | Window END — same formats as start_time. Defaults to now. |
| interval | string | – | 1m | 3m | 5m | 15m | 30m | 1h | 2h | 4h | 8h | 12h | 1d | 3d | 1w | 1M (default "1h") |
| lookback_hours | number | – | Window length ending now, in hours (default 24). Ignored when start_time is given. |
| start_time | string | – | Window START — ISO date/datetime or unix seconds/milliseconds. Use with end_time for a window that does not end now. |
No output schema declared.
No examples provided.
hyperliquid_funding_history ~230
Historical funding-rate payments for one Hyperliquid perp — timestamped funding rate and premium at each funding interval (hourly on Hyperliquid), from Hyperliquid's public info API ({"type":"fundingHistory"}). Use this to see how funding has trended (e.g. persistently positive BTC funding = longs paying shorts = crowded long), or to reconstruct realized funding cost over a window. For the CURRENT funding rate only, hyperliquid_asset_context is cheaper (one call, no window math).
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Perp symbol, e.g. "BTC", "ETH", "SOL". |
| end_time | string | – | Window END — same formats as start_time. Defaults to now. |
| lookback_hours | number | – | Window length ending now, in hours (default 24, funding pays hourly so this returns ~1 row/hour). Ignored when start_time is given. |
| start_time | string | – | Window START — ISO date/datetime or unix seconds/milliseconds. Use with end_time for a window that does not end now. |
No output schema declared.
No examples provided.
hyperliquid_l2_book ~218
Live level-2 order book (bids + asks, each with price, aggregate size, and order count) for one Hyperliquid perp or spot symbol, from Hyperliquid's public info API ({"type":"l2Book"}). Returns two arrays — bids (best first, descending price) and asks (best first, ascending price) — each entry {px, sz, n}. Use `depth` to trim to the top N levels per side; Hyperliquid itself returns the full book (often 20+ levels per side) when depth is omitted.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Perp symbol (e.g. "BTC") or spot pair id (e.g. "@0" from hyperliquid_spot_meta, or the canonical name like "PURR/USDC"). |
| depth | number | – | Levels to keep per side, best-first (default: all levels Hyperliquid returns, typically 20+). Pass e.g. 5 for just the top of book. |
No output schema declared.
No examples provided.
hyperliquid_mids ~151
Live mid prices (midpoint of best bid/ask) for every asset Hyperliquid tracks — perps by symbol ("BTC", "ETH", ...) and spot pairs by numeric id ("@0", "@1", ...) — in one call, from Hyperliquid's public info API ({"type":"allMids"}). This is the cheapest way to get a current price: one request returns 1,000+ symbols. Pass `coin` to get just one symbol's mid price instead of the full map.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Optional — return only this symbol's mid price, e.g. "BTC" or "ETH". Omit to get the full map. |
No output schema declared.
No examples provided.
hyperliquid_perp_meta ~197
Perpetuals universe metadata from Hyperliquid's public info API ({"type":"meta"}) — every perp contract Hyperliquid lists (currently 190+), each with its symbol, szDecimals (size precision), maxLeverage, and isDelisted when retired. This is the reference list to resolve a human-asked symbol ("BTC", "ETH", "SOL") to a contract Hyperliquid actually trades before calling hyperliquid_mids, hyperliquid_l2_book, hyperliquid_candles or hyperliquid_funding_history with it — those all take the bare coin symbol shown here (e.g. "BTC", not "BTC-PERP"). Pass `coin` to look up one symbol instead of the full list.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Optional — filter to one perp symbol, e.g. "BTC" or "ETH". Omit to list the whole universe. |
No output schema declared.
No examples provided.
hyperliquid_spot_balances ~152
Spot token balances for one Hyperliquid wallet address -- per token: total, amount on hold in open orders, available (total minus hold) and entry notional in USDC. Includes the spot USDC balance. Public on-chain data, keyless. Use for "what tokens does this Hyperliquid wallet hold". e.g. {address:"0x31dea2516beee92135b96f464eeec3cf292a13f2"}.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | 0x-prefixed 42-character wallet address. |
| limit | number | – | Max token rows to return, largest first (default 50). Totals always cover every token. |
No output schema declared.
No examples provided.
hyperliquid_spot_meta ~177
Spot market metadata from Hyperliquid's public info API ({"type":"spotMeta"}) — every spot trading pair Hyperliquid lists, each with its pair name (e.g. "PURR/USDC"), pair index, the two token ids it is composed of, and whether it is the canonical listing for that token. Hyperliquid names most non-canonical spot pairs generically ("@1", "@2", ...) because the human-readable name belongs to the canonical pair; this tool returns Hyperliquid's raw naming as-is. Use the `index` from here as the `coin` argument to hyperliquid_l2_book/hyperliquid_candles for a spot pair, in the form "@<index>" (Hyperliquid's own convention for spot coin ids distinct from perp symbols).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Hyperliquid MCP server?
Hyperliquid runs locally as an npm package, launched with npx -y @pipeworx/mcp-hyperliquid. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-hyperliquid
claude mcp add pipeworx-io-hyperliquid -- npx -y @pipeworx/mcp-hyperliquid
What is the Hyperliquid MCP server?
Hyperliquid is an MCP server listed in the public MCP registry as io.github.pipeworx-io/hyperliquid. Hyperliquid MCP, read-only market data from Hyperliquid's public info API. This page covers its npm package (@pipeworx/mcp-hyperliquid).
Is the Hyperliquid MCP server safe to use?
Hyperliquid scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Hyperliquid MCP server expose?
Hyperliquid exposes 10 tools: hyperliquid_perp_meta, hyperliquid_spot_meta, hyperliquid_mids, hyperliquid_asset_context, hyperliquid_l2_book, and 5 more. Their descriptions and schemas cost roughly 2,060 tokens of context every time the server is loaded.
Is the Hyperliquid MCP server still maintained?
Hyperliquid is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Hyperliquid MCP server under?
Hyperliquid declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.