Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

CCXT

NPM · CCXT-MCP

Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets

Available components

−4 this week 84 Trust /100

Last scanned (10 hours ago)

Scores higher than 81% of npm servers

Category Crypto and Web3

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 30 of 103 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to ccxt/ccxt). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 58 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 7034 tokens (~219/item across 32 items; 32 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
  • Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage98
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 95% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 33 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 −5
    • Stability: pass → 0.63 functional
  • 28 Oct 26 +1
    • CVE-2026-109932 affects this package: high ▼ security
    • CVE-2026-109829 affects this package: high ▼ security
    • CVE-2026-87018 affects this package: high ▼ security
    • CVE-2026-109383 affects this package: high ▼ security
    • CVE-2026-87029 affects this package: high ▼ security
    • Stability: 0.97 → pass security
  • 27 Oct 26 −1
    • Stability: pass → 0.97 functional
  • 24 Oct 26 −5
    • CVE-2026-109869 affects this package: high ▼ security
    • CVE-2026-109841 affects this package: high ▼ security
    • CVE-2026-109924 affects this package: high ▼ security
    • CVE-2023-54404 affects this package: high ▼ security
    • Known CVEs: pass → fail ▼ security
  • 21 Oct 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: unverified → fail ▼ functional
  • 20 Oct 26 −1
    • Security disclosure: fail → unverified ▼ functional
    • Stability: pass → 0.97 functional
  • 17 Oct 26 +2
    • Stability: 0.83 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed npm/ccxt-mcp@0.1.3

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo ccxt/ccxt
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/ccxt/ccxt/.github/workflows/mcp-release.yml@refs/heads/master
Rekor log index 2745202908
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:5c653b4ff957a6169c91bc6dba48a4ead7b62dfc6e42c154c6c8425005e468a9ce290165c0526468f8e964b653fdd49e49c03a5aada2a4c846844daec

Background: How many MCP packages publish verified provenance →

Vulnerabilities 9 findings
ID CVE Severity Vector Fix available
GHSA-2m5v-pch6-74hx CVE-2026-109383 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-4qv8-2p9j-2685 CVE-2026-109924 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-4w7w-5xrc-9h26 CVE-2026-109829 high CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:H/A:N yes
GHSA-55wc-3pg8-jfw6 CVE-2026-87029 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9fm3-97px-rjf6 CVE-2026-109932 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-f72v-6w45-q472 CVE-2026-109841 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:N/I:H/A:N yes
GHSA-qrxm-fqhp-jwvm CVE-2026-87018 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-xjj6-f33q-929c CVE-2026-109869 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 103 packages
Packages resolved 103
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 32 exposed · ~6,455 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
call_implicit_get ~261

Call 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/

NameTypeReqDescription
accountstring–configured account name for authenticated (private/signed) GET endpoints
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
methodstringyesimplicit method name whose HTTP verb is GET, e.g. "publicGetTickerPrice" (from describe_method)
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)

No output schema declared.

No examples provided.

call_implicit_write ~204

Call an exchange-specific implicit REST endpoint over POST/PUT/DELETE/PATCH on an account with "implicitWrites" enabled — covers exchange features the unified API does not (including account/key management). No unified validation exists for raw endpoints, so every call previews and requires confirmation, and is journaled. Endpoint names: describe_method {"query": ..., "exchange": ...}; payload per the exchange API reference (describe_exchange .urls.doc).

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
methodstringyesimplicit method name with a non-GET verb, e.g. "privatePostMarginOrder"
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method

No output schema declared.

No examples provided.

call_read_method ~306

Escape 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/

NameTypeReqDescription
accountstring–configured account name — required for private reads like fetchLedger
argsarray–positional arguments per the describe_method usage line; ISO8601 strings become ms timestamps; null skips an optional argument
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
includeInfoboolean–keep the raw exchange payload inside unified structures
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap", "future", "option") — sets options.defaultType on a dedicated instance
methodstringyesunified method name matching ^(fetch|load), e.g. "fetchFundingRate"
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)

No output schema declared.

No examples provided.

call_write_method ~217

Dispatch the unified write long tail on a trading-enabled account: cancelOrders, cancelOrdersForSymbols, cancelAllOrdersAfter, setPositionMode, addMargin, reduceMargin, setMargin, borrowCrossMargin, borrowIsolatedMargin, repayCrossMargin, repayIsolatedMargin, closePosition, closeAllPositions. Always previews and requires confirmation. Batch order placement is deliberately excluded — use create_order per order so the notional caps apply. Signatures: describe_method.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
argsarray–positional arguments per describe_method; null skips an optional argument
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
methodstringyesone of the allowlisted method names
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method

No output schema declared.

No examples provided.

cancel_all_orders ~129

Cancel every open order on an account, optionally restricted to one symbol. The preview lists the orders that would be canceled.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
symbolstring–only cancel orders on this unified symbol

No output schema declared.

No examples provided.

cancel_order ~111

Cancel one open order by id. No confirmation step — canceling reduces risk and must never be blocked.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
idstringyesorder id
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
symbolstring–unified symbol (required by many exchanges)

No output schema declared.

No examples provided.

create_order ~387

Place an order on a trading-enabled account (works on prediction exchanges with outcome handles as the symbol). Validated against market precision/limits and the account's notional caps. Whether it returns a preview + confirmToken first depends on the account's "confirm" policy: always = every order is previewed; live (the default) = only orders on a LIVE account are previewed, sandbox/demo execute immediately; never = no preview. So on a sandbox/demo account under the default policy an order executes without a confirm step. A stop/trigger order also returns meta.note flagging that conditional orders may not appear in get_orders even when live — confirm before treating the stop as guaranteed protection. Use "cost" instead of "amount" to market-buy by quote value where supported. Exchange-specific order params (triggerPrice, timeInForce, postOnly, reduceOnly, …): describe_method {"method": "createOrder", "exchange": ...}.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
amountnumber–amount in base currency / contracts / shares
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
costnumber–spend this quote-currency value instead of specifying an amount (market buy/sell by cost, where the exchange supports it)
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
pricenumber–limit price — required for limit orders
sidestringyes–
symbolstringyesunified symbol (outcome handle on prediction exchanges)
typestringyesorder type — usually "limit" or "market"; exchange-specific types pass through

No output schema declared.

No examples provided.

describe_exchange ~101

One exchange's supported unified methods, market types, timeframes, required credential fields, sandbox availability and documentation URLs. Per-method detail lives in describe_method.

NameTypeReqDescription
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)

No output schema declared.

No examples provided.

describe_method ~213

Search 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/

NameTypeReqDescription
exchangestring–exchange id for per-exchange docs, feature support and implicit endpoints; when omitted a reference exchange (binance) is used, so implicit-endpoint results are binance-specific — pass "exchange" to…
methodstring–exact method name to describe, e.g. "fetchOHLCV" (or an implicit endpoint name when "exchange" is set)
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
querystring–keyword search over method names, e.g. "funding"

No output schema declared.

No examples provided.

edit_order ~190

Modify price/amount of an open order. On exchanges without native edit, ccxt emulates it as cancel-then-replace — queue position is lost and the cancel can succeed while the replace fails. Runs the full order validation and confirmation.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
amountnumber––
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
idstringyesorder id to modify
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
pricenumber––
sidestring––
symbolstringyesunified symbol of the order
typestring––

No output schema declared.

No examples provided.

get_balance ~150

Balances for a named account. Returns non-zero balances by default (exchanges report every listed currency — hundreds of zero rows).

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
marketTypestring–wallet/market type to query when the exchange has several (e.g. "spot", "swap", "future", "funding") — overrides the account default
nonzeroOnlyboolean–default true; false returns every currency
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method

No output schema declared.

No examples provided.

get_deposit_address ~135

Deposit address for a currency on a funds-enabled account (creates one where none exists and the exchange supports creation). Gated behind the funds tier because transcript-visible addresses invite substitution scams — always verify addresses out-of-band before sending funds.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
codestringyesunified currency code
networkstring–unified network code
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method

No output schema declared.

No examples provided.

get_my_trades ~148

The account's own executed trades (fills). Many exchanges require a symbol.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
limitinteger–max trades (default 50, max 200)
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
sincenumber|string–earliest entry to fetch: timestamp in ms, or an ISO8601 string like "2024-01-01T00:00:00Z"
symbolstring–unified symbol

No output schema declared.

No examples provided.

get_ohlcv ~283

Historical 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.

NameTypeReqDescription
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
limitinteger–number of candles (default 100, max 500)
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap", "future", "option") — sets options.defaultType on a dedicated instance
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
sincenumber|string–earliest entry to fetch: timestamp in ms, or an ISO8601 string like "2024-01-01T00:00:00Z"
symbolstringyesunified symbol
timeframestring–candle interval (default "1h") — valid values come from describe_exchange .timeframes

No output schema declared.

No examples provided.

get_orderbook ~212

Current order book (bids and asks) for one unified symbol.

NameTypeReqDescription
depthinteger–alias for limit (price levels per side)
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
limitinteger–price levels per side (default 20, max 100)
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap", "future", "option") — sets options.defaultType on a dedicated instance
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
symbolstringyesunified symbol — resolve with search_markets

No output schema declared.

No examples provided.

get_orders ~235

Orders for a named account: one order by id, or a list filtered by status ("open" default, "closed", "canceled", "all"). Many exchanges require a symbol for list queries.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
idstring–order id — fetches that single order
includeInfoboolean–include the raw exchange payload (single order only)
limitinteger–max orders (default 50, max 200)
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
sincenumber|string–earliest entry to fetch: timestamp in ms, or an ISO8601 string like "2024-01-01T00:00:00Z"
statusstring–"open" (default), "closed", "canceled" or "all"
symbolstring–unified symbol (required by many exchanges for list queries)

No output schema declared.

No examples provided.

get_positions ~126

Open derivatives positions for a named account (prediction-market positions on prediction exchanges).

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
marketTypestring–derivatives type to query when the exchange has several (e.g. "swap", "future") — overrides the account default
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
symbolsarray–restrict to these unified symbols

No output schema declared.

No examples provided.

get_safety_status ~50

What 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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_tickers ~214

24h price tickers for one or more unified symbols on an exchange (outcome handles on prediction exchanges).

NameTypeReqDescription
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
includeInfoboolean–include the raw exchange payload (single symbol only)
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap", "future", "option") — sets options.defaultType on a dedicated instance
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
symbolsarrayyesunified symbols, e.g. ["BTC/USDT"] — resolve with search_markets

No output schema declared.

No examples provided.

get_trades ~222

Recent public trades for one unified symbol.

NameTypeReqDescription
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
limitinteger–number of trades (default 50, max 200)
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap", "future", "option") — sets options.defaultType on a dedicated instance
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
sincenumber|string–earliest entry to fetch: timestamp in ms, or an ISO8601 string like "2024-01-01T00:00:00Z"
symbolstringyesunified symbol

No output schema declared.

No examples provided.

list_accounts ~31

Locally configured named exchange accounts. Returns aliases and capability flags only — credential values are never exposed by any tool.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_exchanges ~106

List 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.

NameTypeReqDescription
predictionboolean–true: only prediction-market exchanges; false: exclude them
querystring–case-insensitive substring match on the exchange id or name
supportsstring–keep only exchanges supporting this unified method, e.g. "fetchOHLCV"

No output schema declared.

No examples provided.

search_events ~250

Search 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.

NameTypeReqDescription
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
limitinteger–max events (default 25, max 100)
offsetinteger–pagination offset
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
querystring–keyword search (required unless tags or params.eventId/params.slug are given)
sortstring–"volume", "liquidity" or "newest"
statusstring–"active" (default), "closed" or "all"
tagsarray–filter by tags/categories

No output schema declared.

No examples provided.

search_markets ~260

Search 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.

NameTypeReqDescription
activeOnlyboolean–only active markets (default true)
basestring–base currency filter, e.g. "BTC"
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
limitinteger–max results (default 50, max 200)
offsetinteger–pagination offset
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
querystring–case-insensitive substring match on the symbol or market id
quotestring–quote currency filter, e.g. "USDT"
reloadboolean–force-refresh the markets cache
settlestring–settle currency filter (derivatives)
typestring–market type filter: "spot", "swap", "future", "option", …

No output schema declared.

No examples provided.

set_leverage ~143

Set the leverage multiplier for a derivatives symbol on a trading-enabled account. Changing leverage changes the risk of existing positions.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
leveragenumberyesleverage multiplier, e.g. 5
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
symbolstring–unified symbol (required by most exchanges)

No output schema declared.

No examples provided.

set_margin_mode ~129

Set cross or isolated margin mode for a derivatives symbol on a trading-enabled account.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
marginModestringyes–
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
symbolstring–unified symbol (required by most exchanges)

No output schema declared.

No examples provided.

transfer ~187

Move funds between wallets of the same exchange account (e.g. spot ↔ swap, main ↔ funding) on a funds-enabled account. Wallet names are exchange-specific — see describe_method {"method": "transfer", "exchange": ...}.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
amountnumberyes–
codestringyesunified currency code
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
fromAccountstringyessource wallet, e.g. "spot"
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
toAccountstringyesdestination wallet, e.g. "swap"

No output schema declared.

No examples provided.

watch_list ~51

List the currently active WebSocket subscriptions (id, exchange, method, streamKind, account and environment for private streams, args, active flag, age, seconds since last read, update count, and last error).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

watch_read ~570

Get the latest data from a stream. For a STATE stream (streamKind "state": ticker(s), order book(s), ohlcv, balance, positions, ...) it returns the COMPLETE current snapshot in "latest" — the full merged set, so call it whenever you need the current value; "updatesSinceRead" tells you how much changed since you last read. The shape of "latest" mirrors the fetch* method: a single object for watchTicker/watchOrderBook/watchBalance, keyed by symbol for watchTickers/watchBidsAsks ({"BTC/USDT": {...}}), an array for watchPositions, and nested by symbol then timeframe for watchOHLCV ("latest"["BTC/USDT"]["1m"] = [[ts,o,h,l,c,v], ...]). For an EVENT stream (streamKind "events": trades, orders, my trades, liquidations) it returns new updates oldest-first in "events" plus a "nextCursor" — thread that back as "cursor" on each poll so you do not re-receive (double-count) old items. Each "events" element is a wrapper {seq, timestamp, datetime, data} where "data" holds the record(s) for that tick (an array — ccxt delivers a batch per update, e.g. events[i].data is the trades from that tick). "moreBuffered": true means call again with nextCursor for more, and "missedBeforeBuffer" > 0 means older updates were evicted before you read them. Set waitForChange:true to BLOCK until the next update arrives (or timeout) instead of returning immediately — the efficient way to wait for a slow event like an order fill or a position change ("timedOut": true means the wait elapsed with nothing new).

NameTypeReqDescription
cursorinteger–EVENT streams only: the nextCursor from your previous watch_read (omit on the first read). Ignored for state streams.
depthinteger–order-book streams only: levels per side to return in "latest" (default 20, max 100). Use depth:1 for just top-of-book (best bid/ask) — much cheaper when comparing many venues.
subscriptionIdstringyesid from watch_subscribe
timeoutMsinteger–max time to block when waitForChange is set (default 25000, clamped to 1000–55000 — sub-second values are raised to ~1s, larger stay under host tool-call timeouts)
waitForChangeboolean–block until the next update lands (or timeoutMs elapses) instead of returning right away — use to wait for a fill/position change without polling. If something new is already available it returns imm…

No output schema declared.

No examples provided.

watch_subscribe ~592

Open a background WebSocket subscription to a ccxt.pro watch* method so the agent can pull fresh data on demand. Returns a subscriptionId and a "streamKind". STATE streams are snapshots of "what is X right now" — watchTicker(s), watchOrderBook(ForSymbols), watchOHLCV(ForSymbols), watchBalance, watchPositions, watchBidsAsks, watchMarkPrice(s), watchFundingRate(s): watch_read returns the COMPLETE current set in "latest" (the server merges live updates into a full snapshot, so a multi-symbol stream always shows every subscribed symbol, not just the one that just ticked). EVENT streams are logs of discrete events — watchTrades and the private watchOrders/watchMyTrades/watch(My)Liquidations (private ones need an account): watch_read returns each new item oldest-first in "events" with a cursor. Call watch_unsubscribe to stop; streams auto-stop after 10 minutes with no read. Not every exchange streams every method — check describe_exchange.

NameTypeReqDescription
accountstring–configured account name — required for private streams (watchOrders, watchMyTrades, watchBalance, watchPositions, watchMyLiquidations)
argsarray–positional arguments — they differ per method (get the exact signature with describe_method): e.g. watchTicker ["BTC/USDT"], watchOHLCV ["BTC/USDT","1m"], watchOrderBook ["BTC/USDT", depthLimit], wat…
exchangestringyesexchange id, e.g. "binance" — validated against ccxt.exchanges; discover ids with list_exchanges
marketTypestring–market type routing for exchanges with several (e.g. "spot", "swap")
methodstringyesa ccxt.pro watch* method, e.g. "watchOHLCV", "watchTicker", "watchOrderBook", "watchTrades"
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
predictionboolean–set true to use the prediction-markets variant of an exchange that exists in both namespaces (e.g. hyperliquid)
symbolstring–convenience alias for a single-symbol stream (watchTicker/watchOrderBook/watchTrades/watchOHLCV) — equivalent to passing it as args[0]; ignored if args is given
symbolsarray–convenience alias for a multi-symbol stream (watchTickers/watchOrderBookForSymbols/…) — equivalent to passing the list as args[0]; ignored if args is given

No output schema declared.

No examples provided.

watch_unsubscribe ~40

Stop a WebSocket subscription and release its socket. Always stop streams you no longer need.

NameTypeReqDescription
subscriptionIdstringyesid from watch_subscribe

No output schema declared.

No examples provided.

withdraw ~202

Withdraw cryptocurrency from a funds-enabled account to an external address. Irreversible once dispatched. The preview echoes the exact destination address and network — verify them before confirming.

NameTypeReqDescription
accountstringyesconfigured account name — discover with list_accounts; credentials are never tool parameters
addressstringyesdestination address
amountnumberyes–
codestringyesunified currency code, e.g. "USDT"
confirmstring–confirmation token from the preview response — repeat the identical call with this token to execute
networkstring–unified network code, e.g. "TRC20" — check describe_method {"method": "withdraw", "exchange": ...}
paramsobject–extra exchange-specific parameters passed through to ccxt unchanged (e.g. {"until": 1673000000000}) — discover supported keys with describe_method
tagstring–memo/tag where the network needs one

No output schema declared.

No examples provided.

Install

How do I install the CCXT MCP server?

CCXT runs locally as an npm package, launched with npx -y ccxt-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · ccxt-mcp

# add to Claude Code
claude mcp add ccxt-ccxt-mcp -- npx -y ccxt-mcp
Common questions

What is the CCXT MCP server?

CCXT is an MCP server listed in the public MCP registry as io.github.ccxt/ccxt-mcp. Official CCXT MCP server - Market data and trading across 100+ exchanges and prediction markets. This page covers its npm package (ccxt-mcp).

Is the CCXT MCP server safe to use?

CCXT scores 84 out of 100 on VerifyMCP. We recorded 9 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the CCXT MCP server expose?

CCXT exposes 32 tools: list_exchanges, describe_exchange, describe_method, search_markets, get_tickers, and 27 more. Their descriptions and schemas cost roughly 6,455 tokens of context every time the server is loaded.

Is the CCXT MCP server still maintained?

CCXT is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the CCXT MCP server under?

CCXT declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.