Hyperliquid MCP Server
Related Servers
Alternatives to Hyperliquid MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseAqualityFmaintenanceAn MCP server that provides real-time data and insights from the Hyperliquid perp DEX for use in bots, dashboards, and analytics.1729MIT
- AlicenseBqualityBmaintenanceMCP server for querying historical and real-time crypto market data across Hyperliquid, Hyperliquid HIP-3, and Lighter.xyz - orderbooks, trades, candles, funding, open interest, liquidations, and data quality metrics.10064 npm12MIT
- AlicenseNot gradedqualityBmaintenanceMCP server providing Hyperliquid perpetual futures market data including order books, prices, funding rates, open interest, volume, and OHLCV candles with pay-per-call micropayments via x402.MIT
- AlicenseNot gradedqualityCmaintenanceA Model Context Protocol (MCP) server for the Hyperliquid decentralized exchange, enabling AI assistants to perform trading operations, manage accounts, and retrieve market data.3MIT
- FlicenseNot gradedqualityCmaintenanceMCP server for Hyperliquid perpetual DEX with 48 tools for trading, monitoring, risk management, and security. Enables real-time market data, order management, risk validation, and automated trading strategies.-
- AlicenseNot gradedqualityCmaintenanceA read-only MCP server for Hyperliquid that provides public market data (prices, order books, funding) and any wallet's positions, orders, and fills via MCP tools, without requiring a private key.MIT
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_all_mids retrieves mid prices for all coins, get_candle_snapshot provides candlestick data for a specific token, and get_l2_book fetches the L2 order book for a token. There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with 'get_' as the prefix, followed by a descriptive noun phrase (e.g., get_all_mids, get_candle_snapshot, get_l2_book). This uniformity enhances readability and predictability across the tool set.
With only 3 tools, the server feels thin for a trading or market data domain, which typically involves more operations like placing orders, checking balances, or managing positions. While the tools are well-defined, the count is borderline low for comprehensive coverage of such a scope.
The tool set is severely incomplete for a trading platform server, as it lacks essential operations such as order placement, account information retrieval, trade execution, or portfolio management. This creates significant gaps that will likely cause agent failures in real-world trading scenarios.