binance-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| BINANCE_MCP_BASE_URL | No | Base URL for the Binance API. Can be set to "testnet.binance.vision" for testnet. | |
| BINANCE_MCP_LOG_LEVEL | No | Log level for the server, e.g. "INFO". | |
| BINANCE_MCP_WEIGHT_LIMIT | No | Local request-weight budget limit per minute. Default is "6000". Lower it below 6000 if the IP is shared. | |
| BINANCE_MCP_MARKET_TTL_SECONDS | No | Time-to-live for market data cache in seconds. Default is "2". |
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
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_tickerA | Current price and 24 hour rolling statistics for one symbol: last, open, high, low, best bid and ask, volume in both assets, and trade count. |
| get_klinesA | Historical OHLCV candles for one symbol, oldest first, up to 500 per call. Rows are positional; the 'columns' field names them. |
| get_order_bookA | Current order book snapshot for one symbol, up to 100 levels per side. A snapshot, not a stream: it is stale the moment it is returned. |
| get_symbol_infoA | Trading rules for one symbol: status, base and quote assets, precisions, tick size, lot step size and minimum notional. |
| search_symbolsA | Find symbols by partial name or asset code. Use this to resolve a vague pair such as 'sol usd' into an exact symbol before calling other tools. |
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 5 tools
Each tool targets a clearly distinct data surface: current statistics, historical candles, order book depth, symbol metadata, and symbol resolution. There is no meaningful overlap or ambiguity between them.
All tools follow a consistent get_ or search_ pattern with clear resource nouns: get_ticker, get_klines, get_order_book, get_symbol_info, search_symbols. No mixed conventions or vague verbs.
Five tools is well-scoped for a read-only Binance market data server. Each tool provides a distinct, necessary capability without unnecessary bloat or thinness.
The tool surface covers the core public market data needs: symbol discovery, trading rules, current pricing, historical candles, and order book depth. There are no obvious gaps for the apparent read-only market data scope.