Skip to main content
Glama
alekskram

dydx-agent-gateway

by alekskram
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to dydx-agent-gateway

No user-submitted related servers found.

    Related Servers

    • 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

    • markettrace-agent-feed

      MarketTrace
      A
      license
      Not graded
      quality
      B
      maintenance
      Read-only crypto perps microstructure for AI agents: normalized cross-exchange market state (funding + multi-year percentile, OI, volume, CVD, order-book imbalance, liquidations, basis), OHLCV, 15-min state history, and measured conditional outcomes (historical base rates, not predictions) — 6 assets across Binance, Bybit, OKX and Hyperliquid, every metric with self-declared coverage and freshness
      MIT

    • Crypto Options Desk MCP

      dasein108
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that gives an LLM agent a typed, audited tool surface over quant crypto-options desk analytics: gamma exposure, vanna, skew, vol surface, options flow, technicals, portfolio greeks, scenario analysis, and live positions.
      22
      2
      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/5.0

    Scored across 22 tools

    Disambiguation4/5

    Most tools target distinct data categories—market stats, candles, trades, funding, trader PnL, fills, alerts, and health—so an agent can usually pick the right one. A few pairs like trader_profile vs trader_pnl_stats and list_markets vs market_detail could be initially confused, but the detailed descriptions largely prevent misselection.

    Naming Consistency4/5

    All tool names use lowercase snake_case and are readable, with helpful prefixes like market_, trader_, and list_. However, the set mixes verb-led names such as suggest_stops and discover_traders with noun-style names like candles, height, and cvd, so no single naming pattern is maintained.

    Tool Count3/5

    At 22 tools, the server is borderline heavy and spans several subdomains—market data, trader analytics, alerts, registry health, and usage stats. Each tool seems purposeful, but the number is enough that an agent must scan many options before selecting.

    Completeness4/5

    The tool surface covers market data, funding, technical analysis, trader discovery, PnL, fills, alerts, and system health, which is strong for a read-only analytics gateway. Minor gaps like order-book depth and historical per-market PnL or positions exist, but they do not block core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources