Binance MCP Server

MCP ServerVendor

Binance Agent OS endpoint giving approved AI clients market data and account access (also listed under Brokerage & Trade Execution). Public tickers, order books, candlesticks and funding rates need no auth; authorized actions cover balances, internal transfers and spot, margin, Convert and futures trading where eligible. Agents cannot withdraw to external addresses or fund the Agentic subaccount.

cryptoexchangeAgent OStrading

Status

Vendor

Auth

OAuth

Hosting

Remote

Community rating

Not rated yet

Open documentation →

Rate this server

How to connect Binance MCP Server

Step 1

Check the vendor's documentation

This listing does not publish a public endpoint or install command yet. Open the vendor documentation above for access details, then follow the general steps in our connection guide.

Step 2

Authenticate with OAuth

Your client opens a browser sign-in with the vendor. Approve only the scopes you need, and use a read-only account first when the platform offers one.

Step 3

Verify, then widen access

Restart your client, confirm the server's tools appear, and run one read-only question first. Keep client-side approval prompts on for any tool that can write, trade or send. Confirm with your firm's compliance policy before connecting systems holding client data.

Prompts that use this server

Starter prompts from the Practice Stacks that rely on Crypto & Digital Assets.

Digital asset holdings snapshot

One consolidated view across exchanges and wallets.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: consolidate my digital asset holdings across every connected source — exchange accounts, on-chain wallet or explorer tools, and any brokerage account holding crypto or crypto ETPs — into one table: asset, quantity, venue, source tool, USD value and share of total. Show a per-source subtotal so I can see which tool reported what, and flag any asset that appears in more than one source so it is not double-counted. Mask wallet addresses beyond the first and last four characters. Do not trade, transfer, approve or sign anything.

Guardrail · Read-only keys only. Never give a chat tool withdrawal or signing permissions.

Cost basis and realised gains review

A tax-ready view of what was sold and when.

Crypto & Digital AssetsCrypto & Digital AssetsAccounting & Tax

Read-only: list realised gains and losses on digital assets for <tax year> by combining exchange transaction history with on-chain transfer data, then compare the result to what is already recorded in my accounting or tax system. Show acquisition date, disposal date, proceeds, basis and the source tool for each line, and flag every transaction where basis is missing, inferred, or disagrees between the exchange and the books. Do not file, submit, amend or post any journal entry — this is a working draft for the tax preparer.

Guardrail · Draft only. Crypto basis data is often incomplete — verify before filing.

Venue and counterparty risk review

Where the assets actually sit and what that exposes you to.

Crypto & Digital AssetsCrypto & Digital AssetsBrokerage & Trade Execution

Read-only: map where my digital asset exposure actually sits by combining exchange or custodial venue data, on-chain wallet and staking or DeFi data, and any crypto exposure held through brokerage accounts. For each venue describe the counterparty, smart-contract and liquidity risk, and note any concentration above <threshold>% of total digital assets across all sources combined. State which figures came from which tool and what you could not verify on-chain. No recommendations to move funds and no transactions.

Guardrail · Read-only. Never approve token allowances or transactions from a chat session.

Read the full connection guide →