Skip to main content
Glama
nexus-xyz

nexus-exchange-mcp

Official
by nexus-xyz

Related Servers

Alternatives to nexus-exchange-mcp

No user-submitted related servers found.

    Related Servers

    • 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
    • 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
    • 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.
      5 npm
      1
      MIT
    • 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

    TDQS

    B3.4/5.0

    Scored across 66 tools

    Disambiguation2/5

    Several tool clusters have blurred boundaries: get_balance, get_account_summary, and get_account_state all return overlapping account/position snapshots, while get_ticker, get_tickers, get_mark_price, and list_markets cover similar market data. The long descriptions help, but an agent must read carefully to avoid selecting a near-duplicate tool.

    Naming Consistency3/5

    The toolset is consistently snake_case and mostly readable, but it arbitrarily mixes get_ and list_ prefixes: get_withdrawals vs list_deposits, get_tickers vs list_markets, and get_order vs get_order_history. Action verbs also vary among get_, list_, place_, create_, register_, and set_ without a strong unifying pattern.

    Tool Count1/5

    66 tools is an extreme surface size and well beyond the well-scoped 3-15 tool range. Many getters could be consolidated: account snapshots, market data views, demo account tools, and history endpoints all have redundant variants that make the server feel bloated.

    Completeness3/5

    Market data, order placement/cancellation/amendment, account state, bridge deposits, and API key management are well covered. However, there is no create-withdrawal tool despite get_withdrawals and bridge wallet registration, and get_deposit_target is explicitly unbuilt server-side, leaving some workflow dead ends.

    Maintenance

    ActivityActive
    ResponsivenessNo issues