Crypto.com AI Tools
Official Crypto.com CLI/MCP server for exchange trading, plus a hosted keyless market-data MCP.
- Sato Score81
Crypto.com AI Tools is an open-source MCP server by Crypto.com, with last code activity on 2026-07-28 (Recent). Latest release on 2026-06-18. Sato Score 81/100 (how open, active and verifiable it is, not a safety grade), as of 2026-10-15. How the score works →
See how to install Crypto.com AI Tools →Last commit Jul 28, 2026 · Last release Jun 18, 2026 · ★ 26
Listed from mcp.crypto.com on 2026-07-13. Install: not attempted. Evidence →
Next step
Watch Crypto.com AI Tools
One email if what we observe changes — its repo goes quiet or disappears, or the listing is retired. Nothing else.
Check it from your agent
Add Sato Hub’s MCP server (no key), then ask:
https://satohub.ai/api/mcpRun Sato Hub Preflight on crypto-com/cdcx-cli before I use it.Your project?
Prove you control the domain and correct this page — description, links, tags, chains. A claim proves control, not verification: it never changes the Sato Score.
Claim this listing →Overview
cdcx-cli is Crypto.com's official unified CLI, MCP server, and terminal dashboard for the Crypto.com Exchange API — 95 REST endpoints, WebSocket streaming, paper trading, and configurable safety tiers from read-only to live trading, with 13 agent skill files. Alongside it, Crypto.com hosts a separate keyless Market Data MCP server (mcp.crypto.com) exposing live prices, market caps, and trading volumes with no API key or setup required.
Sato Score
81/100· HighHow open, active & verifiable — not a safety or returns grade.
- Maintenance & liveness
- 35/35
- Code transparency
- 18/20
- Interface verifiability
- 10/10
- Docs & demo
- 6/10
- Listing transparency & provenance
- 12/15
- Independent verification
- 0/10
Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety).
Evidence — listed vs checked · what the words mean
Listed from mcp.crypto.com on 2026-07-13. Install: not attempted.
| Claim | Value | Evidence | Source | Checked |
|---|---|---|---|---|
| Chains supported | not stated | self-reported | mcp.crypto.com | as of 2026-10-15 |
| Verification status | Self-Reported — not independently reviewed | self-reported | mcp.crypto.com | as of 2026-10-15 |
| Recent activity | last release 2026-06-18 · last commit 2026-07-28 | observed | github.com/crypto-com/cdcx-cli | 2026-10-15 |
| Install works | documented by the project, not run by Sato Hubnot attempted by Sato Hub | self-reported | github.com/crypto-com/cdcx-cli | as of 2026-07-14 |
| MCP endpoint answers | answered — 9 tools listed | observed | mcp.crypto.com | 2026-10-15 |
| Daily check record | 22 of 44 daily checks since 2026-09-01 succeededa success rate of our checks, not uptime; the source is this listing's own history | observed | — | 2026-10-14 |
| Deploys as | Install script (curl | sh) or cargo installconfidence 0.85 | self-reported | github.com/crypto-com/cdcx-cli | as of 2026-07-14 |
| Works with | Claude Code, Cursor, Claude Desktop, Codex, GitHub Copilot, Gemini CLIconfidence 0.85 | self-reported | github.com/crypto-com/cdcx-cli | as of 2026-07-14 |
| Sato Score | 81/100 (High)how open, active and verifiable — not a safety or quality grade | computed | satohub.ai | 2026-10-15 |
Self-reported rows are the project’s own words, dated when we recorded them — not a check. Only reproduced and reviewed rows carry a mark. None of these rows is a safety or quality rating.
Install — as documented by the project, not run by us
Runtime: cli
curl -sSfL https://raw.githubusercontent.com/crypto-com/cdcx-cli/main/install.sh | sh cdcx mcp config --enable trade,account (registers cdcx as an MCP tool server; also usable as a plain CLI and terminal dashboard)
You supply: CDCX_API_KEY / CDCX_API_SECRET for live trading (public market data and paper trading work without credentials)
MCP invocation: cdcx mcp config --enable trade,account
Read from the project’s own docs as of 2026-07-14. What a deploy spec is →
Tool inventory — 9 tools, probed live 2026-10-15
get_tickers— Tickers for an instrument or allget_trades— Recent trades (default 10, max 150)get_ticker— Single ticker for an instrumentget_mark_price— Mark price for an instrumentget_candlestick— Recent candlesticks for an instrument and timeframe (returns up to 50)get_instruments— List all available trading instrumentsget_instrument— Instrument detail for an instrument by idget_book— Order book snapshot (bids/asks)get_index_price— Index price for an instrument
- Answers a handshake
- yes · 2026-10-15
- Answers a call
- yes — get_tickers returned in 711 ms
Live probe verifies the interface responds — not what the tools do, their safety, or their output quality. The call is one read-only tool named by this server's own list (list_/get_/search_, no mutating verb anywhere in the name, no required arguments and none that look like a key, an address or an amount), asked once a day with no arguments. Not asked is not a failure.
Observed record — 91 daily checks since 2026-07-17
- Succeeded
- 25
- Failed
- 66
- Their error
- 22
- Unattributed
- 44
State changed on 2026-07-19 (responding → unclear), 2026-09-01 (unclear → failing), 2026-09-23 (failing → responding).
This is the share of our daily checks that succeeded — not an availability guarantee. A check can fail because the host was down, because our runner timed out, or because the network in between dropped it, and only the first of those is a fact about this project. Failures are split by what we can attribute; anything we cannot attribute is counted, not hidden. 46 of these checks predate 2026-09-01, when the probe counted a bot-block (HTTP 403) as a failure and recorded no reason for any failure. The rate above leaves those checks out; the counts include them.
Last 30 days — to 2026-10-15, one point per UTC day
A gap is a day we have no attributable observation — never a zero. Thirty points is the whole shape the free layer carries; the daily rows behind it stay in the snapshot series.
Details
- Chains
- Unknown
- Agent types
- MCP Server, Trading
- Open source
- Yes
- Pricing
- Free
- Deploys as
- Install script (curl | sh) or cargo install
- Works with
- Claude Code, Cursor, Claude Desktop, Codex, GitHub Copilot, Gemini CLI
- Last checked
- 2026-10-15
Marketplace Signals
No marketplace signals recorded for this resource yet.
Verification status reflects evidence reviewed by Sato Hub. Self-reported claims are never presented as verified.
Where Crypto.com AI Tools fits
Related concepts: How Agents Interact With Smart Contracts, How Agents Use Wallets, What Are MCPs? The Standard Way to Give Agents Tools
Listing History
Recorded changes to Crypto.com AI Tools's listing — status, verification, Sato Score, and recent releases. Full history is kept in the listing record.
- Sep 23, 2026Sato Score tier: Medium → HighScore 61 → 81.
- Aug 27, 2026Sato Score tier: High → MediumScore 71 → 61.
- Aug 11, 2026Sato Score tier: Medium → HighScore 61 → 71.
- Jul 20, 2026Edited: mcp endpoint url
- Jul 19, 2026Edited: mcp endpoint url
- Jul 18, 2026Sato Hub began tracking this listing
- Jul 14, 2026Auto-enriched: deployment options, supported integrations
- Jul 13, 2026Listed on Sato Hub
Compared with
Appears in
Related Resources
Trust Wallet Agent Kit (TWAK)
ActiveNon-custodial toolkit from Trust Wallet (MCP server, CLI, and SDK) that lets AI agents read and transact across 25+ chains within user-defined rules.
Phantom MCP
ActivePhantom's MCP server that lets AI agents view addresses, sign transactions, swap, and transfer tokens across Solana, Ethereum, Bitcoin, and Sui.
OpenSea Agent Skill
ActiveOfficial OpenSea agent skill and MCP server letting AI agents query NFT/token data and execute marketplace operations such as listing, offers, and token swaps.
Reference
QuestionsWhat people ask about this pageShowHide
Questions people ask about Crypto.com AI Tools
- Is Crypto.com AI Tools open source?
- Yes. Crypto.com AI Tools is open source under the Apache-2.0 license; the repository is https://github.com/crypto-com/cdcx-cli. Checked as of 2026-10-15.
- Which chains does Crypto.com AI Tools support?
- Sato Hub has no confirmed chain list for Crypto.com AI Tools as of 2026-10-15; treat chain support as unknown.
- Is Crypto.com AI Tools still maintained?
- The most recent code activity Sato Hub observed was on 2026-07-28 (last commit 2026-07-28, last release 2026-06-18), which Sato Hub labels "Recent". Posts on X are not counted as maintenance. Activity is a recency signal, not a quality judgment.
- How do I install or run Crypto.com AI Tools?
- cli. Install: curl -sSfL https://raw.githubusercontent.com/crypto-com/cdcx-cli/main/install.sh | sh. Entry: cdcx mcp config --enable trade,account (registers cdcx as an MCP tool server; also usable as a plain CLI and terminal dashboard). This is taken from the project's own documentation and has not been reproduced by Sato Hub. It runs as an MCP server (cdcx mcp config --enable trade,account).
- Is Crypto.com AI Tools verified on Sato Hub?
- Sato Hub holds one earned check for Crypto.com AI Tools: Live endpoint probed — we called the hosted MCP endpoint and it answered with its real tool inventory (proves the interface works, not runtime safety). Its Sato Score is 81 of 100, a measure of how open, active and verifiable the project is, not a safety, quality or returns grade.
Cite this pagePlain text, APA or BibTeXShowHide
Cite this page
Sato Hub. "Crypto.com AI Tools — Sato Hub." Sato Hub, updated 2026-10-15, accessed 2026-10-15. https://satohub.ai/resources/crypto-com-aiData last refreshed 2026-10-15; this page is rebuilt daily. Citations carry the date so a reader can tell which snapshot a claim came from. Catalog data is licensed CC-BY-4.0.
Join the Sato Hub Briefing
Sign up for the Briefing: the agents, tools, and infrastructure that actually shipped, and why they matter.