Skip to content
MCPSTAMP
MCP server report

CryptoDataAPI MCP server

com.cryptodataapi/mcp

We checked this server on 2 November 2026 with McpStamp Check engine 1.2.0. It scored 89 of 100 (grade B), higher than 60.6% of the 33,003 registry servers that responded over HTTPS that day. Ready for Gemini and MCP Registry. Not ready for Claude and ChatGPT.

Measured facts

Score
89B
Sign-in
OAuth
Tools listed
26
Protocol version
2025-11-25
Stores

Store readiness

StoreStatusReason
Claude Connectors Directory Not ready Blocked by Human-readable title on every tool.
ChatGPT app directory Not ready Blocked by Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT) and Human-readable title on every tool.
Gemini Connected Apps Ready No blocking check failed.
Official MCP Registry Ready No blocking check failed.

MCP Registry ready means a valid public remote for the registry, not that the server is listed in a store.

Fixes

5 checks to fix

  1. Fails

    Explicit readOnlyHint, destructiveHint and openWorldHint (ChatGPT)

    tool_open_world

    Blocks ChatGPT.

    Measured 24/26 tools miss an explicit hint: check_key_status, get_market_health, get_market_regime, get_funding_rates, get_open_interest and 19 more

    Set readOnlyHint, destructiveHint and openWorldHint to explicit true/false on every tool (OpenAI app review requires all three).

  2. Fails

    Human-readable title on every tool

    tool_titles

    Blocks Claude and ChatGPT.

    Measured 26/26 without title: create_free_api_key, check_key_status, resend_verification_email, get_market_health, get_market_regime and 21 more

    Add a short human-readable "title" to every tool (shown in store UIs and consent screens).

  3. Warning

    Tool descriptions

    tool_descriptions

    Measured 1 under 60 chars: get_top_coins; 1 over 2000 chars: create_free_api_key

    Keep each tool description between 60 and 2000 characters: when to use it, what it returns, key limits.

  4. Warning

    initialize latency

    latency

    Measured 1894 ms

    Bring initialize under 1.5 s: avoid cold starts and upstream calls in the handshake.

  5. Warning

    JSON-RPC error for unknown method

    jsonrpc_errors

    Measured HTTP 401 instead of a JSON-RPC error

    Route the method first and answer unknown methods with JSON-RPC error -32601 before the auth check, or return a JSON-RPC error body with the 401.

22 checks passed

Passed. Served over HTTPS, initialize over Streamable HTTP, Supported protocol version negotiated, JSON or SSE response Content-Type, GET answers SSE or 405, serverInfo name and version, Server instructions, tools capability declared, Sign-in method the store supports (OAuth or none), 401 carries WWW-Authenticate resource_metadata, Protected resource metadata (RFC 9728), Resource metadata "resource" equals the server URL, Authorization server metadata (RFC 8414 / OIDC), First metadata URL Gemini tries answers 200 with the required fields, issuer equals the authorization_servers entry; token_endpoint_auth_methods_supported (ChatGPT), PKCE S256 advertised, Client registration (DCR or Client ID Metadata Documents), refresh_token grant advertised, tools/list returns tools, inputSchema is an object schema, Tool names are valid and portable, readOnlyHint or destructiveHint on every tool.

Run a fresh check

This page is the 2 November 2026 snapshot. If you maintain this server and have shipped fixes since then, re-check it. The live check and the badge show the current result, and the next snapshot will pick up the change.

Re-check now

Badge

README badge

The badge shows the latest score for this URL and links to this report.

McpStamp score for CryptoDataAPI

Markdown

[![McpStamp score](https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcryptodataapi.com%2Fmcp)](https://www.mcpstamp.com/r/com-cryptodataapi-mcp/)

HTML

<a href="https://www.mcpstamp.com/r/com-cryptodataapi-mcp/"><img src="https://www.mcpstamp.com/badge?url=https%3A%2F%2Fcryptodataapi.com%2Fmcp" alt="McpStamp score" height="20"></a>
Registry entry

About this server

Live crypto market data: prices, funding, OI, liquidations, regimes, GEX, whales, sentiment, macro.
Registry name
com.cryptodataapi/mcp
Remote URL
https://cryptodataapi.com/mcp
Version
1.0.0
Website
cryptodataapi.com/ai-agents/mcp-server
Checked
2 November 2026, engine 1.2.0, no credentials

The description above is the server's own text from the official MCP Registry. If a result looks wrong, run a fresh check and email support@zovo.one with the report link.

More grade B servers

All grade B servers · All server reports · State of MCP readiness, November 2026