hyperliquid-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_markets | List Hyperliquid perpetual markets with mark price, 24h change, 24h volume, open interest, funding rate (1h and annualized APR) and max leverage. Pass |
| get_price | Current mid prices. Pass |
| get_orderbook | L2 order book snapshot for a perp market: best bid/ask, spread, and aggregated levels per side. |
| get_candles | Historical OHLCV candles for a perp market. Intervals: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 8h, 12h, 1d, 3d, 1w. |
| get_account | Full account state for any Hyperliquid address: account value, margin usage, withdrawable, every open perp position (side, size, entry, liquidation price, unrealized PnL, leverage) and spot balances. Read-only public data. |
| get_open_ordersA | Resting open orders for an address: side, price, size, order type, trigger info. |
| get_recent_fills | Most recent trade fills for an address: direction (Open Long / Close Short / ...), price, size, notional, closed PnL and fees. |
| get_funding_paidA | Net funding paid or received by an address over the last N hours, broken down by coin. Positive = received, negative = paid. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools address completely different aspects: one provides open orders, the other provides funding history. There is no overlap or ambiguity.
Both tools follow a consistent 'get_<noun>' pattern, making the naming predictable and clear.
With only 2 tools, the server feels very thin for a trading platform. Typically one would expect many more operations like placing/canceling orders, getting positions, etc.
The server lacks essential operations such as placing, canceling, or modifying orders, as well as getting account balances or positions. The limited surface cannot support meaningful trading workflows.