Hydromancer
NPM · HYDROMANCER-MCP
Read-only Hyperliquid data: wallets, top traders, markets, funding and liquidations.
Available components
Last scanned (27 minutes ago)
Scores higher than 36% of npm servers
Category Finance and Payments
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. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability58
- 50% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Partial
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3002 tokens (~150/item across 20 items; 19 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 87% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +1
- Stability: unverified → 0.10 ▲ functional
- 1 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 67
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/hydromancer-mcp@0.2.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
hydromancer_builder_activity Builder app activity (trades routed through an app) ~176
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.
| Name | Type | Req | Description |
|---|---|---|---|
| builder | string | yes | Builder (app) address. |
| limit | integer | – | How many rows to return (default 25, max 2000). |
| since | string|number | – | Default "1h". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_compare_wallets Compare many wallets at once ~139
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?".
| Name | Type | Req | Description |
|---|---|---|---|
| addresses | array | yes | Wallet addresses to look up. |
| includeHip3 | boolean | – | Include HIP-3 markets (limit drops to 100 wallets). |
| minBalanceUsd | number | – | Only return wallets with at least this balance (see balanceNote on each wallet). |
No output schema declared.
No examples provided.
hydromancer_funding_history Funding rate history for a market ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| since | string|number | – | Default "7d". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_list_markets List every market and HIP-3 exchange ~120
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.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| limit | integer | – | How many rows to return (default 100, max 2000). |
| search | string | – | Text to search for, e.g. "tsla", "gold", "pepe". |
No output schema declared.
No examples provided.
hydromancer_market_depth Order book depth and slippage ~146
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| orderSizeUsd | number | – | Order size for the slippage estimate, in USD (default 100,000). |
| since | string|number | – | Slippage history window. Default "24h". |
No output schema declared.
No examples provided.
hydromancer_market_snapshot Live price, volume and open interest for markets ~132
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").
| Name | Type | Req | Description |
|---|---|---|---|
| coins | array | – | Markets to show, e.g. ["BTC","ETH","xyz:TSLA"]. Omit for the busiest markets. |
| top | integer | – | When coins is empty, how many top markets by 24h volume (default 15). |
No output schema declared.
No examples provided.
hydromancer_my_usage My Hydromancer API usage ~61
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.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | Days to look back (default 7). |
No output schema declared.
No examples provided.
hydromancer_open_interest_history Open interest history ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| interval | string | – | Bucket size (default "1h"). |
| since | string|number | – | Default "24h". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_prediction_markets Prediction markets (HIP-4 outcomes) ~119
Settled Hyperliquid prediction markets (HIP-4 outcomes) with their result and trading stats, searchable by text, underlying asset or category.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Category, e.g. "sports", "politics". |
| limit | integer | – | How many rows to return (default 20, max 100). |
| search | string | – | Free text, e.g. "election", "BTC above". |
| underlying | string | – | Underlying asset, e.g. "HYPE", "BTC". |
No output schema declared.
No examples provided.
hydromancer_price_history Price candles (OHLCV) ~200
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | yes | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| interval | string | – | Candle size (default "1h"). "1s" only covers about the last 30 minutes. |
| since | string|number | – | Default "24h". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_raw_request Advanced: any Hydromancer API request ~143
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | object | yes | Request body, e.g. {"type":"vaultSummaries"} or {"type":"historicalOrders","user":"0x..."}. |
| limit | integer | – | How many rows to return (default 200, max 5000). |
No output schema declared.
No examples provided.
hydromancer_recent_liquidations Recent liquidations ~119
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.
| Name | Type | Req | Description |
|---|---|---|---|
| coin | string | – | Market to check; omit for every market. |
| limit | integer | – | How many rows to return (default 50, max 1000). |
| since | string|number | – | Default "24h". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_top_traders Top traders leaderboard ~251
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.
| Name | Type | Req | Description |
|---|---|---|---|
| builder | string | – | Only traders who have traded through this builder's app. |
| excludeBots | boolean | – | Drop wallets that look automated (human score below 60). Default true. |
| limit | integer | – | How many rows to return (default 25, max 1000). |
| market | string | – | Only "main" (native Hyperliquid) or a HIP-3 dex such as "xyz". Omit for all. |
| minDaysActive | integer | – | Minimum distinct active days (default 1). |
| minTrades | integer | – | Minimum completed trades (default 5). |
| offset | integer | – | Rows to skip, for paging. |
| period | string | – | Time period (default "30d"). |
| rankBy | string | – | Ranking (default "profit"). |
No output schema declared.
No examples provided.
hydromancer_wallet_closed_trades Wallet closed trades (open-to-close round trips) ~242
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
| coin | string | – | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| limit | integer | – | How many rows to return (default 100, max 500). |
| since | string|number | – | Start of window. Default "30d". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_wallet_funding Wallet funding payments ~89
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
| since | string|number | – | Default "7d". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
hydromancer_wallet_open_orders Wallet open orders (limits, stop-losses, take-profits) ~60
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
No output schema declared.
No examples provided.
hydromancer_wallet_overview Wallet overview: balance, open positions, PnL record ~153
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
| includeHip3 | boolean | – | Also include positions on HIP-3 markets (stocks, indices, commodities). Default false. |
No output schema declared.
No examples provided.
hydromancer_wallet_trades Wallet trade history (fills) ~323
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
| coin | string | – | Market name, any case: "BTC", "eth", "HYPE", "kPEPE", or a HIP-3 market such as "xyz:TSLA". |
| limit | integer | – | How many rows to return (default 100, max 2000). |
| mergeSplitOrders | boolean | – | Merge pieces of one order into a single fill (default true). |
| offset | integer | – | Rows to skip, for paging. |
| since | string|number | – | Start of window. Relative ("30m", "6h", "24h", "7d"), a date ("2026-10-01"), a date-time ("2026-10-01T12:00:00Z"), "now", or Unix ms. Default "24h". |
| until | string|number | – | End of window. Default now. |
No output schema declared.
No examples provided.
hydromancer_wallet_transfers Wallet deposits, withdrawals, transfers and liquidations ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Wallet address, 0x followed by 40 hex characters. |
| limit | integer | – | How many rows to return (default 100, max 2000). |
| since | string|number | – | Default "30d". |
| until | string|number | – | – |
No output schema declared.
No examples provided.
How do I install the Hydromancer MCP server?
Hydromancer runs locally as an npm package, launched with npx -y hydromancer-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · hydromancer-mcp
claude mcp add joshavenue-hydromancer-mcp -- npx -y hydromancer-mcp
What is the Hydromancer MCP server?
Hydromancer is an MCP server listed in the public MCP registry as io.github.joshavenue/hydromancer-mcp. Read-only Hyperliquid data: wallets, top traders, markets, funding and liquidations. This page covers its npm package (hydromancer-mcp).
Is the Hydromancer MCP server safe to use?
Hydromancer scores 69 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. 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 Hydromancer MCP server expose?
Hydromancer exposes 19 tools: hydromancer_wallet_overview, hydromancer_compare_wallets, hydromancer_wallet_trades, hydromancer_wallet_closed_trades, hydromancer_wallet_open_orders, and 14 more. Their descriptions and schemas cost roughly 2,880 tokens of context every time the server is loaded.
Is the Hydromancer MCP server still maintained?
Hydromancer 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 Hydromancer MCP server under?
Hydromancer declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.