boss
Provides tools for interacting with Binance Spot, including live market data, technical analysis, order planning with policy checks, approval workflows, and order execution through Binance's public API and Agent OS.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@bossAnalyze BTCUSDT and suggest a buy if safe."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
BOSS
Observe. Plan. Approve. Then act.
Permission-first copilot for Binance Spot, built to run beside Binance Agent OS.
BOSS reads live market data, sizes orders to exchange filters, runs a fail-closed policy gate, and only mints a send token after you type EXECUTE. It does not invent prices. If Binance is unreachable, BOSS stops.
Live demo | |
Desk | |
Docs | |
License | MIT |
Why BOSS
Most guardrails verify what an agent is about to send. BOSS also controls when sending is allowed:
BLOCK — a hard rule failed; no approval, no send
UNKNOWN — required data is missing (usually balances); planning allowed, sending refused
CLEAR — gate open; you still must type
EXECUTE
Missing data is never treated as zero. Every approved order carries an HMAC newClientOrderId stamp. Post-trade ingestion classifies AUTHORISED, FOREIGN, FORGED, MISMATCHED, or UNKNOWN_AUTHENTIC.
Default mandate caps: 100 USDT per order, 500 USDT per UTC day, Spot only.
Related MCP server: Binance Agent MCP Server
Features
Live Spot tape (20 symbols), order book, 1h/4h candles, WebSocket + REST fallback
Analysis reports: technicals, Web3 pulse, public news RSS, Fear & Greed
Exact lot / tick / min-notional sizing from
exchangeInfo19-rule policy matrix evaluated on every plan
One-time
EXECUTEapproval tokens (60s TTL, single-use)Execution packet for Agent OS with unchanged fields + stamp
Hash-chained local receipts and trade-scope burn on foreign orders
15 MCP tools — same session as the web desk
Architecture
┌─────────────┐ ┌──────────────────┐ ┌─────────────────────┐
│ MCP host │────▶│ BOSS MCP / desk │────▶│ Binance public REST │
│ Cursor etc. │ │ observe · plan │ │ + Web3 signal boards│
└─────────────┘ │ policy · approve │ └─────────────────────┘
│ └────────┬─────────┘
│ │ EXECUTE + packet
▼ ▼
┌─────────────────────────────────────┐
│ Binance Agent OS MCP │
│ agent.binance.com/mcp/agentic │
│ account read · Spot order send │
└─────────────────────────────────────┘One Node process serves the landing page, desk UI, REST API, and Streamable HTTP MCP.
Quick start (local)
Requirements: Node.js 22+
git clone https://github.com/nrlartt/boss.git
cd boss
npm install
npm test
npm startURL | Purpose |
Landing page | |
Trading desk | |
BOSS MCP (Streamable HTTP) | |
Documentation |
Copy .env.example to .env only if you need custom settings or local API keys.
Try these commands (desk command bar)
analyze BTCUSDT
plan buy 50 usdt ETHUSDT
plan sell 0.01 BTCUSDTAttach free balances (Operations tab or boss_attach_account) and re-run the plan so BALANCE_SUFFICIENT can pass. Only CLEAR plans accept EXECUTE.
Agent OS workflow
boss_status— confirm Binance public feed is reachableboss_plan— e.g.plan buy 50 usdt BTCUSDTboss_attach_account— balances from Agent OS (if needed)Re-run
boss_planuntil verdict is CLEARUser types
EXECUTE→boss_approveSend
boss_packetfields through Agent OS Spot order tool (unchanged)boss_reconcilewith exchangeorderId+approvalId
MCP configuration
{
"mcpServers": {
"binance": {
"url": "https://agent.binance.com/mcp/agentic",
"auth": { "CLIENT_ID": "vscode" }
},
"boss": {
"url": "http://127.0.0.1:8790/mcp"
}
}
}Hosted: replace the BOSS URL with https://<your-host>/mcp.
Agent OS OAuth is supported on first-class clients (Claude, ChatGPT, Codex, VS Code, Grok). Error 3346001 means the host is not on Binance’s allowlist — use a listed client or optional local API keys after approval.
MCP tools
Tool | Phase | Description |
| read | Health, mandate, session, MCP URL |
| read | Live 24h tape for tracked symbols |
| read | Ticker, depth, filters, SMA, Web3 boards |
| read | Full research report + scored summary |
| write | Parse command, size order, run policy gate |
| write | Attach host-observed balances |
| write | Mint token when phrase is exactly |
| read | Execution packet (does not consume token) |
| write | Send via local API keys (optional) |
| write | Record Agent OS order id, classify stamp |
| write | Ingest exchange order for classification |
| read | Scope, stamp counters, audit events |
| read | Receipt by id or recent list |
| read/write | Caps, allowlist, kill switch |
| read | Fetch stored plan by id |
Policy rules (19)
Evaluated on every plan, in order:
KILL_SWITCH · TRADE_SCOPE · PRODUCT_SPOT · SYMBOL_TRADING · SYMBOL_ALLOWLIST · SIDE_ALLOWED · ORDER_TYPE_ALLOWED · QUOTE_ASSET · LOT_SIZE · MIN_NOTIONAL · MAX_NOTIONAL · DAILY_NOTIONAL · PRICE_TICK · PRICE_DEVIATION · SPREAD_SANE · EVIDENCE_FRESH · BOOK_COVERAGE · BALANCE_SUFFICIENT · APPROVAL_REQUIRED
Environment variables
Variable | Default | Description |
|
| HTTP port |
|
| Mandate, session, receipts |
|
| Public Spot REST base URL |
| auto | 32+ char secret for order stamps |
|
| Skip public feed boot guard if |
| auto on Railway | Hosted mode flag |
| auto | Public base URL for MCP links |
| — | Extra tape symbols (comma-separated) |
| — | Optional; local signed send only |
| — | Optional; local signed send only |
|
| Must be |
Never commit .env. See SECURITY.md.
Development
npm run dev # watch mode
npm test # vitest (20 tests)
npm run typecheck # tsc --noEmitBoot guards run at startup: HMAC, mandate, receipt chain, public feed, clock skew. Any FAIL refuses to listen (except feed when BOSS_ALLOW_OFFLINE=1).
Deploy
Railway one-click deploy from this repo. See DEPLOY.md.
Cloud hosts use https://data-api.binance.vision when BINANCE_SPOT_BASE is unset.
Project layout
public/ Landing page, desk UI, docs
src/
analysis/ Research reports, RSS, technicals
audit/ Scope burn, stamp classification, boot guards
desk/ HTTP service, commands, alerts, session
http/ Server + static routing
market/ Binance REST/WS, signals, signed API
mcp/ MCP tool definitions
plan/ Order sizing planner
policy/ Mandate + 19-rule engine
receipts/ Hash-chained receipt store
stamp/ HMAC clientOrderId
tests/ Vitest suite
skills/boss/ Agent skill for Cursor / Agent OS hostsDisclaimer
BOSS is software, not financial advice. Digital-asset markets are volatile. You are responsible for eligibility, local regulations, Agent OS permissions, and every order you approve. Revoke Agent OS access from your Binance account when needed.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Non-custodial limit, stop-loss and DCA trading on Epsilon (Robinhood Chain) for AI agents
On-chain security and market intelligence for trading agents on Base.
Autonomous xRocket CEX trading inside operator-set limits, plus live market data over MCP
DeFi safety layer for AI agents: wallet safety, token risk, tx decode/simulate. 20 tools.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceConnects LLM agents to Binance Spot API for safe market data access and testnet trading with built-in risk controls.65MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously analyze market data, compute risk metrics, and execute spot or futures trades on Binance with safety guardrails like dry-run mode and slippage protection.1-
- AlicenseNot gradedqualityBmaintenanceEnables risk-gated AI trading on Binance by researching market data, enforcing policy checks, and building executable MCP order requests that require user confirmation before the official Binance MCP server executes them.MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to trade on Binance through a governed MCP proxy that enforces configurable policies, requires a recorded rationale before orders, detects prompt injection, logs all actions in a tamper-evident audit trail, and blocks execution until a human approves.-