
Binance Mcp
io.github.junct-botPublished by GitHub account junct-botv1.2.0Updated Oct 24, 2026
Binance - 340 tools for market data, order books, and trading pairs
Overview
Hosted MCP server exposing 340 Binance tools for market data, order books and trading pairs, with no authentication required.
- What you can do
- Look up Binance market data, order books and trading pairs through 340 tools
- Each tool maps one-to-one to a real Binance API endpoint, generated from the API specification
- Connect from an MCP client such as Claude Desktop, Cursor or Windsurf over Streamable HTTP
- When to use it
- Useful when an assistant needs Binance market data, order book or trading pair information and you want a hosted endpoint with no key setup. It is aimed at crypto-related agent workflows rather than general web tasks.
- Requirements
- A remote MCP endpoint over Streamable HTTP; no local runtime, account, API key or environment variables are declared. Network access to the hosted endpoint is needed.
Installation
In SourceWeft
- Open Binance Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/io.github.junct-bot%2Fbinance-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"binance": {
"type": "http",
"url": "https://binance.mcp.junct.dev/mcp"
}
}
}README
Binance MCP Server
MCP server for Binance. Agent-ready API for Binance.
Hosted at binance.mcp.junct.dev/mcp. Free to use. No auth. No API key required.
Part of Junct — the agent-readiness layer for the crypto stack.
Quick Start
Add to your MCP client config (Claude Desktop, Cursor, Windsurf):
About
This MCP server is deterministically generated from the Binance API specification. Every tool maps 1:1 to a real API endpoint — no hallucinated endpoints, no phantom tools.
- Protocol: Binance
- Endpoint:
https://binance.mcp.junct.dev/mcp - Transport: Streamable HTTP
- Auth: None required
- Documentation: binance.mcp.junct.dev/llms.txt
- Server card: binance.mcp.junct.dev/.well-known/mcp/server.json
Links
Keywords
Binance, MCP server, DeFi, AI agent, agent-ready API, crypto tools, Model Context Protocol, hosted MCP
Source: README.md at commit d83a8eb
Tools
0Version history
1- v1.2.0LatestSep 16, 2026
Score
40% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts
Declare a license in the repository or the registry entry.