← Agentic Gambling Catalog
Canonical evidence profile

Binance Agentic MCP

Binance · Crypto Exchanges

Officialmonitored
Non-affiliate listings. Links in the Agentic Index are not affiliate links, and WagerX earns no referral commission from them. Inclusion is not an endorsement.

Binance's official hosted MCP connects AI agents to crypto-exchange market data and, when explicitly authorized, balances, trading and internal wallet transfers. WagerX confirmed the endpoint is live: an unauthenticated MCP initialize request returned HTTP 401 and advertised official OAuth protected-resource metadata. Tool inspection was blocked before authorization. Binance states that withdrawals are never available and every trade or transfer requires user confirmation.

Evidence & discovery

This profile records public discovery and WagerX observations. It does not establish legality, security, availability or correctness of provider claims.

Provider documentation ↗
Append-only observations

Protocol observation history

Routine checks collect metadata only: protocol initialization and declared capabilities. Separately authorized read-only tests, where published, are recorded below with their exact inputs and limits.

MCP · manual
authentication requiredEndpoint responded but requires authentication.https://agent.binance.com/mcp/agentic

HTTP 401 · 839 ms

Published baseline

Test results

Separate from protocol observation history. Results record the dated inputs, returned response and stated limits of an authorized read-only test.

Download JSON
original-protocol

mcp · https://agent.binance.com/mcp/agentic

Access required
Checked
2026-09-10T14:36:44.031023+00:00
Test input
Initialize an MCP session and list the available tools.
Curated response
The endpoint returned HTTP 401 before MCP inspection completed.
Limit
One point-in-time metadata inspection.
Contract hash
Response hash
original-task

mcp · https://agent.binance.com/mcp/agentic

No task call
Checked
2026-09-10T14:40:20.289810+00:00
Test input
No tool call; protocol inspection did not complete.
Curated response
No application result was obtained.
Limit
This preserves the attempted follow-up without treating it as an executed tool call.
Contract hash
Response hash
Method & limitations
  • The remote endpoint required access before protocol metadata could be inspected.