Sato Hub
MCP

Binance MCP (nirholas)

Community Binance MCP with 478+ tools across spot, margin, futures, staking, NFT, and copy trading.

  • Sato Score52
ActiveUnverifiedQuiet · 3mo ago

Binance MCP (nirholas) is an open-source MCP server by nirholas, with last code activity on 2026-07-14 (Quiet). Sato Score 52/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →

See how to install Binance MCP (nirholas) →

Last commit Jul 14, 2026 · ★ 32

Listed from github.com/nirholas/binance-mcp on 2026-07-13. Install: failed on 2026-09-25. Evidence →

Website ↗GitHub ↗

Next step

Watch Binance MCP (nirholas)

One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.

Check it from your agent

Add Sato Hub’s MCP server (no key), then ask:

https://satohub.ai/api/mcp
Run Sato Hub Preflight on nirholas/binance-mcp before I use it.
Full setup: Claude Code, Cursor, others →

Your project?

Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.

Claim this listing →

Overview

A community-built MCP server for the Binance exchange APIs, claiming 478+ tools spanning spot, margin, and futures trading, staking, NFT, and copy trading. It is not an official Binance product. An agent builder plugs it in to give a trading agent broad Binance API coverage over MCP; exchange API keys and their permissions remain the operator's responsibility.

Sato Score

52/100· Medium

How open, active & verifiable — not a safety or returns grade.

Maintenance & liveness
20/35
Code transparency
18/20
Interface verifiability
0/10
Docs & demo
0/10
Listing transparency & provenance
11/15
Independent verification
3/10
View verification & embed badge →History →How the Sato Score works

Evidence — listed vs checked · what the words mean

Listed from github.com/nirholas/binance-mcp on 2026-07-13. Install: failed on 2026-09-25.

ClaimValueEvidenceSourceChecked
Chains supportednot statedself-reportedgithub.com/nirholas/binance-mcpas of 2026-10-15
Verification statusUnverified — not independently reviewedself-reportedgithub.com/nirholas/binance-mcpas of 2026-10-15
Recent activitylast commit 2026-07-14observedgithub.com/nirholas/binance-mcp2026-10-15
Install worksdid not complete at the install stepa measurement of the documented path, often a stale README — not a judgement of the softwareobservedgithub.com/nirholas/binance-mcp2026-09-25
Website answersanswered (HTTP 200)observedgithub.com/nirholas/binance-mcp2026-10-15
Daily check record90 of 90 daily checks since 2026-07-17 succeededa success rate of our checks, not uptime; the source is this listing's own historyobserved—2026-10-14
Built bynirholasconfidence 0.70self-reportedgithub.com/nirholas/binance-mcpas of 2026-07-14
Creator profilehttps://github.com/nirholasconfidence 0.80self-reportedgithub.com/nirholas/binance-mcpas of 2026-07-14
Works withClaude Desktop, Cursor, ChatGPTconfidence 0.85self-reportedgithub.com/nirholas/binance-mcpas of 2026-07-14
Sato Score52/100 (Medium)how open, active and verifiable — not a safety or quality gradecomputedsatohub.ai2026-10-15

Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.

Install — we ran this on Sep 25, 2026 and the install step did not complete — the commands below are the project's own, and they may simply have moved on

Runtime: Node.js >=18.0.0

install: install failed: src/tools/binance-futures-coinm/trade-api/newOrder.ts(83,17): error TS1005: ':' expected. | src/tools/binance-futures-coinm/trade-api/newOrder.ts(83,55): error TS1005: ',' expected. | src/tools/binance-futures-coinm/trade-api/newOrder.ts(83,68): error TS1005: ',' expected. | src/tools/binance-futures-coinm/trade-api/newOrder.ts(84,11): error TS1005: ',' expected. | src/tools/binance-futures-coinm/
ran: mkdir -p /app || exit 1; cd /app || exit 1; git clone https://github.com/nirholas/binance-mcp.git && cd binance-mcp && npm install && npm run build

entry: skipped (install failed)
ran: d="$(ls -d /app/*/ 2>/dev/null | head -1)"; cd /app/binance-mcp 2>/dev/null || { [ -n "$d" ] && cd "$d"; } || cd /app || exit 1; if timeout 8 node build/index.js </dev/null >/dev/null 2>&1; then c=0; else c=$?; fi; [ $c -eq 124 ] || [ $c -eq 0 ] || exit 3

git clone https://github.com/nirholas/binance-mcp.git
cd binance-mcp
npm install
npm run build
npm run start (STDIO transport); npm run start:sse (SSE transport)

You supply: BINANCE_API_KEY (risk: enables live trading with full account access per README), BINANCE_API_SECRET (same risk)

Add to CursorAdd to VS Code
claude mcp add satohub-binance-mcp-nirholas -- node build/index.js

A local server: your client runs this command on your machine. Installing runs third-party software under your own credentials. Sato Hub publishes the documented invocation and, where the harness reproduced it, the date it did — neither is a safety review.

Read from the project’s own docs as of 2026-09-25. What a deploy spec is →

Observed record — 91 daily checks since 2026-07-17

100%of 91 checks since 2026-07-17 succeeded
Currently responding for 91 days
Succeeded
91
Failed
0
Their error
0
Unattributed
0

This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. Every one of them passed, so the rate covers them too.

Last 30 days — to 2026-10-15, one point per UTC day

Share of OUR checks that succeeded
100%
7-day rolling; unattributable days are gaps · 30/30 days
Tools listed
fewer than 2 points—
from the server's own tools/list · 0/30 days
Sato Score
52
as snapshotted that day · 29/30 days

A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.

Details

Chains
Agent types
MCP Server, Trading
Open source
Yes
Works with
Claude Desktop, Cursor, ChatGPT
Last checked
2026-10-15

Marketplace Signals

No marketplace signals recorded for this resource yet.

Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.

#binance#cex#trading#futures#mcp

Where Binance MCP (nirholas) fits

Trading

Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets

See something inaccurate or outdated?Submit a correction →

Listing History

Recorded changes to Binance MCP (nirholas)'s listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.

  1. Sep 25, 2026
    Verified: deploy spec
  2. Jul 18, 2026
    Sato Hub began tracking this listing
  3. Jul 14, 2026
    Enriched: creator name
  4. Jul 14, 2026
    Auto-enriched: creator profile url, supported integrations
  5. Jul 14, 2026
    Listed on Sato Hub

Compared with

Alternatives to Binance MCP (nirholas) →

Appears in

Related Resources

Coinbase AgentKit

Active
Framework

Coinbase's toolkit for giving AI agents wallets and the ability to take onchain actions.

BaseEthereumMultichain
Recent★ 1.3k

Hyperliquid

Active
VenueVerified

Onchain perpetual futures and spot DEX running on its own L1 with an HyperEVM smart-contract layer.

MultichainHyperliquid
Recent★ 506▸ Jun 2023

Model Context Protocol (MCP)

Active
Standard

Anthropic's open standard for connecting AI systems to external tools and data sources.

Unknown
Active★ 9.4k

Reference

QuestionsShowHide

Questions people ask about Binance MCP (nirholas)

Is Binance MCP (nirholas) open source?
Yes. Binance MCP (nirholas) is open source under the MIT license; the repository is https://github.com/nirholas/binance-mcp. Checked as of 2026-10-15.
Which chains does Binance MCP (nirholas) support?
Sato Hub has no confirmed chain list for Binance MCP (nirholas) as of 2026-10-15; treat chain support as unknown.
Is Binance MCP (nirholas) still maintained?
The most recent code activity Sato Hub observed was on 2026-07-14 (last commit 2026-07-14), which Sato Hub labels "Quiet". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
How do I install or run Binance MCP (nirholas)?
Node.js >=18.0.0. Install: git clone https://github.com/nirholas/binance-mcp.git && cd binance-mcp && npm install && npm run build. Entry: npm run start (STDIO transport); npm run start:sse (SSE transport). This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (node build/index.js (stdio, per Claude Desktop config)).
Is Binance MCP (nirholas) verified on Sato Hub?
No independent verification is on record for Binance MCP (nirholas); its verification status is "Unverified" and its Sato Score is 52 of 100. Self-reported is not verified, and the score is not a safety, quality or returns grade.
Cite this pageShowHide

Cite this page

Sato Hub. "Binance MCP (nirholas) — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/binance-mcp-nirholas

Data last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.

Join the Sato Hub Briefing

Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.