Remote MCP · Endpoint

SHAKE128 hex length band, input discarded MCP server

No. SHAKE128 hex length band, input discarded answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/shake128-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/shake128-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
22 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
SHAKE128 hex length band, input discarded
Listing
From the official MCP registry (active).
Recent checks of SHAKE128 hex length band, input discarded
CheckedResultHandshake
1 hour agoHandshake completed22 ms
11 hours agoHandshake completed252 ms
1 day agoHandshake completed97 ms
2 days agoHandshake completed242 ms
4 days agoHandshake completed443 ms
4 days agoHandshake completed56 ms
5 days agoHandshake completed54 ms
6 days agoHandshake completed47 ms
8 days agoHandshake completed41 ms
11 days agoHandshake completed37 ms
14 days agoHandshake completed14 ms
16 days agoHandshake completed29 ms
18 days agoHandshake completed22 ms
20 days agoHandshake completed29 ms
22 days agoHandshake completed815 ms
24 days agoHandshake completed18 ms
26 days agoHandshake completed16 ms
28 days agoHandshake completed18 ms
29 days agoHandshake completed30 ms

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

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 SHAKE128 hex length band, input discarded and makes no claim about it beyond what these checks measured.