Skip to main content
Glama
kukapay

hyperliquid-info-mcp

by kukapay

Related Servers

Alternatives to hyperliquid-info-mcp

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      C
      maintenance
      MCP 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.
      -
    • A
      license
      B
      quality
      F
      maintenance
      An MCP server implementation that integrates with Hyperliquid exchange, providing access to crypto market data including mid prices, historical candles, and L2 order books.
      3
      11 npm
      44
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      MCP 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.
      100
      64 npm
      12
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      MCP 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
    • A
      license
      A
      quality
      B
      maintenance
      A read-only MCP server for querying Hyperliquid perp markets, funding rates, order books, candles, and account positions/fills/funding for any address, without needing API keys or wallets.
      8
      30 npm
      1
      MIT

    TDQS

    A3.8/5.0

    Scored across 17 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes targeting specific data types (market data, user data, metadata), but there is some overlap between get_perp_dexs and get_perp_metadata which both retrieve perpetual market metadata. The descriptions help differentiate them slightly (one mentions 'decentralized exchange' context), but an agent might still be confused about which to use for general perpetual metadata queries.

    Naming Consistency5/5

    All 17 tools follow a consistent 'get_' prefix with snake_case naming, creating a predictable verb_noun pattern (e.g., get_user_state, get_l2_snapshot). The naming convention is uniform throughout, making it easy to understand the tool's purpose at a glance.

    Tool Count4/5

    With 17 tools, the count is slightly high but reasonable for a comprehensive cryptocurrency exchange data server. The tools cover market data, user data, and metadata across multiple domains (spot, perpetuals, staking), so most tools earn their place, though some consolidation might improve efficiency.

    Completeness4/5

    The toolset provides excellent read-only coverage for market data (prices, candles, order books, funding) and user account information (orders, trades, state, staking, fees). The main gap is the lack of write/action tools (e.g., place_order, cancel_order), but as an 'info' server this is understandable and agents can work around it by knowing this is a query-only interface.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive