MCP server for Binance Thailand (Gulf Binance) API — trade crypto, monitor markets, and manage your account. ## Features - Real-time market data: prices, order books, candlesticks, 24hr stats (no API key needed) - Place and manage orders: LIMIT, MARKET, STOP_LOSS, TAKE_PROFIT, and more - Account management: balances, trade history, fee rates - Wallet operations: deposits, withdrawals, address management - Sub-account transfers and user data stream management - HMAC SHA256 signed requests for secure trading ## 27 Tools **General (3)**: server time, exchange info, symbol types (GLOBAL vs SITE/Thailand) **Market Data (7)**: order book, recent trades, aggregate trades, klines/candlesticks, 24hr ticker, price ticker, book ticker **Account (3)**: account info/balances, trade history, trade fees **Orders (6)**: place order, query order, cancel order, open orders, all orders, cancel all orders **Wallet (4)**: withdraw, deposit address, deposit history, withdraw history **SubAccount (1)**: transfer between sub-accounts **User Data Stream (3)**: create, keepalive, close listen key ## Configuration - BINANCE_TH_API_KEY — API key from https://www.binance.th (API Management) - BINANCE_TH_SECRET_KEY — Secret key for HMAC signing ⚠️ WARNING: No testnet. All trading and withdrawals use real money.
MCP readiness
Readiness is how fully this listing follows its protocol and how it behaved in our probes over 30 days. It is shown for reference and does not move it in search. Search order and leaderboards use the separate quality grade (here C+, 70.0/100), which weighs availability, conformance, p95 speed and descriptor. How the two differ
| Valid MCP handshake | 10/10 | initialize and tools/list both answered. |
| Live MCP endpoint | 24/25 | Endpoint answers the MCP initialize handshake (4903 ms); slow response -1. |
| Protocol revision | 8/10 | Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28. |
| Signed descriptor | n/a | No MCP standard defines a signed server descriptor. |
| Uptime (30 days) | 15/15 | 31/31 probes succeeded over 30 days (100%). |
| Tool declaration | 10/10 | Lists 27 tool(s) with descriptions. |
| Verified identity | 5/10 | Publisher declared (repository, package or homepage); claim this listing to verify domain control. |
| Freshness + modern flags | 4/5 | seen in a source within 7 days. |
| Auth declaration | 2/5 | Declares credential scheme: smithery_api_key. |
Compared with peers
Against 53,039 reachable MCP servers in our daily snapshot (2026-11-12 06:46 UTC). Display only; it does not change search order.
- Readiness
- Higher than 88% of peers
- This listing 87 · peer median 81
- Latency
- Faster than 21% of peers
- This listing 609 ms · peer median 326 ms
Where it loses the most points, and how to win them back
- Verified identity −5
— Claim the listing and prove control of its domain.
Now: Publisher declared (repository, package or homepage); claim this listing to verify domain control.
- Auth declaration −3
— State how to authenticate (an auth scheme, or that none is needed).
Now: Declares credential scheme: smithery_api_key.
- Protocol revision −2
— Support the current protocol revision.
Now: Speaks MCP 2025-11-25, 1 revision(s) behind 2026-07-28.
Adoption signals
Public signals from outside this directory, shown for context. They do not change search order or grades.
Listed in
Directories this entry was found in.
How to connect
https://server.smithery.ai/node2flow/binance-th-mcp/mcpcurl -X POST https://server.smithery.ai/node2flow/binance-th-mcp/mcp \
-H 'Content-Type: application/json' \
-H 'Accept: application/json, text/event-stream' \
-d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{}}'