CommunityAbandoned· 1.0y★ 4.3by doggybee

CCXT MCP

Crypto exchange integration using CCXT, covering spot, futures, OHLCV, balances, and orders across 20+ exchanges.

View repo

Safety & Trust

Delv Safety Grade: C

Score 58/100 · assessed 2026-04-28

Maintainer40

Permissions50

Supply chain65

Transparency70

Incidents100

This MCP server wraps the CCXT library to provide cryptocurrency exchange integration across 20+ platforms. The maintainer 'doggybee' appears to be a solo developer with limited public profile, creating moderate bus factor risk. The server requires API keys and secrets for exchange access, granting read and write capabilities to trading accounts including balance queries, order placement, and position management. Whilst distributed via npm with standard packaging, the scope of permissions is concerning: full trading authority means potential for significant financial loss if credentials leak or the server is compromised. The CCXT dependency itself is well-established, but this wrapper adds an intermediary layer. Documentation exists but is basic. No known security incidents, though the financial sensitivity of operations warrants careful credential management and monitoring. Suitable for development environments with test accounts rather than production trading with substantial funds.

Lethal Trifecta (prompt-injection exposure)

TWO OF THREE

Private dataYes

Reads secrets, credentials, private files

Untrusted inputNo

Ingests web pages, PRs, issues, emails

External commsYes

Can send data outbound

Crypto exchange API keys are private and high-value. No untrusted ingestion in normal use, but a 2/3 with very high blast radius if compromised.

Green flags

Distributed via npm with standard package management
Builds on established CCXT library
Open source with visible repository
No known security incidents or CVEs

Red flags

Solo maintainer with limited public track record
Full trading permissions including order placement and balance access
API keys grant direct financial transaction authority
Thin documentation on security best practices
No evidence of security audit or review

Permissions requested

Outbound networkAccess secretsPayments readPayments writeIdentity read

Assessed by Delv Editorial using public metadata. Grades are advisory and update as the ecosystem changes. They do not replace your own review of permissions and code before granting an agent access to sensitive systems.

Install

npm install -g @mcpfun/mcp-server-ccxt

Env vars needed: EXCHANGE_API_KEYEXCHANGE_SECRET

Review

CCXT MCP wraps the CCXT library, giving Claude access to 20+ crypto exchanges through a single server. You get spot and futures markets, OHLCV candles, balance checks, and order placement. The big win is consistency: instead of wrangling each exchange's API quirks, you ask Claude to fetch Binance OHLCV or check your Kraken balance, and it just works. I'd reach for this when building trading research workflows or multi-exchange monitoring. Say you want to compare BTC/USDT spreads across Binance, Coinbase, and Kraken. You ask Claude to pull orderbook snapshots from all three, and it returns structured data you can analyse. Or you're backtesting a strategy: request hourly candles for the past six months, export to CSV, done. The server handles authentication per exchange, so you set API keys once in the config and forget about them. Quirks: you need to know which exchange supports which features. CCXT itself has patchy coverage (some exchanges don't expose funding rates, others lack margin endpoints), and this MCP inherits those gaps. The docs don't spell out every limitation, so expect some trial and error. Also, rate limits are on you. Claude won't auto-throttle requests, so hammering an exchange will get you temporarily banned. You'll want to batch requests sensibly. The install is straightforward if you're comfortable with npm globals and editing JSON configs. You supply exchange credentials as environment variables, which means rotating keys or switching exchanges requires a config edit and restart. Not a dealbreaker, but not as slick as runtime credential swapping. Who shouldn't bother: if you're only tracking one exchange and already have a Python script, this adds overhead. It shines when you need Claude to reason across multiple exchanges or when you want conversational access to market data without writing boilerplate. Casual crypto holders checking portfolio balances once a week won't get much value. This is for developers doing research, arbitrage scouting, or building trading dashboards where Claude becomes the query layer.

Verdict

Install this if you're doing multi-exchange crypto research or building trading tools where Claude's reasoning helps. Skip it if you're happy with a single exchange's API or don't need conversational access to market data. The CCXT foundation is solid, but you'll hit the library's own coverage gaps.

Good at

Single interface for 20+ exchanges means you don't write per-exchange API wrappers.
Covers spot, futures, OHLCV, balances, and orders in one server.
Useful for arbitrage research and multi-exchange comparisons without leaving Claude.
CCXT's mature library underneath handles most edge cases and auth flows.

Watch out

Inherits CCXT's patchy feature coverage, so some exchanges lack margin or funding rate endpoints.
No built-in rate limiting, so you can easily hit exchange bans if you're not careful.
Credential management requires config edits and restarts, no runtime key swapping.
Docs don't detail which exchanges support which features, expect some trial and error.

Use cases

multi-exchange trading
market data analytics
arbitrage research
OHLCV backtesting

Getting started

1. Run `npm install -g @mcpfun/mcp-server-ccxt` to install globally. 2. Add the server to your Claude Desktop config, setting `EXCHANGE_API_KEY` and `EXCHANGE_SECRET` environment variables for your chosen exchange (e.g., Binance, Kraken). 3. Restart Claude Desktop and ask it to fetch a ticker or balance from your configured exchange to confirm the connection. 4. Check CCXT's exchange-specific docs to see which features your exchange supports, as not all endpoints work everywhere. 5. Watch your rate limits: Claude won't throttle requests automatically, so batch queries to avoid temporary bans.

Works with

Claude DesktopClaude CodeCursor