Remote MCP · Endpoint

Cryptominium MCP server

No. Cryptominium answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://cryptominium.com/mcp

The last check completed an MCP handshake.

Registry name
com.cryptominium/cryptominium
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
585 ms
Tools exposed
8 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
What a crypto position would really sell for: measured exit costs, address and transaction lookups.
Listing
From the official MCP registry (active).
Recent checks of Cryptominium
CheckedResultHandshake
9 hours agoHandshake completed585 ms
4 days agoHandshake completed455 ms
14 days agoHandshake completed337 ms
15 days agoHandshake completed521 ms
15 days agoHandshake completed373 ms
17 days agoHandshake completed326 ms
18 days agoHandshake completed333 ms
19 days agoHandshake completed329 ms
20 days agoHandshake completed222 ms
21 days agoHandshake completed352 ms
23 days agoFailed - the request timed out—
26 days agoHandshake completed261 ms
28 days agoHandshake completed383 ms

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

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 Cryptominium and makes no claim about it beyond what these checks measured.