Remote MCP · Endpoint

costheta MCP server

No. costheta answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://costheta.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.costheta/costheta
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
519 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Verifiable physical randomness from cosmic-ray detections. Free beacon, paid signed decisions.
Listing
From the official MCP registry (active).
Recent checks of costheta
CheckedResultHandshake
1 hour agoHandshake completed519 ms
2 days agoHandshake completed485 ms
4 days agoHandshake completed380 ms
5 days agoHandshake completed362 ms
7 days agoHandshake completed400 ms
8 days agoHandshake completed404 ms
9 days agoHandshake completed382 ms
12 days agoHandshake completed504 ms
13 days agoHandshake completed395 ms
15 days agoHandshake completed378 ms
16 days agoHandshake completed532 ms
17 days agoHandshake completed352 ms
19 days agoHandshake completed360 ms
20 days agoHandshake completed365 ms
20 days agoHandshake completed356 ms
21 days agoHandshake completed371 ms
22 days agoHandshake completed705 ms

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

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