mcp-server-ccxt
Provides an MCP server that uses the Python CCXT library to fetch real-time and historical cryptocurrency market data (prices, market summaries, top volumes, OHLCV, price change stats, and volume history) from multiple exchanges.
Score Breakdown
⚙ Agent Friendliness
🔒 Security
No explicit transport/auth/security posture is documented for the MCP server. TLS is not discussed (likely local). Exchange credentials handling is not described; since no auth model is documented, agents should assume the server is for trusted environments. Dependency hygiene appears reasonable (small set: mcp, ccxt) but no vulnerability/CVE status is provided.
⚡ Reliability
Best When
You need LLM-accessible market data from many exchanges for analytics, summarization, or research workflows where read-only accuracy is acceptable and you can tolerate exchange/API variability.
Avoid When
You require strict SLAs, deterministic pagination/streaming semantics, or robust, documented auth controls for sensitive environments (the server appears to be run locally without an explicit auth model).
Use Cases
- • Have an LLM query current crypto prices by trading pair and exchange
- • Generate market summaries (bid/ask, spreads) for specific symbols
- • Retrieve and analyze OHLCV/candlestick history for defined timeframes
- • Identify top trading pairs by volume per exchange
- • Compute price change and volume trends over time using exchange data
Not For
- • Performing trade execution or order management (read-only market data focus)
- • Providing guaranteed real-time accuracy beyond what exchange APIs return
- • Serving as a secure custody or authentication gateway for trading accounts
- • Use in compliance-critical reporting without validating exchange data sources and definitions
Interface
Authentication
No authentication scheme is described in the README. This implies the server is likely intended to be run locally and used by a trusted MCP client. Exchange API authentication is not described (market data endpoints typically do not require it for many exchanges, but some may).
Pricing
No pricing information provided; expected cost is your infrastructure/compute plus any upstream exchange/API usage constraints.
Agent Metadata
Known Gotchas
- ⚠ Exchange rate limits and connectivity issues can cause tool failures; the README suggests delays but does not show explicit retry/backoff contracts.
- ⚠ Timeframe/parameter validation is mentioned, but the exact input schema and error formats for tool arguments are not shown.
- ⚠ The server is run as a local process (command/args for Claude Desktop); orchestration and sandboxing are on the user environment.
Alternatives
Full Evaluation Report
Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for mcp-server-ccxt.
AI-powered analysis · PDF + markdown · Delivered within 30 minutes
Package Brief
Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.
Delivered within 10 minutes
Score Monitoring
Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.
Continuous monitoring
Scores are editorial opinions as of 2026-03-30.