No user-submitted related servers found.
Scored across 103 tools
Many tools are thematically distinct (e.g., hip4_* vs builder_*), but there is significant overlap among cohort-related tools (e.g., pulse_cohort_positions vs pulse_cohort_recent_positions, pulse_cohort_trades vs pulse_cohort_recent_trades) and market/OI tools (market_historical_oi vs live_oi_history vs live_official_oi). While descriptions are detailed, an agent may struggle to pick the optimal tool for a given cohort or OI query.
Names generally follow a domain prefix pattern (hip4_, pulse_, live_, market_, builder_, trader_), with verb_noun structure (e.g., list_markets, pulse_global_stats). Some inconsistencies exist: list_asset vs list_assets, market_price vs pulse_* style, and redundant 'live_' vs 'market_' prefixes for overlapping OI history tools. Overall consistent but not perfect.
With 103 tools, this is far beyond typical well-scoped server sizes (3-15). While the server covers a broad analytics domain, the massive count reflects significant feature creep and redundancy (e.g., multiple cohort variants, multiple OI history tools, deprecated aliases). It is overwhelming for agents and likely to hurt selection accuracy.
The tool surface is extremely comprehensive for Hyperliquid analytics, covering trader profiling, cohorts, liquidations, risk, builder analytics, and prediction markets. Minor gaps include lack of direct trade placement or order management, but as a read-only analytics server, core data access is well covered. Deprecated aliases are clearly flagged, and most lifecycles are addressed.