Skip to main content
Glama
talkincode

HyperLiquid MCP Server

by talkincode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to HyperLiquid MCP Server

No user-submitted related servers found.

    Related Servers

    • hyperliquid-mcp

      midodimori
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server for the Hyperliquid decentralized exchange, enabling AI assistants to perform trading operations, manage accounts, and retrieve market data.
      307 PyPI
      3
      MIT

    • Hyperliquid MCP Server

      samimiair
      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.
      -

    • tdx-mcp

      845340126
      A
      license
      Not graded
      quality
      D
      maintenance
      基于通达信行情服务器的 MCP Server，为 AI 助手提供实时 A 股、期货、港股等行情数据及技术指标。
      MIT

    • Hyperliquid MCP

      erscoder
      A
      license
      A
      quality
      C
      maintenance
      Enables natural language control of Hyperliquid perpetual futures, including querying positions, prices, orderbook, and executing trades like market and limit orders, all from MCP-compatible clients.
      13
      MIT

    • Hyperliquid MCP Server

      mektigboy
      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
    • polskidegen-hl-tracker by polskidegen

      polskidegen-hl-trackerofficial

      polskidegen
      A
      license
      A
      quality
      D
      maintenance
      MCP server for Hyperliquid that provides read-only on-chain wallet analytics. Enables natural-language queries about positions, fills, funding, and realized PnL for any public address.
      8
      7 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 24 tools

    Disambiguation2/5

    Multiple tools have overlapping purposes: there are three cancel tools (cancel_all_orders, cancel_order, cancel_order_by_client_id), three TP/SL tools (set_take_profit_stop_loss, set_take_profit, set_stop_loss), and close_position vs market_close_position. While descriptions clarify the differences, the boundaries are tight enough that an agent could easily select the wrong tool, especially for closing positions or setting TP/SL.

    Naming Consistency4/5

    The vast majority of tools follow a consistent verb_noun snake_case pattern (e.g., cancel_order, get_orderbook, update_leverage). Minor deviations such as market_open_position and market_close_position insert a modifier before the verb, but the intent is still clear and the overall convention is predictable.

    Tool Count3/5

    At 24 tools, the server is on the heavy side. The broad domain justifies many tools, but the count is inflated by redundant variants (three cancel tools, three TP/SL tools, five account query tools that could be consolidated. It's not extreme, but it exceeds the ideal 3-15 range and feels heavier than necessary.

    Completeness4/5

    The tool set covers the core trading lifecycle: market data, order placement (limit, market, bracket), order modification/cancellation, position management (close, TP/SL), leverage, transfers, and account queries. Minor gaps exist such as fetching a specific order by ID or listing all available coins, but agents can work around these with the existing tools.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources