Affinity
Search your CRM, prep for meetings and update deal records from your AI assistant.
Read live crypto exchange market data: prices, order books, trades, candlesticks, instrument specs.
Opens Agent Studio, where connecting is one click. The connector URL below works in any MCP client.
Paste it into any MCP client. Setup docs
The Crypto.com MCP server lets Claude, ChatGPT and any MCP client read live cryptocurrency market data from the Crypto.com Exchange in plain English. It exposes nine tools covering prices, order books, recent trades, candlestick history and instrument specifications. Every tool is annotated read-only, nothing here can trade, and no account or API key is required.
Verified connector
Listed by Anthropic as a partner connector in its Connectors Directory.
Connection checked by Agentman on .
Anthropic states this reflects the level of review a connector received, not a security audit.
Recent candlesticks for an instrument and timeframe (returns up to 50)
Index price for an instrument
Single ticker for an instrument
Mark price for an instrument
Recent trades (default 10, max 150)
List all available trading instruments
Instrument detail for an instrument by id
Tickers for an instrument or all
Order book snapshot (bids/asks)
Read from the server on 2026-08-17, including each tool's own safety annotations.
initialize response advertises four tools that do not exist. The instructions string returned on 2026-08-17 names get_widget, get_market_orderbook, get_market_trades and get_market_candles, and describes embeddable widgets. A tools/list against the same session in the same minute returned nine tools, none of them by those names. The tool list is authoritative; the instructions string is stale. It matters because a model reads instructions as guidance, so an agent may attempt a call that cannot succeed.Get_candlestick, Get_tickers, Get_ticker and Get_book. The live server returns get_candlestick, get_tickers, get_ticker and get_book. MCP tool names are case-sensitive, so code written from the directory listing would fail. The other five names match exactly.instrument_name, and Crypto.com's exchange documentation gives the form as symbols like BTCUSD-PERP. An agent that passes a plain coin name will not get an answer; call get_instruments first to resolve one.get_candlestick returns at most 50 bars, get_trades at most 150 with a documented seven-day window, and no tool returns a long-range historical series. This connector is built for the current state of the market rather than for backtesting or trend research.https://crypto.com/privacy/en entered an infinite redirect loop on 2026-08-17 (/privacy/en → /us/privacy → /privacy/privacy_us.pdf → back), exhausting the redirect limit with zero bytes returned. This page therefore makes no claim about Crypto.com's privacy terms. Crypto.com's MCP FAQ separately states the server collects no personal information, does not access conversations and requires no authentication, but that is the docs page speaking, not the policy.initialize, a notifications/initialized and a tools/list against the endpoint. Behavioural claims above come from the tool schemas, from Crypto.com's documentation, or from Crypto.com's exchange API reference, each attributed in Sources.No. Crypto.com's documentation states the Market Data MCP server is completely free and requires no account, no API key and no payment information. Our anonymous handshake against the endpoint on 2026-08-17 confirmed it: the server completed the MCP initialize exchange and returned all nine tool definitions with no credential presented and no authentication challenge returned.
No. All nine tools on this server are annotated readOnlyHint true and destructiveHint false, and no tool name, description or input schema references placing, cancelling or amending an order, or reading an account balance. Crypto.com's own documentation states the server cannot execute trades or access your personal accounts. It is a market-data feed only.
Because a repeated call genuinely returns a different answer. Idempotency describes whether a repeat call produces the same result, not whether it writes anything. Calling get_ticker twice a minute apart returns two different prices because the market moved between them. The flag correctly signals live data rather than instability, and no repeat call causes a side effect.
They are two separate reference prices for derivatives, and this server exposes one tool for each. get_index_price returns the index value, derived from prices across multiple venues for the underlying asset. get_mark_price returns the mark price, which the exchange uses to value open positions. Crypto.com's exchange documentation publishes mark price updates at roughly 50-millisecond intervals.
Not much, by design. get_candlestick's own description caps the response at 50 bars, and get_trades defaults to 10 with a maximum of 150. Crypto.com's exchange documentation adds a seven-day maximum window on recent trades. These are recent-activity endpoints, so this connector answers what is happening now rather than supporting long-range historical analysis.
An order book is the live list of unfilled buy and sell orders for one instrument. get_book returns a snapshot of it: an array of bids in descending price order and asks ascending, each level carrying a price and a quantity, plus a UTC timestamp. Crypto.com's exchange documentation caps depth at 50 levels per side.
No, and Crypto.com says so explicitly. Its documentation carries a Not Financial Advice notice stating the server provides market information only, and does not provide investment advice, trading signals or recommendations. Its features page separately lists predicting future prices among what the server does not do. Every tool returns measurements; interpretation is left entirely to you.
/docs/getting-started, /docs/claude, /docs/examples, /docs/features, /docs/faq and /docs/troubleshooting, all HTTP 200 on the same date. Sources for: the free/no-account/no-API-key statements, the Claude web, Desktop and Code setup steps and config block, the "Not Financial Advice" notice, the list of what the server cannot do, the rate-limit language, the data-source statement, and the verification and troubleshooting steps · retrieved 2026-08-17https://mcp.crypto.com/market-data/mcp — anonymous initialize (HTTP 200, no authentication challenge, serverInfo "Crypto.com Exchange MCP" 0.1.0, protocol 2025-03-26) followed by notifications/initialized (HTTP 202) and tools/list (HTTP 200, 9 tools with descriptions, input and output schemas and safety annotations), 2026-08-17. The successful anonymous exchange is what sets authVerified. No tool was called · retrieved 2025-03-26exchange-docs.crypto.com 302s here and the destination is cited). Pages used: /docs/api/rest/reference-and-market-data (the public unauthenticated market-data description, the 50-level book cap, the seven-day trade window, the shared rate-limit pool and the catalogue-caching advice), /docs/api/rest/public-get-candlestick (the twelve accepted timeframe values), /docs/api/rest/public-get-book, /docs/api/rest/public-get-tickers, /docs/api/rest/public-get-instruments (instrument symbol form and contract-specification fields), and /docs/api/websocket/ws-channel-mark-instrument-name and /ws-channel-index-instrument-name (mark price updating at roughly 50ms, and the index channel). These document the exchange endpoints the MCP tools mirror; per-tool behaviour above is attributed to the MCP schemas, not to these pages · retrieved 2026-08-17robots.txt for crypto.com (retrieved 2026-08-17, HTTP 200, genuine text). User-agent: * disallows only podcast, promo and CDN paths; the docs host is not restricted. No Content-Signal line is present on any Crypto.com host we checked, which per the Cloudflare convention neither grants nor restricts AI use. mcp.crypto.com serves no robots.txt, llms.txt or sitemap.xml (all HTTP 404 with a JSON gateway message), and the docs pages carry <meta name="robots" content="index, follow"> — the only machine-policy signal readable on that host · retrieved 2026-08-17streamable-http transport, is_authless: true, and nine tool names, four of which differ in capitalisation from the live server) · retrieved 2026-08-16robots.txt HTTP 200 and permissive, 2026-08-17). Referenced as the vendor's support route only; no claim on this page is sourced from it · retrieved 2026-08-17https://crypto.com/us/privacy and https://crypto.com/privacy/privacy_us.pdf, returning zero bytes after the redirect limit was exhausted. Nothing is cited from it · retrieved 2026-08-17Connect Crypto.com once and your agents call these tools on their own: on a schedule, in a workflow, with nobody at the keyboard.