CryptoDataAPI
com.cryptodataapi/mcp · 1.0.0
Live crypto market data: prices, funding, OI, liquidations, regimes, GEX, whales, sentiment, macro.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 60 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 15 of 15 | The registry entry declares a key or a token. |
| Latest connection test reached it | 20 of 20 | The latest test had its handshake answered. |
Where it answers
https://cryptodataapi.com/mcpstreamable-httpX-API-Keyoptional, secret: Optional. Omit to sign in via OAuth browser login (free tier, no card). Or pass a cdk_live_ key from https://cryptodataapi.com/login for headless use.
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 26 tools.
- Protocol
- 2025-06-18
- Calls itself
- cryptodataapi 1.28.1
- Handshake time
- 656 ms
- HTTP status
- 200
The tools it lists (26, as of 3 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
create_free_api_keyCreate a FREE CryptoDataAPI key (no signup, no payment) — call this FIRST if you don't have a key yet. No API key is required to call this. ASK THE USER FOR THEIR REAL EMAIL — do not invent one, and do not reuse a placeholder. A confirmation link is sent to that address, and clicking it upgrades the SAME key in place: 100 -> 1,000 requests/day, Pro switched on for 24 hours (per-coin quant regimes, gamma, whale activity and liquidation heatmaps across every coin). An address the user cannot open means they keep the 100/day starter limit and lose both. The full
check_key_statusCheck the current API key: tier, rate limits, requests used today, and whether its email is verified. Call this after a 429, or whenever the user asks what their plan includes. IMPORTANT — if `email_verified` is false, TELL THE USER what `upgrade_message` says: confirming the emailed link raises this same key from 100 to 1,000 requests/day and switches Pro on for 24 hours (per-coin quant, gamma, whales, liquidation heatmaps across every coin). It applies to the key they already have — nothing to re-install. Use resend_verification_email if they can't find the l
resend_verification_emailRe-send the confirmation link for the current key's email address. Use when the user wants the higher free rate limit (1,000/day), the 24-hour Pro trial but can't find the original email. Tell them to check their inbox — the unlock applies to the key already in use, so there is nothing to re-install afterwards.
get_market_healthOverall crypto market health: the dual long-term/short-term health score with all 11 components (breadth, funding, sentiment, derivatives, etc.) and a flat `indicators` summary. Use this for a one-call read on how healthy the market is right now.
get_market_regime
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
com.cryptodataapi/mcp, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 29 days ago. The registry entry · cryptodataapi.com