Skip to main content
Glama
C0inFlips

binance-mcp-chainvector

by C0inFlips
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to binance-mcp-chainvector

No user-submitted related servers found.

    Related Servers

    • mcp-binance-futures

      cociugv
      A
      license
      Not graded
      quality
      C
      maintenance
      A Model Context Protocol (MCP) server that enables any compatible AI model to autonomously trade Binance USDT-margined perpetual futures. Includes a separate paper-trading strategy lab that requires no credentials.
      1
      MIT

    • qualto-mcp

      mystiquemide
      A
      license
      A
      quality
      B
      maintenance
      Verification-first MCP server for Binance Agent OS that enables AI agents to propose trading claims, execute orders bound to claim IDs, and attest them against live Binance order data with a strict tool allowlist and session locking.
      5
      MIT

    • binance-announcements-mcp

      kukapay
      A
      license
      B
      quality
      D
      maintenance
      An MCP server that streams the latest Binance announcements to your AI agents in real time, enabling instant analysis and action on market-moving updates.
      1
      1
      MIT

    • mcp-binance-futures

      Muvon
      A
      license
      A
      quality
      C
      maintenance
      MCP server for Binance USDT-M Futures trading — exposes tools for market data, account state, order management, and position/margin control.
      23
      6
      Apache 2.0

    • binance-mcp

      mujeeb8
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Binance market data, account insights, and Convert workflows.
      10
      7 npm
      MIT

    • Rasattrading MCP

      saldraykee22
      A
      license
      B
      quality
      B
      maintenance
      A Binance price-action and liquidity-focused MCP server for AI agents, offering 39 tools for market data, analysis, screening, alerts, and order execution with paper-first safety and optional real trading.
      39
      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

    C2.5/5.0

    Scored across 196 tools

    Disambiguation2/5

    With 196 tools, there are many overlapping and confusingly similar tools, such as BinanceWalletWithdrawHistory and its V1/V2 variants, and multiple ticker tools like BinanceTicker24hr, BinanceTicker, BinanceTickerTradingDay, BinanceTickerPrice, and BinanceTickerBookTicker. An agent would likely misselect between these without deep reading of descriptions.

    Naming Consistency2/5

    Naming is highly inconsistent: Binance tools use PascalCase with mixed verb placement (BinanceAllOrders, BinanceNewOrder, BinanceGetOrder, BinanceKlines), while ChainVector tools use camelCase (chainvectorMomentum). Also, some tools have a 'register' prefix, and one (getSolStakingQuotaDetails) has no prefix, making the pattern unpredictable.

    Tool Count1/5

    196 tools is far beyond any reasonable MCP scope, even for a combined Binance and ChainVector server. This makes the set unwieldy and likely to be split into several focused servers, as the count alone overwhelms navigation and selection.

    Completeness3/5

    The server covers a vast number of Binance wallet, market data, and algorithm order endpoints, and the ChainVector analytics suite is thorough. However, core futures trading operations are missing: there is no standard futures order placement, position retrieval, or cancel for regular futures orders, only algorithmic orders. This leaves a significant gap for a trading-focused tool set.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources