# Hyperliquid (npm · @pipeworx/mcp-hyperliquid)

Hyperliquid MCP — read-only market data from Hyperliquid's public info API.

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 78/100, [markdown](https://verifymcp.io/servers/pipeworx-io-hyperliquid/hyperliquid-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-hyperliquid/hyperliquid-mcp)
- npm · `@pipeworx/mcp-hyperliquid`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid.md), [page](https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-hyperliquid`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-hyperliquid).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 67/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 11 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-hyperliquid -- npx -y @pipeworx/mcp-hyperliquid
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-hyperliquid": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hyperliquid"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-hyperliquid": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hyperliquid"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-hyperliquid -- npx -y @pipeworx/mcp-hyperliquid
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-hyperliquid": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-hyperliquid"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-hyperliquid --command npx --arg -y --arg @pipeworx/mcp-hyperliquid
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-hyperliquid:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-hyperliquid"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-hyperliquid": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-hyperliquid"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-hyperliquid -t stdio -c npx -a -y @pipeworx/mcp-hyperliquid
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-hyperliquid": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-hyperliquid"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 66, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 81, +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.

### 2026-10-30 (score 80, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (10)

### `hyperliquid_perp_meta` (~197 tokens)

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.

Input parameters:

- `coin` (string): Optional — filter to one perp symbol, e.g. "BTC" or "ETH". Omit to list the whole universe.

### `hyperliquid_spot_meta` (~177 tokens)

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).

### `hyperliquid_mids` (~151 tokens)

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.

Input parameters:

- `coin` (string): Optional — return only this symbol's mid price, e.g. "BTC" or "ETH". Omit to get the full map.

### `hyperliquid_asset_context` (~183 tokens)

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.

Input parameters:

- `coin` (string, required): Perp symbol, e.g. "BTC", "ETH", "SOL". See hyperliquid_perp_meta for the full list.

### `hyperliquid_l2_book` (~218 tokens)

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.

Input parameters:

- `coin` (string, required): 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.

### `hyperliquid_candles` (~379 tokens)

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.

Input parameters:

- `coin` (string, required): 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.

### `hyperliquid_funding_history` (~230 tokens)

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).

Input parameters:

- `coin` (string, required): 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.

### `hyperliquid_account_state` (~202 tokens)

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"}.

Input parameters:

- `address` (string, required): 0x-prefixed 42-character wallet address.

### `hyperliquid_spot_balances` (~152 tokens)

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"}.

Input parameters:

- `address` (string, required): 0x-prefixed 42-character wallet address.
- `limit` (number): Max token rows to return, largest first (default 50). Totals always cover every token.

### `hyperliquid_account_history` (~171 tokens)

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"}.

Input parameters:

- `address` (string, required): 0x-prefixed 42-character wallet address.
- `period` (string): Window (default "week").
- `scope` (string): "combined" (default) = perp + spot; "perp" = perp only.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 66
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79

## Common questions

### 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.

### What did VerifyMCP test on the Hyperliquid MCP server?

VerifyMCP ran 16 checks on Hyperliquid, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-hyperliquid
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-hyperliquid
- Repository: https://github.com/pipeworx-io/mcp-hyperliquid
- Website: https://pipeworx.io/packs/hyperliquid
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-hyperliquid/pipeworx-mcp-hyperliquid