# CryptoKeyhole (remote · cryptokeyhole.com)

Read-only on-chain and market crypto analytics for Bitcoin, Ethereum and more, from our own nodes.

- Trust score: 66/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- remote · `cryptokeyhole.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp.md), [page](https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp)

## Channel facts

- Endpoint: `https://cryptokeyhole.com/api/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-22.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 43/100
  - AI-judged instruction clarity (fair).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 72/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 16% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### 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.

### Claude

```bash
claude mcp add --transport http com-cryptokeyhole-analytics 'https://cryptokeyhole.com/api/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-cryptokeyhole-analytics": {
      "url": "https://cryptokeyhole.com/api/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-cryptokeyhole-analytics": {
      "type": "http",
      "url": "https://cryptokeyhole.com/api/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-cryptokeyhole-analytics]
url = "https://cryptokeyhole.com/api/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-cryptokeyhole-analytics": {
      "type": "remote",
      "url": "https://cryptokeyhole.com/api/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-cryptokeyhole-analytics --url 'https://cryptokeyhole.com/api/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-cryptokeyhole-analytics:
    url: "https://cryptokeyhole.com/api/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-cryptokeyhole-analytics": {
      "Transport": "http",
      "Url": "https://cryptokeyhole.com/api/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-cryptokeyhole-analytics -t streamable-http -u 'https://cryptokeyhole.com/api/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-cryptokeyhole-analytics": {
      "type": "http",
      "url": "https://cryptokeyhole.com/api/v1/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-22 (score 66, 0)

- [security] 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
- [functional regression] Schema quality: 179 → 207
- [functional improvement] Stability: unverified → 0.03

### 2026-10-21 (score 66)

First indexed and scored.

## MCP tools (6)

### `get_assets_list` (~184 tokens)

Get assets list

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.

### `get_metrics_list` (~239 tokens)

Get metrics list

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.

Input parameters:

- `asset` (string)
- `category` (string)
- `cursor` (string)
- `limit` (integer)

### `get_asset_metrics` (~217 tokens)

Get asset metrics

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.

Input parameters:

- `asset` (string, required)
- `category` (string)
- `cursor` (string)
- `limit` (integer)

### `get_metric_metadata` (~39 tokens)

Get metric metadata

Read the current metric definition, supported intervals, method, coverage and source limitations.

Input parameters:

- `asset` (string)
- `metric` (string, required)

### `fetch_metric` (~295 tokens)

Fetch metric

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.

Input parameters:

- `asset` (string)
- `end` (integer): Exclusive UNIX seconds UTC.
- `interval` (string)
- `metric` (string, required)
- `publication` (string): An actual retained publication ID; only supported metric/interval pairs accept it.
- `sma` (integer)
- `smoothing` (string)
- `start` (integer): Inclusive UNIX seconds UTC.

### `fetch_bulk_metrics` (~64 tokens)

Fetch bulk metrics

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.

Input parameters:

- `requests` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp#diagnostics

## Score history

- 2026-10-22: 66
- 2026-10-21: 66

## Common questions

### 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.

## Links

- Remote endpoint: https://cryptokeyhole.com/api/v1/mcp
- Website: https://cryptokeyhole.com/mcp/
- Changelog RSS feed: https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-cryptokeyhole-analytics/api-v1-mcp