Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to nexus-exchange-mcp

No user-submitted related servers found.

    Related Servers

    • bybit-ws

      poliakarmai
      A
      license
      Not graded
      quality
      A
      maintenance
      An MCP server that enables AI agents to scan the market, manage positions, and retrieve trading metrics for Bybit through natural language commands.
      1
      AGPL 3.0

    • CryptoConduit-MCP

      chxndre
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents direct access to Polymarket Crypto prediction markets, enriched with live spot prices. Discover markets, analyze order books, paper trade strategies, track activity, and execute live trades — all through natural language.
      1
      AGPL 3.0

    • x402 MCP Server

      fernsugi
      A
      license
      Not graded
      quality
      D
      maintenance
      An MCP server that provides DeFi data tools (crypto prices, whale concentration, funding rates) for AI agents via the x402 protocol.
      8 npm
      1
      MIT

    • mcp-crypto-monitor

      AMEOBIUS-space
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that gives AI agents the ability to check crypto wallet balances, track token prices, calculate portfolio value, monitor gas prices, and track the Fear & Greed Index — all with zero external dependencies using free public APIs.
      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.2/5.0

    Scored across 115 tools

    Disambiguation1/5

    Roughly half the surface consists of deprecated aliases that duplicate a live tool one-to-one (get_balance/fetch_balance, get_orderbook/fetch_order_book, place_order/create_order, amend_order/edit_order, list_deposits/fetch_deposits, etc.), so an agent must constantly resolve 'which of these two identical tools do I call?'. On top of that, several tools are admitted dead ends that always fail (create_bridge_deposit_address, list_bridge_deposit_addresses, get_deposit_target), and get_deposit vs create_deposit vs deposit_collateral add further near-miss overlap.

    Naming Consistency2/5

    Two competing conventions coexist: the modern set uses fetch_*/create_*/edit_*/cancel_*/register_* while the deprecated set uses get_*/list_*/place_*/amend_*/adjust_*. Within each family the verb_noun pattern is readable, but mixing get_/fetch_ and place_/create_ across the same resource is exactly the inconsistency the rubric penalizes.

    Tool Count1/5

    115 tools is an extreme mismatch for any single server. Even after removing the ~45 deprecated aliases, the live surface is 60+ tools, which far exceeds a well-scoped set and forces the agent to carry a large mental model of near-duplicates.

    Completeness4/5

    Domain coverage is actually broad and strong: markets/tickers/orderbook/OHLCV/funding, full order lifecycle (create, batch, preview, edit, cancel, cancel-all), account/positions/PnL/fees/history, deposits/withdrawals/bridge, API keys, agent keys, wallets, and WS tokens. The main gap is that a few advertised bridge/deposit-target tools have no working server implementation, leaving genuine dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources