Skip to main content
Glama
0xArchiveIO

0xarchive-mcp

by 0xArchiveIO
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to 0xarchive-mcp

No user-submitted related servers found.

    Related Servers

    • hyperevm-mcp

      sand0vvv
      A
      license
      A
      quality
      A
      maintenance
      Read-only MCP server for the Hyperliquid / HyperEVM ecosystem - yields, protocol TVL, fees, markets, funding history, order-book depth.
      9
      23 npm
      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

    • Hyperliquid Perp Market Data

      Br0ski777
      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

    • 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
      17 npm
      44
      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
    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 111 tools

    Disambiguation3/5

    The venue prefixes (hyperliquid, hip3, hip4, lighter, spot) make many tools distinguishable, but the L2/L4 orderbook family is genuinely confusing: get_orderbook vs get_l2_orderbook and get_orderbook_history vs get_l2_orderbook_history look near-identical apart from tier/depth details. HIP-4's current-vs-history naming also diverges enough to cause misselection.

    Naming Consistency4/5

    The set follows a strong get_/web3_ + resource naming pattern, with venue prefixes applied consistently across most tool families. Minor inconsistencies like get_hip4_open_interest_current vs get_open_interest, and the ambiguous get_l2_orderbook vs get_orderbook, prevent a 5.

    Tool Count1/5

    111 tools is an extreme tool count. Even though each endpoint is individually clear, exposing every venue, data type, tier, and historical variant as a separate tool creates an overwhelming selection surface and is well outside a coherent MCP tool scope.

    Completeness4/5

    For a data-archive server, the surface is impressively broad: current and historical trades, candles, funding, open interest, liquidations, order books, order flow, freshness, and SLA coverage across multiple venues. The main gaps are minor, such as no spot OHLCV candles and no HIP-4 candles, but price/trade history tools can partially cover those workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources