binance-market-mcp-server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| PORT | No | The port to listen on when TRANSPORT=http is set. | 3000 |
| TRANSPORT | No | The transport mode: 'stdio' for local use, or 'http' for remote. Set to 'http' to enable HTTP mode. | stdio |
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": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| binance_get_current_priceA | Get the current price and 24-hour trading stats for a crypto trading pair from Binance. This tool fetches a live snapshot: last traded price, 24h price change (absolute and %), 24h high/low, and 24h volume. It does NOT return historical data — use binance_get_historical_ohlc for that. Args:
Returns: { "symbol": string, "price": number, // last traded price "price_change_24h": number, // absolute change over 24h "price_change_percent_24h": number, // % change over 24h "high_24h": number, "low_24h": number, "volume_24h_base": number, // volume in base asset (e.g. BTC) "volume_24h_quote": number, // volume in quote asset (e.g. USDT) "as_of": string // ISO 8601 timestamp of this snapshot } Examples:
Error Handling:
|
| binance_get_historical_ohlcA | Get historical OHLC (open/high/low/close) candles for a crypto trading pair from Binance, for a given date range and interval. Use this to build price series for indicator calculation (momentum, moving averages, volatility models like EGARCH) or backtesting. Automatically paginates past Binance's 1000-candle-per-request limit. Caps total candles returned at 2000 per call — if your range would exceed that, the response is truncated and "truncated": true is set; split the request into smaller date ranges if you hit this. Args:
Returns: { "symbol": string, "interval": string, "requested_start": string, "requested_end": string, "candle_count": number, "truncated": boolean, // true if more candles existed than were returned "note": string (optional), // present if truncated or range predates available data "candles": [ { "open_time": string, // ISO 8601 "open": number, "high": number, "low": number, "close": number, "volume": number, "close_time": string, // ISO 8601 "quote_volume": number, "trade_count": number } ] } Examples:
Error Handling:
|
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 2 tools
The two tools have completely distinct purposes: one retrieves historical OHLC candles, the other fetches current price and 24h stats. There is no overlap or ambiguity between them.
Both tools follow the identical binance_ verb_noun pattern (get_historical_ohlc and get_current_price), making the naming predictable and clear.
At 2 tools, the server is minimal but well-scoped for the stated market-data purpose. Each tool covers a fundamental need (current quote vs. historical series), so the count is appropriate though slightly thin.
The two tools cover the core market-data needs: live price snapshot and historical candle data. Minor gaps exist (e.g., no order book, no multi-symbol endpoint), but the surface is coherent and sufficient for many use cases.