# Hyperliquid Agent Gateway (pypi · hyperliquid-agent-gateway)

Read-only MCP gateway to Hyperliquid: liquidation distance, funding carry, HyperEVM flows. No keys.

- Trust score: 66/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-01

## Components

- pypi · `hyperliquid-agent-gateway`: 66/100 (this document), [markdown](https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway.md), [page](https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway)

## Channel facts

- Registry: `pypi`
- Package: `hyperliquid-agent-gateway`
- Version: `0.1.3`
- 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-10-01.

- **Supply Chain Security**: 50/100
  - Malware scan not yet available for this package.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 15 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to alekskram/hyperliquid-agent-gateway).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 8 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1624 tokens (~135/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Hyperliquid Agent Gateway MCP server?

Hyperliquid Agent Gateway runs locally as a PyPI package, launched with uvx hyperliquid-agent-gateway. 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 alekskram-hyperliquid-agent-gateway -- uvx hyperliquid-agent-gateway
```

### Cursor

```json
{
  "mcpServers": {
    "alekskram-hyperliquid-agent-gateway": {
      "command": "uvx",
      "args": [
        "hyperliquid-agent-gateway"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "alekskram-hyperliquid-agent-gateway": {
      "command": "uvx",
      "args": [
        "hyperliquid-agent-gateway"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add alekskram-hyperliquid-agent-gateway -- uvx hyperliquid-agent-gateway
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "alekskram-hyperliquid-agent-gateway": {
      "type": "local",
      "command": [
        "uvx",
        "hyperliquid-agent-gateway"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add alekskram-hyperliquid-agent-gateway --command uvx --arg hyperliquid-agent-gateway
```

### Hermes

```yaml
mcp_servers:
  alekskram-hyperliquid-agent-gateway:
    command: "uvx"
    args: ["hyperliquid-agent-gateway"]
```

### Netclaw

```json
{
  "McpServers": {
    "alekskram-hyperliquid-agent-gateway": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "hyperliquid-agent-gateway"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add alekskram-hyperliquid-agent-gateway -t stdio -c uvx -a hyperliquid-agent-gateway
```

### Other

```json
{
  "mcpServers": {
    "alekskram-hyperliquid-agent-gateway": {
      "command": "uvx",
      "args": [
        "hyperliquid-agent-gateway"
      ]
    }
  }
}
```

## 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-10-01 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-30 (score 65, −15)

- [security regression] Malware scan: pass → unverified

### 2026-09-29 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-09-28 (score 64, −5)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-27 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-25 (score 68, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-23 (score 67, +1)

- [security regression] Tool safety: pass → unverified
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.03
- [functional] First check of Schema quality: unverified
- [functional] Package version: 0.1.2 → 0.1.3

### 2026-09-22 (score 66)

First indexed and scored.

## MCP tools (12)

### `market_overview` (~112 tokens)

Market Overview

Perp market overview from ONE metaAndAssetCtxs call (~233 perps):
per-coin mark, open interest, day volume, premium (funding basis),
max leverage, plus totals (sum OI, sum day volume). Rows are sorted
by `sort` in {open_interest (default), volume, premium} descending
and capped at `limit` (max 100). Example: market_overview(limit=10)

Input parameters:

- `limit` (integer)
- `sort` (string)

### `spot_overview` (~106 tokens)

Spot Overview

Spot market overview (~326 pairs) from spotMeta +
spotMetaAndAssetCtxs: pair rows (name, mark, day volume, OI where
published) with HIP-1 <-> ERC-20 links resolved - '@{index}' spot
coin names are mapped to token names via spotMeta.tokens. Sorted by
day volume descending, capped at `limit` (max 100).
Example: spot_overview(limit=10)

Input parameters:

- `limit` (integer)

### `quote` (~125 tokens)

Quote

One coin's live quote from l2Book: bid/ask/mid/spread and
top-of-book sizes. mid is the book midpoint ((bid+ask)/2) whenever
both sides are present ('book'); allMids is only a labeled fallback
when the book lacks a side ('allMids'), so mid never escapes the
[bid, ask] range. The coin is validated against the perp
universe (spot '@{index}/NAME' pairs pass through to the book).
Example: quote(coin="BTC")

Input parameters:

- `coin` (string, required)

### `order_book` (~97 tokens)

Order Book

Aggregated order book for one coin from l2Book: `depth` levels per
side (default 10, max 100), aggregated by the book's nSigFigs
precision (default taken from the response levels), with total
liquidity (sum px*sz) per side. Example: order_book(coin="ETH",
depth=20)

Input parameters:

- `coin` (string, required)
- `depth` (integer)

### `candles` (~119 tokens)

Candles

OHLCV candles from candleSnapshot for `coin`: rows newest-first,
capped at `limit` (max 500). startTime is computed so roughly
\`limit` candles of `interval` are requested. Valid intervals: 1m,
15m, 1h, 4h, 1d, 1w, 1M. Example: candles(coin="BTC",
interval="4h", limit=50)

Input parameters:

- `coin` (string, required)
- `interval` (string)
- `limit` (integer)

### `trades` (~78 tokens)

Trades

Recent public fills from recentTrades(coin) WITH both sides'
addresses: rows (newest-first, max 500) carry side, px, sz, time,
coin, hash and users [maker, taker]. Example: trades(coin="BTC",
limit=10)

Input parameters:

- `coin` (string, required)
- `limit` (integer)

### `funding_history` (~94 tokens)

Funding History

Hourly funding history for `coin` (fundingHistory) plus the
CURRENT premium from metaAndAssetCtxs (premium_now): rows carry
fundingRate (hourly), premium, time (ms). Newest-first, capped at
\`limit` (max 500). Example: funding_history(coin="BTC", limit=48)

Input parameters:

- `coin` (string, required)
- `limit` (integer)

### `liquidation_risk` (~239 tokens)

Liquidation Risk

KEY TOOL. Liquidation risk for one perp account
(clearinghouseState + userFunding): margin summary (accountValue,
totalRawUsd, totalMarginUsed, withdrawable), cross maintenance
margin, per-position leverage/entry/mark/unrealizedPnl and
liquidationPx when the venue provides it. Positions in the LIVE
clearinghouseState response carry NO markPx: mark is resolved per
coin from metaAndAssetCtxs (fallback allMids) and each row says
where it came from in mark_px_source ('position' | 
'metaAndAssetCtxs' | 'allMids' | null). When liquidationPx is
null, liq_distance_pct is an ESTIMATE from the maintenance-margin
ratio (crossMaintenanceMarginUsed / marginSummary.accountValue;
isolated positions use marginUsed / positionValue) - flagged
'estimated': true, liqPx stays null (honest). funding_drag totals
negative funding payments from userFunding. Address must be 0x +
40 hex. Example: liquidation_risk(address="0x...")

Input parameters:

- `address` (string, required)

### `trader_activity` (~111 tokens)

Trader Activity

Trading profile for one address (userFills + userFunding +
clearinghouseState): total closed PnL, fees (fee + builderFee),
volume, fill count, win-rate-ish share of fills with closedPnl > 0,
per-coin breakdown, net funding and open positions. `limit` caps
fills analyzed (max 500, newest-first).
Example: trader_activity(address="0x...", limit=100)

Input parameters:

- `address` (string, required)
- `limit` (integer)

### `funding_carry_screener` (~119 tokens)

Funding Carry Screener

Rank ALL perps from ONE metaAndAssetCtxs call by `metric`
(premium default; oi / volume options) and return the topN rows
with premium, oi, dayVolume, markPx. fundingHistory rows are fetched
ONLY for the topN coins (weight economy) and appear as
'funding_history' on rows where that call succeeded.
Example: funding_carry_screener(topN=5, metric="premium")

Input parameters:

- `metric` (string)
- `topN` (integer)

### `token_transfers` (~181 tokens)

Token Transfers

Recent ERC-20 Transfer events for `contract` on HyperEVM via
eth_getLogs with an ADAPTIVE window (starts 30 blocks, halves on
too-big/failing responses, doubles on quiet ones up to 60; active
tokens need ~30-60 block windows). Rows (newest-first, max 500):
from, to, value (raw/1e18, 6dp), txHash, blockNumber, ts when the
log carries a timestamp. `from_block` anchors the walk (default:
latest - 300). Errors degrade to an honest error dict naming the
RpcError kind (rate-limit vs window-too-wide narrative).
Example: token_transfers(contract="0x...", limit=50)

Input parameters:

- `contract` (string, required)
- `from_block`
- `limit` (integer)

### `wallet_balance` (~116 tokens)

Wallet Balance

Wallet balances on HyperEVM + Hyperliquid spot: native balance
(eth_getBalance), ERC-20 balances via eth_call balanceOf for up to
20 tokens resolved from spotMeta tokens with 0x contract addresses
(cap respects the 100 req/min rpc budget), and Hyperliquid spot
balances via spotClearinghouseState. Per-token rows: token,
balance_raw (wei), balance (units, 6dp), source.
Example: wallet_balance(address="0x...")

Input parameters:

- `address` (string, required)

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway#diagnostics

## Score history

- 2026-10-01: 66
- 2026-09-30: 65
- 2026-09-29: 80
- 2026-09-28: 64
- 2026-09-27: 69
- 2026-09-26: 68
- 2026-09-25: 68
- 2026-09-24: 67
- 2026-09-23: 67
- 2026-09-22: 66

## Common questions

### What is the Hyperliquid Agent Gateway MCP server?

Hyperliquid Agent Gateway is an MCP server listed in the public MCP registry as io.github.alekskram/hyperliquid-agent-gateway. Read-only MCP gateway to Hyperliquid: liquidation distance, funding carry, HyperEVM flows. No keys. This page covers its PyPI package (hyperliquid-agent-gateway).

### Is the Hyperliquid Agent Gateway MCP server safe to use?

Hyperliquid Agent Gateway scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. 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 Agent Gateway MCP server expose?

Hyperliquid Agent Gateway exposes 12 tools: market_overview, spot_overview, quote, order_book, candles, and 7 more. Their descriptions and schemas cost roughly 1,497 tokens of context every time the server is loaded.

### Is the Hyperliquid Agent Gateway MCP server still maintained?

Hyperliquid Agent Gateway is still listed as active in the MCP registry. We last reached this channel on 1 October 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 Agent Gateway MCP server under?

Hyperliquid Agent Gateway declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/hyperliquid-agent-gateway/
- Socket report: https://socket.dev/pypi/package/hyperliquid-agent-gateway
- Repository: https://github.com/alekskram/hyperliquid-agent-gateway
- Changelog RSS feed: https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway.xml
- Changelog JSON feed: https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway.json
- HTML version of this page: https://verifymcp.io/servers/alekskram-hyperliquid-agent-gateway/hyperliquid-agent-gateway