Is CCXT MCP Server safe to connect to an AI agent?
Approval is optional. Safety 85%
What an AI agent can do
- Live vs paper: live and sandbox/testnet accounts (per exchange); out of the box only public market data; trading must be enabled per account in the config file, and `"trading": true` works only on sandbox/demo accounts (live needs `"trading": "live"`) source
- Order approval: official local MCP server from the ccxt project (MIT), runs over stdio and keys never appear in tool parameters; capability tiers (market, read, trading, funds for withdrawals, raw write endpoints) are off until set in the config file, which no tool can edit; writes are previewed and confirmed by default on live accounts (confirm: always | live | never), checked against a per-order USD cap you set (maxOrderValue), optional daily cap and symbol allowlist, and logged to an append-only audit journal source
- Markets: crypto spot and derivatives on 100+ exchanges via the unified ccxt API, prediction markets (e.g. Polymarket)
- Pricing: free, open source (MIT); exchange trading fees apply
Safeguards that exist
- Can it place live orders unattended?: Live orders possible; an approval or preview step exists but is optional source
- Order approval or confirmation options: Approval/confirmation step documented source
- Paper, demo or testnet mode: Paper, demo or testnet mode available source
- Withdrawal permission needed or allowed: Withdraw/transfer is a separate 'funds' tier, off by default, enabled per account only in the config file; docs advise keys with withdrawal disabled (official docs) source
- Scoped keys, permission scopes or IP whitelisting: Per-account opt-in capability tiers (market, trading, funds, implicitWrites) that a conversation cannot change, plus symbol allowlists (official docs) source
- Open source or audited: Open source source
Safeguards that are missing
None of the seven inputs scored zero.
Safety score
| Input | From our listing | Points |
|---|---|---|
| Can it place live orders unattended? | Live orders possible; an approval or preview step exists but is optional | 10 / 25 |
| Order approval or confirmation options | Approval/confirmation step documented | 15 / 15 |
| Paper, demo or testnet mode | Paper, demo or testnet mode available | 15 / 15 |
| Withdrawal permission needed or allowed | Withdraw/transfer is a separate 'funds' tier, off by default, enabled per account only in the config file; docs advise keys with withdrawal disabled (official docs) source | 15 / 15 |
| Scoped keys, permission scopes or IP whitelisting | Per-account opt-in capability tiers (market, trading, funds, implicitWrites) that a conversation cannot change, plus symbol allowlists (official docs) source | 10 / 10 |
| Open source or audited | Open source | 10 / 10 |
| Sourced and verified facts | Facts from the vendor's official docs | 10 / 10 |
| Total | 85% of the points we could check | 85 / 100 |
Sources
Full listing: CCXT MCP Server · How the score works: Safety score method · Alpaca MCP vs CCXT MCP Server