Skip to main content
Glama
kydlikebtc

binance-mcp-server

by kydlikebtc
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to binance-mcp-server

No user-submitted related servers found.

    Related Servers

    • 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

    • 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.
      87 npm
      37
      MIT

    • Trading MCP Server

      TigranPetosyants
      A
      license
      B
      quality
      D
      maintenance
      Provides a comprehensive suite of 20 tools for cryptocurrency trading and technical analysis across 100+ exchanges like Binance and MEXC via CCXT. It enables users to execute orders, track positions, and scan for market opportunities through Claude Desktop using natural language.
      20
      20 npm
      MIT

    • 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.
      87 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.7/5.0

    Scored across 35 tools

    Disambiguation4/5

    Most tools are clearly differentiated by asset class (spot vs futures) and action (place, cancel, open orders, history). However, binance_account_info, binance_account_status, and binance_server_time have overlapping diagnostic purposes, and binance_portfolio_account vs binance_analyze_portfolio_risk could be confused. Descriptions help clarify, but a couple of boundaries are fuzzy.

    Naming Consistency4/5

    The naming pattern is largely consistent with binance_<spot|futures>_<action>_<target> (e.g., binance_spot_place_order, binance_futures_cancel_order). Minor deviations exist: binance_get_optimal_trade_size uses 'get_' while others use 'calculate_' (e.g., binance_calculate_position_size), and some tools like binance_server_time, binance_exchange_info, and binance_account_info omit the market segment. Overall, the style is still predictable and readable.

    Tool Count2/5

    With 35 tools, the server is significantly over-built. Many spot and futures operations are exact duplicates (place/cancel/open_orders/order_history/trade_history/cancel_all_orders), which could be consolidated into parameterized tools. The count exceeds the 'heavy' threshold of 25 and would likely overwhelm agents trying to select the right tool.

    Completeness4/5

    Core trading workflows are well covered: account info, balances, positions, orders, prices, klines, tickers, orderbook, and risk calculators. Minor gaps exist—such as lack of deposit/withdrawal management, funding rate history, or order modification (cancel+replace)—but these are workarounds. The domain is fully addressable for typical trading operations.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources