Remote MCP · Endpoint

CryptoKeyhole MCP server

No. CryptoKeyhole answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://cryptokeyhole.com/api/v1/mcp

The last check completed an MCP handshake.

Registry name
com.cryptokeyhole/analytics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
528 ms
Tools exposed
18 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only market and on-chain data for Bitcoin, Ethereum and more; on-chain from our own nodes.
Listing
From the official MCP registry (active).
Recent checks of CryptoKeyhole
CheckedResultHandshake
42 minutes agoHandshake completed528 ms
3 days agoHandshake completed1.03 s
12 days agoHandshake completed416 ms
12 days agoHandshake completed375 ms
14 days agoHandshake completed683 ms
15 days agoHandshake completed1.24 s
16 days agoHandshake completed406 ms
17 days agoHandshake completed397 ms
18 days agoHandshake completed177 ms
19 days agoHandshake completed395 ms
22 days agoHandshake completed625 ms
25 days agoHandshake completed657 ms
27 days agoHandshake completed526 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with CryptoKeyhole and makes no claim about it beyond what these checks measured.