flowscan-mcp
Related Servers
Alternatives to flowscan-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI assistants to retrieve live Hyperliquid data on wallets, trades, top traders, markets, liquidations, builders, and prediction markets through read-only natural-language tools.1993 npmMIT
- AlicenseAqualityBmaintenanceProvides AI agents read-only, keyless access to Hyperliquid market data, funding rates, account risk, and HyperEVM token transfers through MCP tools, with caching and rate limiting to protect upstream APIs.1285 PyPI1MIT
- AlicenseCqualityDmaintenanceA read-only Model Context Protocol server for Hyperliquid that exposes over 30 tools to query public market data and user state via the Hyperliquid Info API, without requiring a private key.41MIT
- AlicenseAqualityDmaintenanceEnables AI agents to interact with Hyperliquid perpetual futures exchange for market analysis, account management, and risk-managed trading.51MIT
- AlicenseNot gradedqualityDmaintenanceProvides live cryptocurrency prices, price history, and symbol listing tools for AI agents via the Hyperliquid API.68 PyPI1MIT
- AlicenseAqualityCmaintenanceRead-only Hyperliquid and cross-exchange market research for AI agents, providing structured tools for live market data without requiring authentication.981 npmMIT
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.