Binance MCP. Pull real-time crypto data, from order books to 1-month candles.
Gemini Works with every AI agent you already use
…and any MCP-compatible client
Just plug in your AI agents and start using Vinkius.
Binance MCP Server gives your AI client direct access to real-time crypto market data. Get current prices, 24h stats, and full order books from Binance without needing an API key for public data.
It gives you the OHLCV data needed for technical analysis, from minute candles up to one month. It’s your one stop for market depth and trade history.
What your AI agents can do
Get 24h ticker
Gets the last price, 24h change (price and %), high/low, volume, trade count, and open interest for a market overview.
Get agg trades
Returns compressed trade data, which is more efficient than individual trades for high-volume pairs, up to 1000 records.
Get exchange info
Retrieves all available trading pairs, their status, and the exchange's rules and filters.
Retrieves the latest price for one or all trading pairs using get_ticker_price.
Fetches the current order book, showing buy bids and sell asks up to 5,000 levels using get_order_book.
Gets OHLCV chart data for a pair across 15 time intervals, from 1 minute to 1 month, using get_klines.
Pulls 24-hour rolling statistics—including high/low, volume, and percentage change—with get_24h_ticker.
Accesses the latest market activity by fetching individual or compressed trade records using get_trades or get_agg_trades.
Lists all available trading pairs and the exchange's current rules using get_exchange_info.
Ask AI about this MCP
Supported MCP Clients
Gemini Waiting for input…
Binance MCP Server: 8 Tools for Market Data Analysis
Use these 8 tools to pull every type of crypto market data: live prices, order book depth, 24h stats, and historical candles.
019d841eget 24h ticker
Gets the last price, 24h change (price and %), high/low, volume, trade count, and open interest for a market overview.
019d841eget agg trades
Returns compressed trade data, which is more efficient than individual trades for high-volume pairs, up to 1000 records.
019d841eget exchange info
Retrieves all available trading pairs, their status, and the exchange's rules and filters.
019d841eget klines
Pulls candlestick (OHLCV) chart data for a pair across 15 timeframes (1m to 1M) for technical analysis.
019d841eget order book
Gets the current buy bids and sell asks for a pair, allowing analysis of market depth up to 5,000 levels.
019d841eget server time
Returns the current Binance server time in Unix timestamp format, useful for syncing system clocks.
019d841eget ticker price
Gets the latest price for a trading pair or all pairs, serving as the fastest way to check current market prices.
019d841eget trades
Retrieves the latest individual trade records for a pair, useful for analyzing specific market movements.
Choose How to Get Started
Build a custom MCP for your own tools, or connect a ready-made integration from our catalog.
Build Your Own
Turn any API into an MCP. Import a spec, define Agent Skills, or deploy with MCPFusion.
- Import from OpenAPI, Swagger, or YAML specs
- Create Agent Skills with progressive disclosure
- Deploy to edge with MCPFusion framework
- Built in DLP, auth, and compliance on every call
- Real time usage dashboard and cost metering
- Publish to catalog or keep private
Make Your AI Do More
Start with Binance, then connect any of our 4,700+ other servers whenever your AI needs more. One click, no limits.
- Use this MCP plus 4,700+ others, all in one place
- Add new capabilities to your AI anytime you want
- Every connection is secured and compliant automatically
- Track usage and costs across all your servers
- Works with Claude, ChatGPT, Cursor, and more
- New servers added to the catalog every week
What you can do with this MCP connector
You're hooking up your AI client directly to Binance's live crypto feed. You get current prices, 24-hour stats, and full order books without needing an API key for public data. It’s your go-to source for market depth and OHLCV data, ranging from minute candles up to a whole month.
get_ticker_price lets you check the latest price for any pair, or all pairs, fast. get_order_book pulls the current buy bids and sell asks for a pair, letting you analyze market depth up to 5,000 levels. get_klines gives you candlestick (OHLCV) chart data for a pair across 15 time intervals, from 1 minute to 1 month. get_24h_ticker pulls 24-hour stats, including the high/low, volume, and percentage change.
You can access the latest market activity by fetching individual trades with get_trades or using get_agg_trades for compressed trade records. get_exchange_info lists every available trading pair and the exchange's rules. get_server_time just spits out the current Binance server time in a Unix timestamp, useful for syncing your clock.
How Binance MCP Works
- 1 Your AI client sends a request specifying the data needed (e.g., 'What was the price range yesterday?').
- 2 The Binance MCP Server translates that request into a specific tool call (e.g.,
get_klines) and executes it against the live exchange feed. - 3 The server returns a clean, structured data object to your client, which can then be analyzed or plotted.
The bottom line is, you talk to your agent, and the server handles the complex data retrieval from Binance, giving you structured results.
Who Is Binance MCP For?
Quant analysts, algorithmic traders, and financial developers need this. If your job involves anything more complex than just looking at a dashboard, you need this. It eliminates the need to manually switch between different data sources—you just ask your agent.
Uses get_klines to pull OHLCV data across multiple timeframes, then feeds that data into a modeling script to test trading hypotheses.
Monitors the spread and depth using get_order_book to spot immediate liquidity imbalances before placing trade logic.
Builds backtesting dashboards by calling get_24h_ticker and get_trades to populate metrics and verify market activity feeds.
What Changes When You Connect
- Get the current price instantly. Use
get_ticker_priceto check the latest price for any pair without running complex queries. It’s the fastest way to get a snapshot. - Map market depth quickly.
get_order_booklets you see the best bids and asks and analyze the spread across up to 5,000 levels. You can immediately gauge liquidity. - Backtest easily.
get_klinesprovides OHLCV data for 15 different timeframes. You can pull 1-minute candles or 1-month bars to build any kind of chart. - Understand market health.
get_24h_tickergives you the quick summary: 24h high/low, volume, and percentage change. It’s perfect for a quick market overview. - Review trade flow. Need to see what just happened? Use
get_tradesto pull the individual records of recent trades, orget_agg_tradesfor a bulk, more efficient dump of activity.
Real-World Use Cases
Analyzing a potential trade entry point
The agent needs to know if ETH is ripe for a short. It first calls get_order_book to check the spread and depth. Then, it calls get_ticker_price to confirm the current price. Finally, it uses get_klines to get the 4-hour candlestick data to confirm the current trend. The full sequence gives a high-conviction signal.
Building a comprehensive market dashboard
A developer needs to populate a dashboard with 24h stats, current prices, and historical trends. They first run get_24h_ticker for the summary, then get_ticker_price for the live widget, and finally get_klines to populate the chart component. The process is structured and reliable.
Investigating unusual trading activity
A quant suspects manipulation. They use get_trades to grab the last 500 individual trades, then run get_agg_trades to check the volume distribution. They use get_exchange_info to verify if the pair they are looking at is even tradable. This gives a deep dive into the mechanics.
Verifying data integrity for a system launch
The dev team needs to ensure all pairs are accounted for. They call get_exchange_info to get the list of all symbols. Then, they loop through the list, calling get_ticker_price for every symbol to ensure the feed is alive and the data structure is correct before launch.
The Tradeoffs
Only using `get_exchange_info`
The user assumes get_exchange_info contains the current price or order book depth. They call it, get a list of symbols, and then wait for the price data to magically appear in the result set.
→
Use get_exchange_info only to list symbols. For current prices, always use get_ticker_price. For depth, use get_order_book. Never expect the current price from the info endpoint.
Fetching all data sequentially
The user calls get_klines for BTC/USDT, then waits, then calls get_order_book for BTC/USDT, then waits, then calls get_24h_ticker for BTC/USDT. This creates unnecessary latency and forces the agent to wait for three separate API round trips.
→ Don't wait for three separate calls. Design your prompt to ask for a 'Market overview of BTC/USDT'. Your agent should then understand it needs the inputs from all three tools and structure the final output logically.
Ignoring timeframes
The user asks for 'the recent price action' and only runs get_ticker_price. They get a single number, which gives zero historical context or depth, making the data useless for analysis.
→
If you need history, use get_klines and specify the timeframe (e.g., 'last 30 days, 4-hour interval'). If you need depth, use get_order_book. Never confuse a single snapshot with a full picture.
When It Fits, When It Doesn't
Use this if your task requires deep, multi-faceted market data: analyzing price action, market depth, and historical trends simultaneously. If you need to backtest a strategy, you need the combination of get_klines (for history) and get_order_book (for depth).
Don't use this if you just need a single, simple status check. If you only need to know the current price, get_ticker_price is faster. If you only need a list of pairs, get_exchange_info is enough. Don't try to use the server for everything; use the right tool for the job.
Independent Platform Disclaimer: Vinkius is an independent platform and is not affiliated with, endorsed by, sponsored by, verified by, or otherwise authorized by Binance. All third-party trademarks, logos, and brand names are the property of their respective owners. Their use on this website is strictly for informational purposes to identify service compatibility and interoperability.
VINKIUS INFRASTRUCTURE
Cloud Hosted
Managed infra
V8 Isolated
Sandboxed per request
Zero-Trust Proxy
No stored credentials
DLP Enforced
Policy on every call
GDPR Compliant
EU data residency
Token Compression
~60% cost reduction
Works with Claude, ChatGPT, Cursor, and more
The Model Context Protocol standardizes how applications expose capabilities to LLMs. Instead of operating in isolation, your AI gains direct access to external platforms, live data, and real-world actions through secure, standardized connections.
This server provides 8 capabilities that interface natively with Claude, ChatGPT, Cursor, and any MCP client. No middleware. No custom integration required.
Available Capabilities
Dealing with scattered market data is a huge time sink.
Today, analyzing a pair's health means jumping between five different tabs: one for the price chart, one for the order book, one for the 24h stats, and two more for checking recent trades. You spend ten minutes just copy-pasting numbers between Excel sheets and cross-referencing which data point is stale.
With the Binance MCP Server, you ask your agent for a full market picture—say, 'Give me the last 4 hours of BTC/USDT, including depth and 24h stats.' The agent runs the necessary tools (`get_klines`, `get_order_book`, `get_24h_ticker`) and spits out one clean, structured block of data. You get the data, not the headache.
Binance MCP Server: Get market data from chat.
Manual data gathering used to require running multiple, distinct API calls for each time window and data type. You had to handle the state machine yourself, ensuring you fetched the correct timestamp ranges for `get_klines` and the appropriate limits for `get_order_book`.
Now, you just tell your agent what you need. It orchestrates the multiple tools and handles the complexity. You only write the request; it handles the plumbing.
Common Questions About Binance MCP
How do I get the current price using the get_ticker_price tool? +
Use get_ticker_price to get the latest price for a pair or all pairs. If you omit the symbol, it returns all available pairs, which is useful for quick checks.
Can I analyze market depth with the get_order_book tool? +
Yes, get_order_book gives you the current bids and asks. You can control the level depth by specifying the limit parameter, up to 5,000 levels.
What is the best way to get historical data using the get_klines tool? +
The get_klines tool is for OHLCV data. You must specify the interval (e.g., 1h, 1d) and the time range using Unix timestamps for accurate results.
Do I need an API key to use the get_24h_ticker tool? +
No, you don't. This server provides public market data, so no API key is required for the core tools like get_24h_ticker.
How do I check recent trades with the get_trades tool? +
The get_trades tool retrieves the latest individual trades. If you need a more volume-efficient summary, try get_agg_trades instead.
How do I get aggregated trades using the get_agg_trades tool? +
It gets compressed trade data, which is better than individual trades for high-volume pairs. This tool returns up to 1000 trades, saving you processing time when analyzing busy markets.
What kind of exchange rules can I check with get_exchange_info? +
It lists all trading pairs, their status, and what kind of filters are available. You can also see the base/quote assets and order types supported by the exchange.
Can I get the server time with the get_server_time tool? +
Yes, it returns the current Unix timestamp in milliseconds and an ISO string. Use this to synchronize your client's clock with the exchange server for accurate data logging.
Do I need an API key? +
No! All public market data (prices, order books, trades, klines, exchange info) is available without authentication. Just subscribe and start querying.
What trading pairs are available? +
Binance supports 1500+ trading pairs. Use get_exchange_info to see the complete list. Popular pairs include BTCUSDT, ETHUSDT, BNBUSDT, SOLUSDT and many altcoin pairs.
What candlestick intervals are available? +
15 intervals are available: 1m, 3m, 5m, 15m, 30m, 1h, 2h, 4h, 6h, 8h, 12h, 1d, 3d, 1w, 1M. Use get_klines with the interval parameter. Each candle includes open, high, low, close and volume.
Can I get historical price data? +
Yes! Use get_klines with startTime and endTime parameters (Unix timestamp in milliseconds) to retrieve historical candlestick data. You can get up to 1000 candles per request.
Use it with your favorite AI tools
Connect this server to Cursor, Claude, VS Code, and more.
More in this category
IBKR (Interactive Brokers)
Manage your Interactive Brokers account — execute trades, monitor portfolio ledgers, and fetch real-time market data via the Client Portal API.
Highnote
Automate card issuance and financial management via Highnote — manage account holders, cards, and transactions directly from any AI agent.
Pagar.me
Create orders, manage subscriptions, and process Pix/Boleto payments via Pagar.me API.
You might also like
Modelbit (ML Model Deployments)
Deploy and call machine learning models directly from your AI agent using Modelbit's inference endpoints.
Advice Slip
Universal advice engine — get random advice or search by keyword via AI.
EdApp
Train your workforce with mobile-first microlearning courses, quizzes, and gamified lessons that employees complete on their phones.