Skip to main content
Glama

Server Details

Binance - 340 tools for market data, order books, and trading pairs

Status
Unhealthy
Last Tested
Transport
Streamable HTTP
URL
Repository
junct-bot/binance-mcp
GitHub Stars
0
Server Listing
Binance MCP Server

Glama MCP Gateway

Connect through Glama MCP Gateway for full control over tool access and complete visibility into every call.

MCP client
Glama
MCP server

Full call logging

Every tool call is logged with complete inputs and outputs, so you can debug issues and audit what your agents are doing.

Tool access control

Enable or disable individual tools per connector, so you decide what your agents can and cannot do.

Managed credentials

Glama handles OAuth flows, token storage, and automatic rotation, so credentials never expire on your clients.

Usage analytics

See which tools your agents call, how often, and when, so you can understand usage patterns and catch anomalies.

100% free. Your data is private.
Tool DescriptionsC

Average 3.4/5 across 340 of 340 tools scored. Lowest: 2/5.

Server CoherenceB
Disambiguation2/5

The tool set has significant overlap and ambiguity, with many tools performing similar actions on different account types (e.g., multiple delete, get, post tools for spot, margin, futures, sub-accounts). While descriptions clarify specific contexts, the sheer number and similarity make it difficult for an agent to reliably choose the correct tool without deep domain knowledge. Tools like delete_api_v3_open_orders and delete_sapi_v1_margin_open_orders are nearly identical except for the account type, leading to potential misselection.

Naming Consistency5/5

Tool names follow a highly consistent pattern throughout, using HTTP method prefixes (get, post, delete, put) followed by API path segments (e.g., api_v3, sapi_v1) and specific endpoints. This structured naming, such as get_api_v3_account and post_sapi_v1_margin_order, provides clear and predictable identifiers, making it easy to understand the tool's purpose and API route despite the large count.

Tool Count1/5

With 340 tools, the count is extremely high and overwhelming for the server's purpose of interacting with Binance's API. This exceeds typical MCP server scopes (usually 3-15 tools) and creates a heavy cognitive load. While Binance's API is extensive, exposing every endpoint as a separate tool is impractical for agent use, likely leading to confusion and inefficiency.

Completeness5/5

The tool set appears complete for the Binance API domain, covering a vast range of operations including market data, account management, trading (spot, margin, futures), sub-account functions, lending, staking, and more. It provides full CRUD and lifecycle coverage across all supported services, with no obvious gaps that would hinder agent workflows for cryptocurrency exchange interactions.

Discussions

No comments yet. Be the first to start the discussion!

Related MCP Servers

  • A
    license
    Not graded
    quality
    D
    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.
    112
    34
    MIT
  • A
    license
    Not graded
    quality
    D
    maintenance
    Provides 27 tools for interacting with the Binance Thailand (Gulf Binance) API, enabling market data, trading, order management, wallet operations, and account management through natural language.
    9
    MIT
  • -
    license
    Not graded
    quality
    D
    maintenance
    Enables users to fetch real-time cryptocurrency market data from Binance including OHLCV prices, mark prices, funding rates, and open interest for both spot and futures markets. Provides easy access to Binance trading data through a simple JSON-RPC interface.

View all MCP Servers

Try in Browser

Your Connectors

Sign in to create a connector for this server.