flowscan-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FLOWSCAN_BASE_URL | No | Base URL for requests. Only useful for testing against a mirror or a mock; the `source` field in results always shows `https://www.flowscan.xyz`. | https://www.flowscan.xyz |
| FLOWSCAN_TIMEOUT_MS | No | Per-request timeout in milliseconds. | 45000 |
| FLOWSCAN_CACHE_TTL_MS | No | In-memory cache lifetime for ordinary responses. Identical requests within this window reuse the cached result. | 20000 |
| FLOWSCAN_MAX_CONCURRENCY | No | Maximum simultaneous requests to Flowscan. Extra calls wait. | 4 |
| FLOWSCAN_MAX_RESULT_CHARS | No | Maximum characters in one tool result before truncation. | 60000 |
| FLOWSCAN_LONG_CACHE_TTL_MS | No | Cache lifetime for large, slow-changing payloads (HIP-3 snapshot, per-DEX and builder stats, Binance comparison, builders leaderboard and all-time summary, builders user series, builder intelligence). | 300000 |
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 |
|---|---|
| flowscan_coverageA | Start here when unsure. Returns the map of flowscan.xyz pages -> tools, what Flowscan does NOT serve (block/tx lookups, prices), the mainnet-only rule and output-shaping conventions. Optionally filter by a keyword (e.g. 'revenue', 'address', 'hip-3'): matching pages plus matching notServed items, with servedByThisServer=false when only notServed matches. Also lists HIP-3 dex display names vs on-chain prefixes. |
| flowscan_stablecoin_marginC | Homepage 'Stablecoin Perp Margin': total stablecoin value on HyperCore split into spot balances and perp margin (with unique holders/traders), and per token (USDC, USDT, USDE, USDH) spot/perp balances, holders, average/median, total value and market share %. USD. |
| flowscan_peersA | The /peers gossip-network crawl (~600 nodes). Default: meta (crawl time, counts, reachability, states), footprint (top countries/ASNs) and sentries (validator sentries with operator, state, peers served). section='nodes' (IP id, role, operator, state, tier, hops, parent, feeders, geo, ASN; filterable), 'edges' (feed links) or 'all' are paged. |
| flowscan_staking_overviewA | The /validators (Staking) page: total HYPE staked, delegator count, validator count, and every validator (~35) with name, address, commission (bps), total delegated HYPE, staker count and jailed flag (descriptions only with includeDescription). Filter by name/address, drop jailed validators, sort ascending or descending: e.g. sortBy=commission_bps, order=asc, excludeJailed=true finds the cheapest active validator. |
| flowscan_validator_stakersA | Staking page validator drill-down: one validator's summary (name, commission, total delegated, staker count, jailed) plus its delegators (stakers) as {address, amount HYPE}, largest first. |
| flowscan_staking_eventsA | Staking page validator activity: most recent delegation/undelegation events for one validator, newest first (user, amount in HYPE, isUndelegate, tx hash, time ms + ISO). |
| flowscan_revenue_hypercore_feesA | /revenue 'Daily HyperCore Revenue' (and homepage 24h panel): one row per UTC day, oldest first: nativeHypercoreFee (non-HIP-3 markets) and hip3HypercoreFee (HIP-3 markets), USDC strings, plus rangeTotals. |
| flowscan_revenue_deployer_feesA | /revenue 'Deployer Fees': HIP-3 deployer fees per UTC day, oldest first: totalFee and byDex [{dex, totalFee}] with on-chain names ('xyz', 'para', 'io', 'mkts', 'hyna', 'cash', 'flx', 'vntl', 'km', 'hyperliquid'), plus rangeTotals (overall and per DEX). |
| flowscan_revenue_priority_gasA | /revenue 'Daily Priority Gas' and 'Top Users': per UTC day, writePriority and readPriority {totalGas (HYPE), count} and, with includeTopUsers, the top 5 gas payers, plus rangeTotals. |
| flowscan_revenue_summaryA | Convenience aggregate of the /revenue page and the homepage '24h Revenue' card: sums native HyperCore fees (USDC), HIP-3 HyperCore fees (USDC), their sum totalUsdcExcludingGas, HIP-3 deployer fees (USDC, paid to deployers, not protocol revenue) and priority gas (HYPE) over the last 1, 7 and 30 complete UTC days, plus the current (partial) UTC day separately and an annualized run-rate from the trailing 7 complete days. Computed from the three /api/gossip/info series on flowscan.xyz. |
| flowscan_perp_marketsA | Homepage perp snapshot for every perp market (~330 incl. HIP-3 like 'xyz:TSLA'): long/short counts and notional, ratios, open interest, avg entry, median leverage, unique addresses, snapshotIso/snapshotAgeSeconds (refreshes every few minutes). openInterest is Flowscan's two-sided figure: long + short notional (2x the one-sided OI some UIs show). Prefer this for live OI/positioning; hip3_markets/hip3_dex give HIP-3 history, hip3_binance_comparison the Binance side. |
| flowscan_perp_positionsA | Perp snapshot drill-down: open positions in one market, largest first (address, signed size, notional, side, entry, leverage, liq price, account value, funding/all-time PnL), with snapshotIso/snapshotAgeSeconds, marketSummary (whole market, unfiltered; OI = long + short notional) and filteredSideSummary (over the filtered rows only, with |
| flowscan_address_perp_positionsA | Homepage perp snapshot address lookup: an account's open perp positions across all markets incl. HIP-3 (market, side, signed size, notional, entry, leverage, liquidation price, funding PnL, all-time PnL) from the latest snapshot (refreshes every few minutes), with totalNotional and totalPositions. Sorted by notional desc. For live margin/account state use flowscan_address_summary. |
| flowscan_address_summaryA | Overview of an /address page: role (user/vault/subAccount/agent/missing), lifetime PnL summary (PnL, win rate, trades, hold time, volume, fees, funding, days active, tradedPairs as count + first 30), live perp state (account value, notional, margin, withdrawable, positions with size/entry/leverage/liquidation/uPnL/ROE/funding, largest first, capped by positionsLimit) and non-zero spot balances. Perp state is the main DEX unless |
| flowscan_address_ordersA | Address 'Open Orders' / 'Order History'. kind='open' (default): all resting orders on every DEX (coin, side B/A, limit price, size, oid, time). 'openDetailed': main-DEX orders with trigger/TP-SL/reduce-only/type/TIF (upstream max 100, |
| flowscan_address_fillsA | Address 'Trades' tab: fills newest first, 50/page (coin, px, sz, side, direction, closed PnL, fee, hash, time + timeIso). |
| flowscan_address_ledgerA | Address 'Funding' / 'Ledger' tabs, newest first, rows with timeIso. kind='ledger' (default, 50/page, since 30 days ago): deposits, withdrawals, sends, transfers, vault/staking moves; totals.byType {count, sumUsdc, inUsdc, outUsdc}. kind='funding' (100/page, last 7 days): hourly payments; totals {netUsdc, paidUsdc, receivedUsdc, byCoin}. Totals cover ALL matched rows in coveredRange: quote them, never add rows. Pages past the 2000-row cap are followed (maxPages); if still |
| flowscan_address_stakingB | Address page 'Staking' section: totalDelegatedHype, current delegations per validator (validator address and name, commission_bps, is_jailed, amountHype, lock-up end) and the staking history (delegate/undelegate, deposits/withdrawals to staking, newest first). |
| flowscan_address_vaults_subaccountsB | Address 'Vaults' and 'Sub-accounts': equity held in each vault (vault, equity, lock-up) and sub-accounts (name, address, account value, notional, withdrawable, open positions, non-zero spot balances). |
| flowscan_address_extrasB | Smaller address-page widgets. kind: 'approvedBuilders' (builder codes the user approved with max fee), 'borrowLend' (HyperCore native borrow/lend state per token, health and health factor), 'rateLimit' (API request allowance vs cumulative volume), 'twapSliceFills' (fills generated by the user's TWAP orders). |
| flowscan_spot_stocksA | The /spot-stocks page: tokenized stocks on Hyperliquid SPOT: NVDAX, SPYX, QQQX, SKHYX, MUX, SNDKX, SPCXX, TSLAX, AAPLX, CRCLX (xStocks) and SPCXD (Dinari). Per-token price, 24h/all-time volume, holders and liquidity ARE served. section='current' (default): summary + per-token stats. 'timeseries': daily volume/holders/traders/value per token (30 days default). 'liquidity': cumulative depth within 2/5/10/25 bps in tokens and USD. 'topHolders': largest holders. |
| flowscan_weekend_weeksA | The /weekend-trading selector: tracked weekends, newest first (fridayCloseTs = week id, sundayCloseTs, ISO twins, status, avg % change, risers/fallers, market count, data availability). includeSchedule adds the next ~12 weekend/holiday sessions. |
| flowscan_weekend_pricesA | Weekend page price table: for HIP-3 TradFi perps (e.g. 'xyz:TSLA', 'xyz:GOLD'; stocks, indices, commodities, FX), the Friday-close prices, Sunday-close prices (once the weekend is over), live current prices (during an active weekend), and weekendChanges {pct, dollar} per market, plus status and price counts. |
| flowscan_weekend_positionsB | Weekend page positioning panel: per perp market (crypto and HIP-3 TradFi, ~330), long/short counts and notional at Friday close vs the latest snapshot, new/closed longs and shorts, net long/short changes, and optionally the top 5 address-level position changes per market. |
| flowscan_weekend_coin_changesA | Weekend page coin drill-down: one HIP-3 TradFi market's Friday-close -> Sunday-close move (pct and dollar) for every tracked weekend, newest first. Only DEX-prefixed TradFi markets have data; a bare symbol like 'TSLA' is resolved to 'xyz:TSLA' (crypto like 'BTC' has no weekend data). Timestamps come with ISO twins. |
| flowscan_hip4_marketsA | The /hip-4 page: HIP-4 prediction markets. section='active' (default): slim rows (outcomeId, name, marketType, asset ids, underlying/target/expiry, yesMark/noMark = implied probability, yesChange24h, volume24h, totalVolume, deployer, question) sorted by sortBy (default volume24h desc). 'settled': resolved outcomes with settleFraction and trade stats. 'questions': question groups. 'all': all three. full=true for descriptions. Candles: flowscan_hip4_outcome. |
| flowscan_hip4_outcomeA | HIP-4 page outcome drill-down: candles for the YES and NO assets of one outcome over the last N days (compact rows [openTime ms, open, high, low, close, volume, trades]), plus per-side trade stats and, for settled outcomes (settled=true), the settled outcome record. Settled outcomes typically have no candles. Only outcomeId is required (asset ids default to '#0' YES / '#1' NO). Get outcomeId from flowscan_hip4_markets. |
| flowscan_hip4_labelsA | Resolve HIP-4 outcome asset ids like '#14730' (YES) / '#14731' (NO) to readable labels such as 'Arsenal ยท Yes', as the address page does for HIP-4 spot balances. Returns {labels: {assetId: label}}. |
| flowscan_hip3_overviewA | The /hip-3 headline: HIP-3 totals (volume all-time/30d/90d, trades, traders, new users, OI), per-DEX and per-collateral market share, collateral per DEX, builder-routed share (top 3 per DEX), and dexAliases (display name -> on-chain prefix, e.g. KM=mkts, Paragon=para, Entropy=io). OI is two-sided (long + short). Prefer this for DEX-level totals and share. |
| flowscan_hip3_dailyA | HIP-3 page charts: daily values per DEX as dated rows [{date, XYZ: v, KM: v, ...}] (raw=true for positional {dates, series}). metric: volume, trades, traders, new_users, oi, oi_by_market (top markets), collateral_traders, collateral_oi. Returns the last N days (default 30); lastDayPartial flags when the last date is the current, still-accumulating UTC day. |
| flowscan_hip3_marketsA | HIP-3 market tables. Without |
| flowscan_hip3_dexA | HIP-3 per-DEX tab: collateral, total volume/trades/traders/OI, every market with all-time volume, traders and current two-sided OI (sorted by volume), and dated daily-total rows for the last N days (today flagged partial). |
| flowscan_hip3_buildersA | HIP-3 'Builders' section: share of HIP-3 volume routed via builder codes (all-time/30d/90d), per-DEX builder volume with top builders, and 800+ builders ranked by HIP-3 volume only (address, name, total/30d/90d volume, shares). |
| flowscan_hip3_binance_comparisonA | HIP-3 page Binance comparison: ~240 real-world-asset symbols (equities incl. HK/KR/CN, commodities, indices, FX, pre-market) with Binance USDT-M symbol, open interest (USD), 24h volume (USD) and last price. With |
| flowscan_builders_leaderboardA | The /builders 'Builder Arena': ~1800 builders ranked by one metric over a FIXED window (1d/7d/30d/90d/all_time): revenue, volume (USD), new_users, total_users or avg_revenue_per_user_all_time (last two all-time only). Compact rows (rank, id, name, category, value, that metric's windows, all-time revenue, users); full=true for all metrics. For arbitrary ranges like 'last 45 days' use flowscan_builder_revenue; flowscan_hip3_builders ranks by HIP-3 volume only. |
| flowscan_builders_summaryA | The /builders page headline totals: all-time builder revenue (USD), volume (USD), users and avg revenue per user, overall and per builder category (with builder counts), plus the per-builder all-time list (paged with limit/offset, default 50). |
| flowscan_builders_daily_revenueA | The /builders daily revenue chart: for each UTC day in the range, builder revenue (USD) keyed by builder id (slug like 'phantom' for well-known builders, 0x address for the rest), plus range totals per builder and the grand total. Defaults to the last 30 days ending yesterday, like the site. By default keeps the top 20 builders by range revenue. For one builder's total over a range use flowscan_builder_revenue instead. |
| flowscan_builder_lookupA | Resolve a builder name to its id/address. Names can be ambiguous (e.g. two 'fomo' builders); call this first, then pass the exact id/address to flowscan_builder_revenue or flowscan_builder_dashboard (as |
| flowscan_builder_revenueA | Total and daily revenue (USD) of ONE builder over any range ('past 45 days'): |
| flowscan_builders_user_seriesA | The /builders user-growth chart: daily count of active traders and new traders across all builders and per builder since 2025-07-27. Prefer this for daily active/new trader time series; for windowed totals use flowscan_builders_leaderboard (its new_users.7d is a separate dataset and can differ). |
| flowscan_builder_dashboardA | The /builders/{id} dashboard for one builder over a FIXED window (7d/30d/90d/all, ending yesterday UTC): stats (volume, revenue, fills, unique/new traders, volume per trader, share of Hyperliquid and builder volume, revenue run-rate), daily series (last 90 days unless |
| flowscan_builder_intelligence_listA | The /builder-intelligence index: ~120 analysed builders (id, name, category, total/active users, all-time revenue/volume USD, 7d new users) and categories. Ids feed flowscan_builder_intelligence_detail, category ids flowscan_builder_intelligence_summary. Prefer this for user-status/retention questions. Its '7d new users' comes from a different dataset than the leaderboard's and user_series'; say which you quote. |
| flowscan_builder_intelligence_detailA | A /builder-intelligence builder report: user status (active/dormant/cooling-off/switched/moved-on), revenue, cohorts, lifecycle, retention, daily activity, top users, heatmap, daily revenue. Payload is ~11 MB, so pick |
| flowscan_builder_intelligence_summaryA | The /builder-intelligence aggregate view for a category (e.g. wallet, copytrading, desktop_trading, mobile_trading) or 'overall': metadata (builders included and their weights), totals (users, active users, 7d new users, all-time revenue, fees 24h/7d/30d/90d, average daily revenue, week-1/4 retention) and user-weighted averages (key metrics, user status, revenue by status, lifecycle, retention, equity/fee cohorts). Cohort member address lists are reduced to {count, sample}. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| flowscan_guide | Rules for answering Hyperliquid questions with the flowscan_* tools (which tool fits, modes, numbers, citations). Use for any question about Hyperliquid data that flowscan.xyz shows, such as protocol revenue and fees, HYPE staking and validators, builder codes, HIP-3 perp DEXs, HIP-4 outcome markets, a specific address's positions/trades/balances, weekend trading of TradFi markets, tokenized spot stocks, perp positioning, or gossip-network peers, answered through the flowscan MCP server's tools. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| flowscan_guide | Same text as the flowscan_guide prompt (skills/flowscan/SKILL.md). |
| flowscan_coverage | Pages -> tools map, what is not served and the rules for this server's mode (strict). Same data as the flowscan_coverage tool. |
TDQS
Scored across 44 tools
Tools map to distinct pages/sections and descriptions frequently cross-reference each other (e.g. flowscan_perp_markets vs flowscan_hip3_markets, flowscan_builder_revenue vs flowscan_builders_leaderboard), which strongly reduces misselection. There is still overlap among the many HIP-3 and builder analytics tools, but explicit guidance makes boundaries mostly clear.
Names follow a predictable flowscan_ + snake_case convention with descriptive verb/noun groups. Minor inconsistency appears in singular/plural forms (flowscan_builders_leaderboard vs flowscan_builder_dashboard) and noun-only names like flowscan_coverage and flowscan_peers, but the pattern remains readable.
44 tools is very heavy for a single server, well beyond the typical 3-15 range, and many are narrow slices of individual pages or widget sections. The broad analytics scope partially explains it, but the selection burden is high and related tools could be consolidated.
The surface covers a wide range of Hyperliquid analytics: address detail, staking, revenue, HIP-3, HIP-4, builders, spot stocks, weekend data, peers and stablecoin margin. It also documents non-served areas (block/tx lookups, prices) via flowscan_coverage, leaving only minor potential gaps such as general crypto perp price history.