Security & FAQ
OAuth scopes, key isolation, limits, audit log, and answers about BYTtrade MCP
Security model
| Control | Detail |
|---|---|
| OAuth 2.1 | You choose scope: read-only or trading; revoke anytime |
| Key isolation | Exchange API keys stay on BYTtrade servers — never sent to Claude/Cursor |
| Limits | Notional, leverage, rate limit, optional demo-only gate |
| Idempotency | Safe retries for trade calls |
| Audit log | Every MCP call and trade is logged |
Safe usage rules
- Prefer demo until you confirm behavior.
- For live trades: confirm size, exchange, leverage, SL/TP, and worst-case loss in chat or Telegram.
- Arbitrage multi-leg orders can partially fail — plan for incomplete fills.
- Outputs are not financial advice.
FAQ
What is MCP and how is BYTtrade different?
Model Context Protocol lets Claude (and other MCP clients) call BYTtrade tools. BYTtrade ships a full crypto MCP: 25+ tools, 4 exchanges, spot/swap, arbitrage, bots, and live trading — with OAuth scopes and an audit log.
Do I need a BYTtrade account?
Yes. MCP connects via OAuth. Sign up first, then connect from Claude or Cursor and choose permissions.
Is it safe?
Exchange API keys never go to the AI client. You pick scope, set limits, and can revoke access. Every call is logged. Residual risk remains with any live trading — use demo and small size first.
Can AI trade without my approval?
Only if you granted trading scope and the client executes tools. For high-impact actions, use confirmation in chat or Telegram Approve/Reject when available. You can keep read-only scope to block all executions.
Where is the product page?
- English: byttrade.com/en/aitrading
- Russian: byttrade.com/ru/aitrading