Skip to main content
Glama
Impa-Ventures

hyperliquid-mcp

by Impa-Ventures
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to hyperliquid-mcp

No user-submitted related servers found.

    Related Servers

    • hyperliquid-mcp

      edkdev
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely trade on Hyperliquid perpetual exchange, including order placement, position management, market data retrieval, and vault operations via natural language.
      34 PyPI
      23
      MIT

    • Liquid Trading MCP Server

      garavels
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural language trading of Hyperliquid perpetual futures, including portfolio checks, market data, order placement with confirmation, and position management.
      -

    • Alpha Arena MCP

      kukapay
      A
      license
      A
      quality
      D
      maintenance
      Enables AI agents to interact with Hyperliquid perpetual futures exchange for market analysis, account management, and risk-managed trading.
      5
      1
      MIT

    • Hyperliquid MCP Server

      t3rmed
      A
      license
      A
      quality
      Not graded
      maintenance
      Enables interaction with the Hyperliquid DEX for retrieving market data, managing positions, and executing trades. Supports both testnet and mainnet operations with comprehensive trading tools including order placement, cancellation, and portfolio management.
      11
      MIT

    • Hyperliquid MCP Server

      samklein952-hub
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the Hyperliquid exchange to trade perpetuals, check positions, and manage risk through natural language. It provides tools for fetching real-time market data, tracking portfolio value, and executing orders with a focus on safety through default paper trading.
      10
      1
      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.2/5.0

    Scored across 12 tools

    Disambiguation4/5

    The tools are mostly distinct, with clear separation between spot and perp clearinghouse states, and different order-related queries (status, open, history). There is slight potential confusion between 'order' and 'get_order_status', but descriptions clarify the intended purpose.

    Naming Consistency3/5

    Most read-only tools follow the 'get_' prefix convention, but 'order', 'cancel_order', and 'transfer_spot_perp' do not, mixing bare verbs with the prefix pattern. The names are readable but not fully consistent in style.

    Tool Count5/5

    With 12 tools, the server is well-scoped for its purpose, covering account state, order lifecycle, market data, and transfers without being overwhelming. Each tool serves a clear function within the trading domain.

    Completeness4/5

    The tool set covers core trading workflows, including querying state, managing orders, and fetching market data. Minor gaps exist, such as no explicit trade history, modify order capability, or position-specific endpoints, but these are workable for most use cases.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources