Provides tools for retrieving live and historical market data from Binance, including current price, 24h statistics, and OHLC candles for any trading pair.
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-market-mcp-server what's the current price of BTCUSDT and its 24h change?"
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.
An MCP (Model Context Protocol) server that gives Claude live and historical Bitcoin (or any Binance pair) market data — the data layer for a regime-switching DCA signal system. It does not compute momentum, EGARCH, or any signal logic itself; it fetches clean price data, and the analysis happens downstream in the skill/prompt that consumes it.
Two tools, backed by Binance's free public REST API (no key or signup required):
binance_get_current_priceLive snapshot: last price, 24h change (absolute + %), 24h high/low, 24h
volume. Defaults to BTCUSDT but accepts any Binance pair.
binance_get_historical_ohlcHistorical daily/hourly/weekly OHLC candles for a date range. Handles
pagination transparently past Binance's 1000-candle-per-request cap (returns
up to 2,000 candles per call; narrow the date range if you need more).
Binance's BTCUSDT history begins 2017-08-17 — covers the 2020 and 2024
halving cycles in full, most of the 2017–2018 cycle.
Both tools are read-only (no orders, no account access — this hits Binance's public market-data endpoints only, nothing that requires an API key).
Related MCP server: Crypto MCP Server
CoinGecko's free Demo tier only gives ~1 year of historical daily data — not enough for multi-year cycle backtesting. Binance's public klines endpoint gives free, keyless access to daily candles back to 2017, which is what a 4+ year DCA horizon backtest actually needs.
binance-market-mcp-server/
├── package.json
├── tsconfig.json
├── src/
│ ├── index.ts # entry point, stdio + HTTP transport
│ ├── types.ts # shared TS interfaces
│ ├── constants.ts # API base URL, limits, defaults
│ ├── tools/market.ts # tool registration + handlers
│ ├── services/binance-client.ts # Binance API client, pagination, errors
│ └── schemas/market.ts # Zod input validation
└── dist/ # compiled output (after `npm run build`)npm install
npm run build
# stdio mode (for Claude Desktop / Claude Code local config)
npm start
# HTTP mode (for remote/claude.ai custom connector)
TRANSPORT=http PORT=3000 npm startQuick manual test once running in HTTP mode:
curl -X POST http://localhost:3000/mcp \
-H "Content-Type: application/json" \
-H "Accept: application/json, text/event-stream" \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"test","version":"1.0.0"}}}'You should get back a serverInfo block confirming the handshake. This part
was verified in the build sandbox. What was NOT verified in the sandbox:
actual live calls to the Binance API (the sandbox's network whitelist
doesn't include api.binance.com). First real end-to-end test — an actual
binance_get_current_price call hitting live Binance — needs to happen
either locally on your machine or after deployment. Do this before trusting
the server for anything real.
Any Node-friendly host with a free tier works. Two straightforward options:
Push this folder to a GitHub repo.
On render.com: New → Web Service → connect the repo.
Build command: npm install && npm run build
Start command: npm start
Add environment variable: TRANSPORT=http (Render sets PORT itself).
Deploy. Your MCP endpoint will be https://<your-app>.onrender.com/mcp.
Note: Render's free tier spins down after inactivity — first request after idle will be slow (cold start, ~30-50s). Fine for a weekly manual check-in, not for anything latency-sensitive.
Same idea — connect repo, set TRANSPORT=http, Railway auto-detects Node
and runs npm run build && npm start. Railway's free tier has usage-hour
limits rather than spin-down; check current limits before committing to it
long-term.
Settings → Connectors → Add custom connector → paste your deployed
/mcp URL. No authentication is configured on this server (it's read-only
public market data) — if you want to restrict access, add an API-key check
in src/index.ts before connecting it to anything shared.
Whale wallet / on-chain data: not covered by this server. Flagged earlier as a free-tier data gap — needs a separate connector once that source is picked.
Other symbols: already generalized — symbol param works for any
Binance pair, not just BTCUSDT.
Rate limits: Binance public endpoints allow generous request volume for this use case (weekly checks + occasional backtest pulls). No API key needed. If you scale this to many symbols/high frequency, revisit.
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:
symbol (string, optional): Trading pair, e.g. "BTCUSDT". Defaults to "BTCUSDT".
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:
Use when: "what's the current BTC price" -> symbol="BTCUSDT" (or omit, it's the default)
Use when: "check ETH price" -> symbol="ETHUSDT"
Don't use when: you need price history over time (use binance_get_historical_ohlc)
Error Handling:
Returns "Error: ..." text if the symbol is invalid or Binance is rate-limiting.
Inputs: symbol.
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:
symbol (string, optional): Trading pair, e.g. "BTCUSDT". Defaults to "BTCUSDT".
interval (string, optional): Candle size — "1h", "4h", "1d", or "1w". Defaults to "1d".
start_date (string, required): Start date, format YYYY-MM-DD. BTCUSDT data begins 2017-08-17.
end_date (string, required): End date, format YYYY-MM-DD.
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:
Use when: "get me 5 years of daily BTC prices" -> symbol="BTCUSDT", interval="1d", start_date="2020-01-01", end_date="2025-01-01"
Use when: "weekly BTC candles for the last 2 years" -> interval="1w" with an appropriate date range
Don't use when: you just need the current price (use binance_get_current_price)
Error Handling:
Returns "Error: ..." text if dates are malformed, start is after end, or Binance is rate-limiting.
If start_date predates 2017-08-17, the response will include a "note" explaining the series starts later than requested.
Inputs: end_date (required), start_date (required), symbol, interval.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Binance - 340 tools for market data, order books, and trading pairs
Read-only market and on-chain data for Bitcoin, Ethereum and more; on-chain from our own nodes.
Crypto market signals and portfolio telemetry. 6 tools pay-per-call in USDC, no API key.
Live and historical cryptocurrency prices via CoinGecko free API.