Binance MCP Server
The Binance MCP Server provides real-time and historical market data streaming for both spot and futures markets via WebSocket.
You can:
Stream real-time market data (trades, tickers, candlesticks, depth, mark price) for specific trading pairs
Retrieve comprehensive market data for spot and futures markets
Subscribe to multiple market data streams simultaneously for real-time updates
Fetch historical candlestick data with customizable intervals
Access futures-specific data including open interest and funding rates
Test endpoints and manage automatic reconnections with exponential backoff
Ensure type-safe message handling with comprehensive error management
Provides real-time market data streaming from Binance, supporting both spot and futures markets. Offers access to trade data, price statistics, order book information, candlestick data, mark prices, funding rates, and open interest information through various endpoints and WebSocket streams.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Binance MCP Server subscribe to BTC/USDT trade and ticker streams on spot market"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Binance MCP Server
A Model Context Protocol (MCP) server implementation for Binance market data with WebSocket support.
Features
Real-time market data streaming via WebSocket
Support for both spot and futures markets
Automatic reconnection with exponential backoff
Type-safe message handling
Comprehensive error handling
Related MCP server: Binance MCP Server
Installation
npm installUsage
Starting the Server
npm startWebSocket Stream Types
The following stream types are supported:
trade: Real-time trade dataticker: 24-hour rolling window price change statisticsbookTicker: Best bid/ask price and quantitykline: Candlestick datamarkPrice: Mark price and funding rate (futures only)fundingRate: Funding rate data (futures only)
Example Usage in Claude Desktop
// Subscribe to trade and ticker streams for BTC/USDT
await server.subscribe('BTCUSDT', 'spot', ['trade', 'ticker']);
// Handle incoming data
server.onStreamData('BTCUSDT', 'trade', (data) => {
console.log('New trade:', data);
});Development
Running Tests
npm testBuilding
npm run buildLicense
Private
Available Tools
6 toolsget_futures_funding_rateC
Get current funding rate for a futures trading pair
Inputs: symbol (required).
get_futures_open_interestC
Get current open interest for a futures trading pair
Inputs: symbol (required).
get_klinesC
Get historical candlestick data
Inputs: symbol (required), type (required), interval (required), limit.
get_market_dataC
Get comprehensive market data for a trading pair
Inputs: symbol (required), type (required).
subscribe_market_dataC
Subscribe to real-time market data updates
Inputs: symbol (required), type (required), streams (required).
test_futures_endpointsD
Test individual futures endpoints
Inputs: symbol (required).
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
Real-time crypto market data: candles, tickers, orderbooks across 13+ exchanges via MCP.
A Model Context Protocol server for Wix AI tools
Trading MCP server for AI agents, with live market data, account reads and controlled execution.
A comprehensive Model Context Protocol (MCP) server that enables AI assistants to interact with yo…
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA Model Context Protocol server that exposes Binance cryptocurrency exchange data to LLMs, allowing agents to access real-time prices, order books, and historical market data without requiring API keys.21MIT
- AlicenseBqualityBmaintenanceA Model Context Protocol server that provides Claude Code with seamless access to Binance exchange API functionality for market data retrieval, account management, and trading operations.10366 npm34MIT
- AlicenseAqualityCmaintenanceMCP server for Binance USDT-M Futures trading — exposes tools for market data, account state, order management, and position/margin control.238Apache 2.0
- AlicenseNot gradedqualityDmaintenanceAn HTTP-based Model Context Protocol server that provides tools and resources for accessing real-time cryptocurrency data from the Binance API. It enables users to fetch prices, analyze market changes, and track activity via a streamable endpoint.ISC