Hydromancer MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| HYDROMANCER_API_KEY | Yes | Your Hydromancer API key (required). | |
| HYDROMANCER_BASE_URL | No | API endpoint. Only the mainnet and testnet Hydromancer hosts are accepted. | https://api.hydromancer.xyz/info |
| HYDROMANCER_TIMEOUT_MS | No | Request timeout in milliseconds. | 30000 |
| HYDROMANCER_MAX_RESULT_CHARS | No | Cap on one tool result, so the AI is not flooded. | 40000 |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hydromancer_wallet_overviewA | One-call profile of any Hyperliquid wallet: account value, every open perp position (side, size, entry, liquidation price, leverage, unrealized PnL), spot balances and its realized trading record (PnL, win rate, trade count, volume, human score). Use this first for questions like "what is this wallet holding?" or "is this trader any good?". Set includeHip3=true to include HIP-3 markets such as xyz:TSLA. |
| hydromancer_compare_walletsA | Look up balance, account mode and open positions for up to 1,000 wallets (100 when includeHip3=true), sorted by balance. Handles unified-account and portfolio-margin wallets, whose money sits in spot rather than perps. Use for watchlists: "which of these wallets are whales?", "what do these 50 traders hold?". |
| hydromancer_wallet_tradesA | Every fill (buy/sell execution) a wallet made in a time window, newest first, with totals: volume, realized PnL, fees and a per-coin breakdown. since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. Default window: last 24h. Large orders split into many fills are merged by default. |
| hydromancer_wallet_closed_tradesA | Completed trades for a wallet: each row is a full position from open to close with entry, exit, size, gross and net PnL, fees, funding and how long it was held. Best tool for judging trading skill ("what is this wallet's win rate and best coin?"). Default window: last 30 days. since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. |
| hydromancer_wallet_open_ordersB | All resting orders for a wallet right now, including stop-loss and take-profit triggers. Shows where a trader plans to buy, sell or exit. |
| hydromancer_wallet_transfersA | Money movements for a wallet: deposits, withdrawals, sends, spot/perp transfers, vault deposits and liquidations. Default window: last 30 days. since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. |
| hydromancer_wallet_fundingA | Funding paid or received by a wallet's open positions, hour by hour, with totals per coin. Positive = received, negative = paid. Default window: last 7 days. |
| hydromancer_top_tradersA | Rank Hyperliquid traders by realized profit, win rate or volume over 1 day to all time, with filters that remove bots and one-off wallets. Use for "who are the best traders this week?", "find consistent winners on stocks (dex xyz)" or "top traders using builder X". Pair with hydromancer_wallet_overview to see what they hold now. |
| hydromancer_market_snapshotA | Current mark/oracle/mid price, 24h volume and open interest (in coins and USD) for one or more markets. The top-markets list also shows max leverage. Leave coins empty for the top markets by 24h volume. Works for HIP-3 markets (e.g. "xyz:TSLA"). |
| hydromancer_price_historyA | Price history as candles (open, high, low, close, volume) for any market. Intervals from 1 second to 1 month. Default: 1h candles for the last 24h. since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. |
| hydromancer_funding_historyA | Hourly funding rates for a market over time, with the average and annualized rate. Positive funding means longs pay shorts. Default window: last 7 days. |
| hydromancer_open_interest_historyA | How open interest (total open positions) in a market changed over time, in coins and USD. Rising OI with rising price usually means new longs; falling OI means positions are closing. Default: hourly for the last 24h. |
| hydromancer_recent_liquidationsA | Positions that were force-closed (liquidated), newest first, for one market or the whole exchange, with totals by side. "Long liquidated" means a long position was wiped out. Default window: last 24h. |
| hydromancer_market_depthA | How much can be bought or sold near the current price. Returns USD depth on each side within 0.1% to 2% of the price for a market, plus the expected slippage for a market order of a given size over time. |
| hydromancer_list_marketsA | Lists every tradable perp market, optionally filtered by search text or category (crypto, stocks, indices, commodities, fx), plus the HIP-3 exchanges (perp DEXs) that list stocks and other assets. Use when unsure of a market's exact name. |
| hydromancer_builder_activityA | Fills routed through a builder (a trading app such as MetaMask, Phantom or a Telegram bot) by its builder address, with volume, builder fees earned, unique traders and top coins. Default window: last 1h (busy builders produce thousands of fills). since/until accept Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. |
| hydromancer_prediction_marketsB | Settled Hyperliquid prediction markets (HIP-4 outcomes) with their result and trading stats, searchable by text, underlying asset or category. |
| hydromancer_my_usageA | Your own Hydromancer API usage by day and request type: requests, failures, speed and billable tokens. Use to check how much of your plan you are using. |
| hydromancer_raw_requestA | Send any Hydromancer /info request directly, for endpoints the other tools do not cover (e.g. vaultSummaries, historicalOrders, spotMeta, outcomeMeta, delegations, perpDexStatus). Pass the request body as JSON including "type". Full list: https://docs.hydromancer.xyz/llms.txt . Read-only: this server never places orders. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| hydromancer_guide | Which Hydromancer tool answers which question, plus recipes. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| hydromancer_guide |
TDQS
Scored across 19 tools
Most tools target clearly different resources or actions, such as wallet fills versus completed positions, market snapshots versus price history, and wallet funding versus market funding history. There is some overlap around wallet performance: wallet_overview, wallet_closed_trades, and top_traders can all answer questions about win rate or trader quality, and raw_request is a catch-all that overlaps every tool.
All tools use a consistent hydromancer_ prefix with snake_case names. The set mixes descriptive noun phrases and verb-led names, but the convention is predictable and readable throughout.
At 19 tools the server is on the heavy side, but the breadth matches a multi-domain Hyperliquid analytics surface covering wallets, markets, liquidations, builders, prediction markets, and usage. Each tool maps to a distinct data need, with no obviously redundant tools.
The surface covers the core read-only analytics workflow very well: wallet profiling, trades, positions, orders, transfers, market data, history, depth, rankings, and liquidations. Some Hyperliquid endpoints such as active prediction markets, spot metadata, historical orders, and vault details are only reachable through raw_request, so coverage is broad but not fully first-class.