Crypto.com

Limits

• This is market data, not advice. Crypto.com's documentation carries an explicit "Not Financial Advice" notice stating the server provides market information only and does not provide investment advice, trading signals or recommendations, and directs readers to do their own research and consult a financial advisor. Its examples page adds that the server cannot predict future prices. We reflect that unsoftened: this page describes what the tools return and nothing more.
• The server's own 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.
• The directory listing capitalises four tool names that are lowercase on the server. Anthropic's snapshot records 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.
• Everything is instrument-scoped, and the instrument names are exchange symbols. Seven of the nine tools require an 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.
• Coverage is one exchange, not the whole market. Crypto.com's features page states the data comes from Crypto.com's own exchange market data. Prices, volumes and books reflect that venue. The index price is the only figure documented as drawing on prices across multiple venues.
• History is shallow. 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.
• Rate limits exist but are not published as a number. Crypto.com's FAQ says there are no strict limits for normal use, that very high-frequency requests may be rate-limited, and that normal conversational use is never limited. Its exchange documentation adds that public endpoints share a global rate-limit pool and recommends caching the instrument catalogue rather than polling. Its Claude guide documents a "Rate limit exceeded" error with a five-to-ten-minute wait as the remedy. No numeric ceiling is published for the MCP server, so an agent polling in a loop should back off on its own rather than rely on one.
• The tools return strings, not numbers. Every price, quantity and volume field in the output schemas is typed as a string, and many ticker fields are nullable. Code consuming these responses needs to parse and null-check rather than assume numeric types.
• The privacy policy in Anthropic's directory listing could not be read. The published URL 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.
• We did not exercise any MCP tool. Our check was an anonymous 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.

Frequently asked questions

Sources

• Crypto.com Market Data MCP documentation (retrieved 2026-08-17, HTTP 200, zero redirects; the URL Anthropic's directory publishes). Six further pages were fetched from its own hrefs and sidebar: /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-17
• Live MCP handshake against https://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-26
• Crypto.com Exchange API v1 documentation (retrieved 2026-08-17, HTTP 200; the directory-era host exchange-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-17
• robots.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-17
• Anthropic Connectors Directory entry (from the 2026-08-16 directory snapshot; partner tier, financial-services category, streamable-http transport, is_authless: true, and nine tool names, four of which differ in capitalisation from the live server) · retrieved 2026-08-16
• Crypto.com support centre (the support URL Anthropic's directory publishes; robots.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-17
• Crypto.com privacy policy (the URL Anthropic's directory publishes). Not retrieved: on 2026-08-17 it entered an infinite redirect loop via https://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-17