Skip to main content
Glama
Sign In
@mutexa/mcp

@mutexa/mcp

Official
by mutexa-labs
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to @mutexa/mcp

No user-submitted related servers found.

    Related Servers

    • hyperevm-mcp

      sand0vvv
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for the Hyperliquid / HyperEVM ecosystem - yields, protocol TVL, fees, markets, funding history, order-book depth.
      9
      83 npm
      MIT

    • Hyperliquid MCP Updated

      lucaluca-04
      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

    • hypernatt-terminal

      hypernatt
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing a forced-order/liquidation map for AI agents, with tools to fetch liquidation radar and manifest, enabling market structure analysis without custody.
      MIT

    • hyperliquid-mcp

      kitsune-de
      A
      license
      A
      quality
      D
      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
      56 npm
      2
      MIT

    • DeFi Quant Multi-Protocol

      Pyrochem
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents and quantitative traders to query block-accurate DeFi telemetry across Morpho Blue, Ethena, Fluid, Sky, Euler V2, and Pendle V2, including stablecoin carry/arbitrage radar and pre-trade risk simulation. It provides atomic Multicall3 reads, post-trade utilization and APY slippage checks, cap headroom decoding, and Pendle TWAP/logit-curve analysis through REST and MCP-compatible endpoints.
      7
      1,298 npm
      1
      MIT
    • polskidegen-hl-tracker

      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
      8 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

    A3.8/5.0

    Scored across 9 tools

    Disambiguation4/5

    Most tools target clearly different objects: market data, a single liquidation price, a perp ladder plan, a loan ladder plan, reserve parameters, an aggregate liquidation map, and a linkability heuristic. The one real overlap is hl_positions versus tracker_view, which both return the same open positions of an address; the descriptions differentiate them (tracker-style sorting, alert flags and re-planning), but an agent could easily pick the wrong one. plan_ladder and liq_price are also adjacent, though one computes a single price and the other a slice band.

    Naming Consistency3/5

    All names are snake_case, which is good, but the convention is mixed: two domain-prefixed tokens (hl_markets, hl_positions), several noun phrases (aave_reserves, liquidation_map, linkability_score), a verb_noun pair (plan_ladder, plan_loans), and an ambiguous hybrid (tracker_view). The hl_ prefix implies a Hyperliquid namespace that was abandoned for every other Hyperliquid tool. Readable, but not a predictable pattern.

    Tool Count5/5

    Nine tools is well within the sweet spot, and each one covers a distinct piece of the workflow (market data, position inspection, liquidation pricing, two planning tools, reserve data, a linkability score, and a market-wide liquidation map). No tool appears to be a redundant variant or wrapper of another.

    Completeness3/5

    The Hyperliquid side is fairly complete for research and planning, and Aave reserves plus offline loan planning are covered. However, there is no way to read an existing Aave position or health factor by address (liq_price's loan mode requires manual inputs), and the planner tools are one-shot with no way to monitor or re-evaluate a ladder after slices are placed. Execution and account/balance data are entirely absent, so every workflow ends in manual work.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources