Binance MCP Server
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
| Name | Description |
|---|---|
| get_market_dataC | Get comprehensive market data for a trading pair |
| test_futures_endpointsD | Test individual futures endpoints |
| get_futures_open_interestC | Get current open interest for a futures trading pair |
| get_futures_funding_rateC | Get current funding rate for a futures trading pair |
| get_klinesC | Get historical candlestick data |
| subscribe_market_dataC | Subscribe to real-time market data updates |
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 6 tools
Most tools have distinct purposes, with clear separation between historical data (get_klines), current data (get_market_data, get_futures_funding_rate, get_futures_open_interest), real-time updates (subscribe_market_data), and testing (test_futures_endpoints). However, get_market_data might overlap with the more specific futures tools in scope, causing minor ambiguity.
All tool names follow a consistent verb_noun pattern using snake_case, such as get_futures_funding_rate, subscribe_market_data, and test_futures_endpoints. This predictability makes it easy for agents to understand and use the tools without confusion.
With 6 tools, the count is reasonable for a Binance market data server, covering key areas like historical and real-time data, futures metrics, and testing. It's slightly lean but functional, as it could benefit from more tools for broader market coverage (e.g., spot trading or account management).
The tools provide good coverage for market data retrieval and futures-specific metrics, but there are notable gaps. For a Binance server, missing operations like placing trades, managing orders, or accessing account information limit its completeness, as agents cannot perform full trading workflows.