MCP server for the Binance Spot + Wallet REST API (API-key auth, stdio).
Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.
Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"amazing-binance-mcp","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.
Everything here was measured by our prober or read from a registry. Nothing is self-reported.
Attributed to the source that supplied each field. Treated as claims, not facts.
# Binance MCP Server (amazing-binance-mcp) A [Model Context Protocol](https://modelcontextprotocol.io) server for the [Binance Spot + Wallet REST API](https://developers.binance.com/docs/binance-spot-api-docs), built on the official [MCP Python SDK](https://github.com/modelcontextprotocol/python-sdk) (FastMCP, stdio transport). It authenticates with a plain **API key** — Ed25519 or HMAC, **no OAuth** — so an LLM can read your deposits, withdrawals, trades, balances, fiat and Pay history and live market data, and — only when you flip the kill-switch — place and cancel spot orders, order lists, TWAP algo orders and conversions. > The PyPI distribution and console script are both **`amazing-binance-mcp`** (the bare > `binance-mcp` and `binance-mcp-server` names on PyPI belong to unrelated packages). > Always run `uvx amazing-binance-mcp`. ## Safety model Three rails, all enforced in the HTTP client — not in the tools — so no tool can forget them: - **No withdrawals, ever.** There is no withdrawal tool, and the client refuses the withdrawal and fiat-rail endpoints under any configuration. Create the API key with "Enable Withdrawals" **off** and an IP allowlist as well; `binance_health_check` warns if the key can withdraw. - **Trading is off by default.** Anything that moves funds or changes account state — orders, cancels, order lists, transfers between your wallets, convert, TWAP, dust conversion — returns `Error: … trading is disabled` until `BINANCE_ALLOW_TRADING=1`. The order dry-run (`binance_test_order`) always works. Those tools are marked 🔒 below. - **Confirmations never claim more than Binance said.** A placed order echoes the status Binance returned (an `EXPIRED` FOK is reported as *not live*); a TWAP is *accepted, not executed*; a convert is *converted* only when the status is `SUCCESS`. A 5xx or timeout on a mutating call is reported as **execution UNKNOWN** with the tool to query before retrying — the server never retries a mutati…
Mapped onto the structured taxonomy from declared text and observed tool names. Confidence shown for derived entries.
Every source is kept verbatim. Field changes are logged as events.