Binance Cryptocurrency MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Server capabilities have not been inspected yet.
Tools
Functions exposed to the LLM to take actions
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 12 tools
Most tools have clearly distinct purposes focused on different market data aspects (e.g., ticker data, trades, order book, price, klines). However, some potential overlap exists between get_24hr_ticker, get_rolling_window_ticker, and get_trading_day_ticker, which could cause confusion about which specific ticker data is needed.
All tools follow a consistent verb_noun pattern with 'get_' prefix followed by descriptive snake_case nouns. The naming is highly predictable and uniform throughout the entire tool set.
12 tools is reasonable for a cryptocurrency exchange data server, providing comprehensive market data coverage. It's slightly on the higher side but well-justified for the domain, though some consolidation might be possible (e.g., multiple ticker tools).
The tool set covers extensive market data retrieval (tickers, trades, order book, price, klines) but lacks trading operations (create/cancel orders, account management) and other exchange functionalities. This creates a significant gap for agents needing to perform actual trading actions beyond data observation.