Skip to main content
Glama
alekskram

hyperliquid-agent-gateway

Related Servers

Alternatives to hyperliquid-agent-gateway

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Hyperliquid's public market, user, vault, and staking data via 61 MCP tools, covering perpetuals, spot, and borrow-lend information.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to read live Hyperliquid market data — perp and spot metadata, mid prices, order books, OHLCV candles, funding rates and history, and current open interest — keylessly from the exchange's public info API, with no wallet or trading access.
      212 npm
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables read-only access to Hyperdash market intelligence for Hyperliquid, including per-asset price changes, trader performance and positions, liquidations, open interest, news, and TWAP orders via 28 MCP tools.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Read-only Hyperliquid and cross-exchange market research for AI agents, providing structured tools for live market data without requiring authentication.
      9
      38 npm
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      A read-only Model Context Protocol server for Hyperliquid that exposes over 30 tools to query public market data and user state via the Hyperliquid Info API, without requiring a private key.
      41
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      An MCP server that lets AI agents read Hyperliquid perpetual futures market data and their own account state, then place and cancel orders, adjust leverage, move USDC from spot to perp, and convert stablecoins to USDC. It holds no credentials and never contacts the exchange, routing every request through a runtime that enforces caps and signs server-side.
      9
      Apache 2.0

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool targets a distinct data category or resource: market data, funding analytics, account risk, wallet balances, and transfers all have clear owners. Even the two funding-related tools differ obviously by single-coin history versus cross-perp screening.

    Naming Consistency5/5

    All tool names are lowercase snake_case noun phrases that directly describe their output, such as funding_carry_screener, market_overview, and token_transfers. There are no mixed conventions or vague generic verbs.

    Tool Count5/5

    12 tools is well-scoped for a Hyperliquid data/risk gateway. Each tool earns its place by covering a distinct part of the domain without redundancy.

    Completeness4/5

    The read-side surface is nearly complete for an analytics-focused gateway: market data, account risk, funding, wallet balances, and transfer events are all covered. Minor gaps include no direct open-orders view and no native ETH transfer history, but these are workable and order execution appears outside the server's apparent scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues