BLOG

AlphaPilot: Dual-MCP Trading Advisory on Binance Agent OS

AlphaPilot is an AI-assisted **market operations agent** for Binance. It was built for the Binance Agent OS Mini Hackathon (Track A) with a clear product line:

October 10, 2026·2 min read·48 views
AlphaPilot: Dual-MCP Trading Advisory on Binance Agent OS

AlphaPilot: Dual-MCP Trading Advisory on Binance Agent OS

How to run a deterministic risk layer beside Binance’s allowlisted Agent OS MCP—without handing your exchange keys to a custom backend.


What AlphaPilot is

AlphaPilot is an AI-assisted market operations agent for Binance. It was built for the Binance Agent OS Mini Hackathon (Track A) with a clear product line:

Find opportunities. Control risk. Optimize capital.

It is not a black-box autotrader and not a chatbot that “suggests” buys with no path to execution. It is a policy and workflow layer that:

  • Scans the market with public Binance REST
  • Scores candidates with deterministic strategies
  • Validates every intent with a Risk Engine that never trusts AI-produced limits
  • Publishes risk-checked TradePlans through a web UI and its own MCP server
  • Lets an allowlisted AI client (Claude, Cursor, ChatGPT, Codex, VS Code, Grok Bot) place orders on Binance Agent OS MCP
  • Records fills so AlphaPilot can monitor positions and surface exit logic

Why this architecture exists

Binance hosts an official MCP endpoint:

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

OAuth for that endpoint is restricted to a short client allowlist. Self-built backends—including AlphaPilot’s own process—hit:

The AI Agent you are using is not currently supported.

So AlphaPilot adopted Option A:

RoleWho owns it
Market data & analysisAlphaPilot (public REST)
Risk limits & TradePlansAlphaPilot (DB + Risk Engine)
Account balancesReported into AlphaPilot by the AI client
Order placementBinance Agent OS MCP (inside allowlisted client)
Position monitoringAlphaPilot (after
record_fill
)

AlphaPilot never stores a Binance API key or OAuth token.


What it was built for

  1. Operators who want AI assistance without giving a model exchange custody
  2. Hackathon / agent-native demos that must work with Binance’s real Agent OS constraints
  3. A dual-MCP workflow: one server for policy, one for execution
  4. Human-in-the-loop by default (
    approval_required
    trading mode), with optional stricter or looser modes later

Core loop:

Public REST scan / chat analysis
        → Strategies + RiskEngine
        → TradePlan (proposed)
        → Human / AI approves
        → Order on Binance Agent OS MCP
        → record_fill
        → Position monitor + exit signals

MORE ARTICLES

Enjoyed this? There's more where that came from.

Browse all posts