Skip to main content
Glama
johnsmithxy1mmm-sys

hypersignal

by johnsmithxy1mmm-sys
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to hypersignal

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
      32 npm
      MIT

    • perp-cli

      hypurrquant
      A
      license
      A
      quality
      C
      maintenance
      Multi-DEX perpetual futures trading MCP server (Pacifica, Hyperliquid, Lighter). 18 tools for market data, trade execution with dry-run safety, funding rate arbitrage, and portfolio analytics.
      18
      114 npm
      36
      MIT

    • cipher-x402-mcp

      cryptomotifs
      A
      license
      A
      quality
      C
      maintenance
      MCP server providing Solana/crypto/macro tools (wallet scan, password breach, Jito tip, GitHub health, FRED series, Drift exposure, premium chapters) with x402 payment gating (USDC on Base) for 7 of 8 tools.
      15
      MIT

    • Hyperliquid MCP Server

      samimiair
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Hyperliquid perpetual DEX with 48 tools for trading, monitoring, risk management, and security. Enables real-time market data, order management, risk validation, and automated trading strategies.
      -
    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.3/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: key management, market data queries (orderbook, candles, funding, account, open orders), trading actions (place, cancel, close, TWAP), admin, signal verification, and score calibration. No two tools appear to serve overlapping functions.

    Naming Consistency5/5

    All tools use the consistent pattern 'hl_' prefix followed by descriptive verb_noun or noun names in snake_case (e.g., hl_get_orderbook, hl_place_order). Minor exceptions like hl_admin_stats and hl_score_calibration are still clearly readable and follow the same prefix convention.

    Tool Count5/5

    14 tools is well-scoped for a cryptocurrency trading platform with advanced features like TWAP and builder codes. Each tool addresses a specific operational or informational need without redundancy or bloat.

    Completeness3/5

    The tool set covers core trading and data operations but has a notable gap: hl_twap_order references polling with hl_execution_status, which is not provided. This missing dependency creates a dead end for TWAP execution monitoring. Otherwise, the surface seems adequate for the stated purpose.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources