hyperliquid-agent-gateway
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
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| market_overviewA | 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 |
| spot_overviewA | 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 |
| quoteA | One coin's live quote from allMids + l2Book: bid/ask/mid/spread and top-of-book sizes. The coin is validated against the perp universe (spot '@{index}/NAME' pairs pass through to the book). Example: quote(coin="BTC") |
| order_bookA | Aggregated order book for one coin from l2Book: |
| candlesA | OHLCV candles from candleSnapshot for |
| tradesA | 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) |
| funding_historyA | Hourly funding history for |
| liquidation_riskA | 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...") |
| trader_activityA | 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. |
| funding_carry_screenerA | Rank ALL perps from ONE metaAndAssetCtxs call by |
| token_transfersA | Recent ERC-20 Transfer events for |
| wallet_balanceA | 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...") |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/alekskram/hyperliquid-agent-gateway'
If you have feedback or need assistance with the MCP directory API, please join our Discord server