Skip to main content
Glama
trustxai

amazing-binance-mcp

by trustxai
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to amazing-binance-mcp

No user-submitted related servers found.

    Related Servers

    • Binance MCP Server

      kevinwang930
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to interact directly with the Binance cryptocurrency exchange for trading, portfolio management, market analysis, and strategy automation via natural language.
      62 npm
      MIT

    • Binance MCP Server

      Lubodi-Code
      A
      license
      A
      quality
      D
      maintenance
      Enables Claude to query Binance Spot market data, account balances, and execute trades via natural language, with withdrawals disabled by default for security.
      11
      MIT

    • SignalDesk

      evggheni
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to generate market briefings, prepare confirm-before-trade Spot orders, and verify fills within Binance Agent OS, with a dry-run simulator for testing without live funds.
      -

    • Binance MCP Server

      shanrichard
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI agents to perform cryptocurrency trading operations on Binance exchange through 30 comprehensive tools supporting spot trading, futures contracts, options, account management, market data analysis, and risk control features. Provides enterprise-grade security with local encrypted API key storage and supports multiple account types with sandbox environment testing.
      9
      MIT

    • Binance MCP Server

      nirholas
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides over 156 tools to interact with the Binance.com global exchange API for spot trading, wallet management, and staking operations. It enables users to execute orders, retrieve market data, and manage crypto assets through natural language interfaces like Claude and ChatGPT.
      62 npm
      37
      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.6/5.0

    Scored across 83 tools

    Disambiguation5/5

    Each of the 83 tools targets a distinct resource+action pairing (e.g., ticker_price vs book_ticker vs ticker_24h vs rolling_ticker vs trading_day_ticker), and the genuinely confusable clusters are separated by explicit cross-references. The 'When NOT to Use' sections consistently name the alternative tool, so an agent can reliably disambiguate even dense groups like the six account-status/wallet tools or the deposit_history/all_deposits pair.

    Naming Consistency5/5

    Every tool follows the uniform binance_<verb>_<noun> snake_case convention: binance_get_* for all reads, binance_place_*/binance_cancel_*/binance_accept_* for mutations, with compound verbs like cancel_replace and convert_dust_to_bnb. The only deviations (health_check vs check_health, all_my_trades vs my_trades) are negligible and do not break the pattern.

    Tool Count2/5

    83 tools is far beyond the 25+ threshold for an overloaded surface, even though the scope (the full Binance spot API) is genuinely broad and every tool maps to a distinct endpoint. The volume will strain agent context windows and slow tool selection; this surface would be easier to navigate split into market-data, trading, and wallet/capital servers.

    Completeness5/5

    The surface covers market data, the full spot order lifecycle (test/place/cancel/replace/cancel-all), all three order-list types, convert with quote-accept-limit lifecycle, TWAP algo orders, fiat/pay/earn, wallets, transfers, dust, and capital history — each with single-window and budgeted-walk variants. Every mutation has a documented verification path for UNKNOWN states, and the only omissions (withdrawal creation, futures/margin) are deliberate, explicitly stated design boundaries.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources