CCXT vs XRocket Exchange MCP

A side-by-side look at the CCXT and XRocket Exchange MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.

CCXT logoCCXTFinance & FintechOfficial CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets64GoodAuth: not declaredXRocket Exchange MCP logoXRocket Exchange MCPFinance & Fintech · Local subprocess (stdio)Unofficial xRocket market data and opt-in local account and financial workflow tools59GoodAuth: not declared

Verdict: choose CCXT for finance & fintech work; choose XRocket Exchange MCP for finance & fintech as a local process. You can also run both side by side in one mcpServers block.

Which MCP server should you choose?

CCXT logoChoose CCXT when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You want tools like list_exchanges, describe_exchange, describe_method.
Explore CCXT

XRocket Exchange MCP logoChoose XRocket Exchange MCP when

  • You need dedicated capabilities in the Finance & Fintech domain.
  • You prefer a local stdio subprocess transport.
  • You want tools like xrocket_market_snapshot, xrocket_market_symbols, xrocket_market_tickers.
Explore XRocket Exchange MCP

Feature & specification comparison

Rows where the two servers differ are marked.

SpecCCXT logoCCXTXRocket Exchange MCP logoXRocket Exchange MCP
CategoryFinance & FintechFinance & Fintech
Quality signal64/100 · Good59/100 · Good
Install commandNot confirmed yetConfirmed
Transport—Local subprocess (stdio)
AuthNot declaredNot declared
PricingNot declaredNot declared
Required env varsNone listedNone listed
Verified ownerCommunity listingCommunity listing
GitHub stars44,4800
Directory activity 2 views 0 installs 0 upvotes 1 views 0 installs 0 upvotes
Tools3210

Tools & capabilities

CCXT tools 32

  • list_exchangesList every exchange this server supports (built from ccxt.exchanges at runtime), with name, websocket and prediction-market availability. Filter by a name query or by support for a unified method.
  • describe_exchangeOne exchange's supported unified methods, market types, timeframes, required credential fields, sandbox availability and documentation URLs. Per-method detail lives in describe_method.
  • describe_methodSearch unified method names by keyword, or get one method's signature and parameter documentation. With "exchange" it adds that exchange's own docs (including supported params.* keys and links to the exchange API reference), per-market-type feature support, and searches its implicit (exchange-specific) endpoints too. Full ccxt manual: https://docs.ccxt.com/
  • search_marketsSearch and filter the markets of one exchange (by text, base, quote, settle currency, market type), paginated. Use this to resolve unified symbols — there is deliberately no list-all-markets tool. On prediction exchanges use search_events instead.
  • get_tickers24h price tickers for one or more unified symbols on an exchange (outcome handles on prediction exchanges).
  • get_orderbookCurrent order book (bids and asks) for one unified symbol.
  • get_ohlcvHistorical OHLCV candlestick data for a symbol and timeframe. Rows are [timestampMs, open, high, low, close, volume]. Page back with "since"; "params.until" bounds the end.
  • get_tradesRecent public trades for one unified symbol.
  • search_eventsSearch events on a prediction-market exchange (polymarket, kalshi, limitless, myriad, hyperliquid with prediction=true). A scoping filter is required: query, tags, or params.eventId/params.slug. Returns events with their markets and outcome handles — outcome handles are what you pass as the symbol to get_tickers/get_orderbook/create_order on prediction exchanges.
  • call_read_methodEscape hatch covering every unified read method not served by a dedicated tool (fetchFundingRate, fetchLedger, fetchOpenInterest, fetchLiquidations, fetchEvent, fetchSettlements, …). Only fetch*/load* methods are accepted — writes are structurally rejected. Get the signature first with describe_method. Docs: https://docs.ccxt.com/
  • call_implicit_getCall an exchange-specific implicit REST endpoint over HTTP GET, for data the unified API does not cover. Pass the implicit method name in the "method" argument (e.g. "publicGetTickerPrice"); these are exchange-specific — find them with describe_method {"query": ..., "exchange": ...} (its results list the name to pass here). The response is the raw exchange payload. Consult the exchange API reference (describe_exchange .urls.doc) and the ccxt manual: https://docs.ccxt.com/
  • get_safety_statusWhat this server is currently allowed to do: configured accounts (names only — never credentials), enabled capability tiers, caps, sandbox/live environments, journal location, unresolved order intents, and any configuration problems.
  • +20 more on the listing page

XRocket Exchange MCP tools 10

  • xrocket_market_snapshotResolve an exact symbol or base asset and return market rules, ticker, best bid/ask, recent trades, and fees in one read-only call. Exact symbols win; ambiguous assets are never guessed.
  • xrocket_market_symbolsList all exchange symbols or inspect one exact symbol and its trading constraints.
  • xrocket_market_tickersGet public 24-hour ticker data, optionally for a repeated list of symbols.
  • xrocket_market_candlesGet public OHLCV candles for an exact ISO-8601 time window.
  • xrocket_market_orderbookGet a public order-book snapshot. Precision must be valid for the selected pair.
  • xrocket_market_tradesGet recent public trades for one symbol.
  • xrocket_asset_infoList public assets or inspect one exact asset identifier.
  • xrocket_ratesGet public crypto-asset rates in one fiat base currency.
  • xrocket_trade_feesGet exchange trade-fee data, optionally for repeated symbols.
  • xrocket_onboarding_linksReturn xRocket sign-in links, the local autonomous trading setup, and canonical API documentation.

Ready-to-paste client configs

Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.

CCXT

No confirmed install command for CCXT yet — follow the setup steps linked from its listing page rather than a guessed package name.

XRocket Exchange MCP

mcpServers (Claude Desktop / Cursor)
{
  "mcpServers": {
    "xrocket-exchange-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "xrocket-mcp@0.6.0"
      ]
    }
  }
}

Frequently asked questions

CCXT is categorized under Finance & Fintech and uses an install path we have not confirmed yet. XRocket Exchange MCP belongs to Finance & Fintech and uses a local stdio subprocess. Pick CCXT for finance & fintech work and XRocket Exchange MCP for finance & fintech.

Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client. CCXT has no confirmed install command yet — follow its own setup instructions.

CCXT has no declared pricing — check the project's own site. XRocket Exchange MCP has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.

Yes. MCP clients support multiple servers: add ccxt and xrocket-exchange-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.

On AllMCPs, CCXT has a quality signal of 64/100 (Good) with 2 views, 0 installs and 44,480 GitHub stars. XRocket Exchange MCP has 59/100 (Good) with 1 views, 0 installs and 0 GitHub stars.