CryptoKeyhole
REMOTE · CRYPTOKEYHOLE.COM
Read-only on-chain and market crypto analytics for Bitcoin, Ethereum and more, from our own nodes.
Available components
Last scanned (11 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 22 Oct 2026.
Category Crypto and Web3
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability43
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1246 tokens (~207/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage72
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 16% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 22 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “fetch_metric” rewrote its description, which is the text the model reads security
- Tool “get_asset_metrics” rewrote its description, which is the text the model reads security
- Tool “get_assets_list” rewrote its description, which is the text the model reads security
- Tool “get_metrics_list” rewrote its description, which is the text the model reads security
- Schema quality: 179 → 207 ▼ functional
- Stability: unverified → 0.03 ▲ functional
- 21 Oct 26 66
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 22 Oct 2026 · Probed https://cryptokeyhole.com/api/v1/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cryptokeyhole.com | CN=YE1,O=Let's Encrypt,C=US | 23 Sept 2026 | 22 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6339d58587aa41a3f11372d1a6242509d5c |
| SANs: *.cryptokeyhole.com, cryptokeyhole.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of cryptokeyhole.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cryptokeyhole.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: https://*.google-analytics.com https://*.googletagmanager.com; font-src 'self'; connect-src 'self' https://*.google-analytics.com https://*.analytics.google.com https://*.googletagmanager.com; object-src 'none'; base-uri 'self'; frame-ancestors 'none'; form-action 'self' |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cryptokeyhole.com/api/v1/mcp | Verified | 200 | |
| http (plaintext) | http://cryptokeyhole.com/api/v1/mcp | HTTPS enforced | 301 | https://cryptokeyhole.com/api/v1/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
fetch_bulk_metrics Fetch bulk metrics ~64
Read multiple metric selections sequentially. Each item retains its own provenance and revision; this is not one atomic snapshot. Unsupported selections are explicit per-item errors. The existing 200000-observation and response-byte bounds apply to the combined result.
| Name | Type | Req | Description |
|---|---|---|---|
| requests | array | yes | – |
No output schema declared.
No examples provided.
fetch_metric Fetch metric ~295
Read exact unreduced BTC, ETH, SOL, XRP, TRX, BNB, DOGE, TON, LINK, HYPE, WBTC, ADA, NEAR, XLM, BCH, LTC, UNI, AVAX, SUI, HBAR, WLD, WLFI, LIT, MNT, SHIB, QNT, ENA, MORPHO, AAVE, ONDO, DOT, ZRO, PEPE, SKY, ARB, FF, POL, APT, CRV, ZAMA, SENT, ETHFI, PENDLE, ENS, FET, LDO, EIGEN, SPX, EDGE, IMX, AXS, BAT, GRT, SYRUP, FLOKI, COMP, SAND, APE, PROM, ALT, GALA, NIL or ERA observations with decimal strings, original source clocks, revision, finality and gaps. End is exclusive. Metric-specific interval and retained-publication restrictions apply. No new observation is acquired.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| end | integer | – | Exclusive UNIX seconds UTC. |
| interval | string | – | – |
| metric | string | yes | – |
| publication | string | – | An actual retained publication ID; only supported metric/interval pairs accept it. |
| sma | integer | – | – |
| smoothing | string | – | – |
| start | integer | – | Inclusive UNIX seconds UTC. |
No output schema declared.
No examples provided.
get_asset_metrics Get asset metrics ~217
Discover the available and held metrics of one asset: BTC, ETH, SOL, XRP, TRX, BNB, DOGE, TON, LINK, HYPE, WBTC, ADA, NEAR, XLM, BCH, LTC, UNI, AVAX, SUI, HBAR, WLD, WLFI, LIT, MNT, SHIB, QNT, ENA, MORPHO, AAVE, ONDO, DOT, ZRO, PEPE, SKY, ARB, FF, POL, APT, CRV, ZAMA, SENT, ETHFI, PENDLE, ENS, FET, LDO, EIGEN, SPX, EDGE, IMX, AXS, BAT, GRT, SYRUP, FLOKI, COMP, SAND, APE, PROM, ALT, GALA, NIL or ERA.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | yes | – |
| category | string | – | – |
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
get_assets_list Get assets list ~184
List active analytics assets: BTC, ETH, SOL, XRP, TRX, BNB, DOGE, TON, LINK, HYPE, WBTC, ADA, NEAR, XLM, BCH, LTC, UNI, AVAX, SUI, HBAR, WLD, WLFI, LIT, MNT, SHIB, QNT, ENA, MORPHO, AAVE, ONDO, DOT, ZRO, PEPE, SKY, ARB, FF, POL, APT, CRV, ZAMA, SENT, ETHFI, PENDLE, ENS, FET, LDO, EIGEN, SPX, EDGE, IMX, AXS, BAT, GRT, SYRUP, FLOKI, COMP, SAND, APE, PROM, ALT, GALA, NIL and ERA.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_metric_metadata Get metric metadata ~39
Read the current metric definition, supported intervals, method, coverage and source limitations.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| metric | string | yes | – |
No output schema declared.
No examples provided.
get_metrics_list Get metrics list ~239
Discover metrics for one asset (BTC by default; ETH, SOL, XRP, TRX, BNB, DOGE, TON, LINK, HYPE, WBTC, ADA, NEAR, XLM, BCH, LTC, UNI, AVAX, SUI, HBAR, WLD, WLFI, LIT, MNT, SHIB, QNT, ENA, MORPHO, AAVE, ONDO, DOT, ZRO, PEPE, SKY, ARB, FF, POL, APT, CRV, ZAMA, SENT, ETHFI, PENDLE, ENS, FET, LDO, EIGEN, SPX, EDGE, IMX, AXS, BAT, GRT, SYRUP, FLOKI, COMP, SAND, APE, PROM, ALT, GALA, NIL or ERA) by existing category, including honest held and delayed states. Cursor pages follow the current catalogue and are not an immutable snapshot.
| Name | Type | Req | Description |
|---|---|---|---|
| asset | string | – | – |
| category | string | – | – |
| cursor | string | – | – |
| limit | integer | – | – |
No output schema declared.
No examples provided.
How do I install the CryptoKeyhole MCP server?
CryptoKeyhole is a hosted endpoint at https://cryptokeyhole.com/api/v1/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · cryptokeyhole.com
claude mcp add --transport http com-cryptokeyhole-analytics 'https://cryptokeyhole.com/api/v1/mcp'
What is the CryptoKeyhole MCP server?
CryptoKeyhole is an MCP server listed in the public MCP registry as com.cryptokeyhole/analytics. Read-only on-chain and market crypto analytics for Bitcoin, Ethereum and more, from our own nodes. This page covers its hosted endpoint (https://cryptokeyhole.com/api/v1/mcp).
Is the CryptoKeyhole MCP server safe to use?
CryptoKeyhole scores 66 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CryptoKeyhole MCP server expose?
CryptoKeyhole exposes 6 tools: get_assets_list, get_metrics_list, get_asset_metrics, get_metric_metadata, fetch_metric, fetch_bulk_metrics. Their descriptions and schemas cost roughly 1,038 tokens of context every time the server is loaded.
Does the CryptoKeyhole MCP server require authentication?
No. We connected to CryptoKeyhole without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CryptoKeyhole MCP server still maintained?
CryptoKeyhole is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.