Skip to main content
Glama

Server Details

Crypto trading for autonomous AI agents on Hyperliquid testnet: market data, orders, leaderboard

The last two health checks of this connector failed. If this server requires authentication, missing or expired test credentials may be the cause. A test profile lets Glama authenticate for health checks and discover tools; it is separate from your personal connections.

If you are the author, claim ownership, then add or update a test profile under Admin → Test Profile.

Status
Unhealthy
Uptime
0.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP
URL
ChatGPT
–
Claude
–

TDQS

A3.7/5.0

Scored across 19 tools

Disambiguation4/5

Each tool targets a distinct resource or action: market data tools (get_price, get_markets, get_market_stats, get_orderbook, get_candles, get_indicators, get_recent_trades) each cover a different data shape, and account/order tools separate cleanly. The main wrinkle is the two-step prepare_order/ prepare_position_tpsl vs submit_signed_order flow, plus cancel_order referencing 'place_order' and prepare_position_tpsl referencing 'set_position_tpsl'—tools that aren't in the set—which could mislead an agent.

Naming Consistency4/5

Names are consistently snake_case verb_noun or get_noun across the set (get_*, prepare_*, submit_signed_order, cancel_order, create_preview_link). Minor deviations exist—submit_signed_order and prepare_position_tpsl are slightly irregular—but a clear, predictable pattern holds throughout.

Tool Count4/5

19 tools is on the heavier side but justified by a broad trading domain (market data, account, positions, order lifecycle, performance, leaderboard, signing). Seven market-data tools is a lot, but each serves a distinct analytical need rather than duplicating.

Completeness3/5

Core lifecycle is covered: account/positions/orders reads, an order placement path (prepare + submit), cancellation, TPSL prep, plus performance and leaderboard. However, descriptions reference place_order and set_position_tpsl which are absent from the surface, and there's no direct place/set-TPSL path for local-signing agents, leaving noticeable dead ends.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Perpetual futures trading API for AI agents. Access 275+ markets (crypto, stocks, commodities, forex) via Hyperliquid. Copy trading, leaderboard, up to 50x leverage. No KYC. 20% referral commissions.
      46 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to perform cryptocurrency trading analysis and execution with 38+ tools including real-time market data, technical indicators, risk management, and support for both paper trading and live execution on Hyperliquid.
      7
      MIT
    • 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.
      23 PyPI
      24
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Real-time crypto intelligence for AI agents. Technical analysis, liquidation heatmaps, sentiment, and funding rates for 50+ Hyperliquid perpetuals via x402 micropayments.
      15
      33 PyPI
      1
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources