Skip to main content
Glama
sand0vvv

hyperevm-mcp

by sand0vvv
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript

Related Servers

Alternatives to hyperevm-mcp

No user-submitted related servers found.

    Related Servers

    • 0xarchive-mcp

      0xArchiveIO
      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

    • hyperliquid-mcp

      kitsune-de
      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

    • hl-read

      akagifreeez
      A
      license
      Not graded
      quality
      C
      maintenance
      A 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
    • 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

    A4.6/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct aspect of the Hyperliquid/HyperEVM ecosystem: yields, protocols, market prices, staking, wallet info, fees, funding history, and order book. There is no overlap, and descriptions clearly differentiate them.

    Naming Consistency5/5

    Tools consistently use 'hyperevm_' for EVM-related data and 'hl_' for native Hyperliquid data, followed by a clear noun describing the resource. The pattern is predictable and logical.

    Tool Count5/5

    With 8 tools, the server covers the core functionalities expected for a read-only data provider on this ecosystem. The count feels well-scoped—neither too many nor too few for the domain.

    Completeness5/5

    The tool set covers major data needs (yields, protocols, market state, staking, wallet, fees, funding history, order book) for a read-only interface. No obvious gaps for public data queries; every important area is addressed.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources