Skip to main content
Glama
karakushan

kvant-binance-mcp

by karakushan
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to kvant-binance-mcp

No user-submitted related servers found.

    Related Servers

    • 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-futures-mcp

      alexcandrabersiva
      A
      license
      Not graded
      quality
      C
      maintenance
      Comprehensive Binance Futures trading MCP server with 41 professional trading tools across account management, order execution, market data, and risk management. Features smart ticker caching, secure authentication, and Docker support for seamless integration with MCP clients.
      4
      Python
      MIT

    • binance-mcp

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

    • WhaleScope MCP

      osindo-dev
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing Binance Futures market intelligence, including funding rates, open interest, long/short ratios, order book, and volatility, with a focus on retail vs whale positioning. It offers read-only access to public data and a composite analysis tool.
      MIT

    • binance-intelligence-mcp

      mefai-dev
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 12 computed intelligence tools for Binance, including accumulation detection, whale tracking, market impact simulation, and more, using public endpoints with no API keys needed.
      6
      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.4/5.0

    Scored across 19 tools

    Disambiguation5/5

    Each tool has a distinct purpose: account info, balances, orders, leverage, margin, market data, etc. No two tools overlap significantly; even similar tools like futures_account_info and futures_balance are differentiated by scope.

    Naming Consistency5/5

    All tools follow the 'futures_<action>_<object>' snake_case pattern consistently, making it easy to infer functionality from names. Examples: futures_cancel_order, futures_change_leverage.

    Tool Count4/5

    19 tools is slightly above the ideal range for a focused server, but given the complexity of a trading API, the count is justified. Each tool covers a necessary operation without redundancy.

    Completeness4/5

    The tool set covers core futures trading operations: account management, order lifecycle, leverage/margin settings, and market data. Minor gaps like order modification or funding rate fetch exist, but the surface is sufficiently complete for standard trading workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources