Remote MCP · Endpoint

Fletcher-32 hex length, input discarded MCP server

No. Fletcher-32 hex length, 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/fletcher-len/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/fletcher-len
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
30 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Fletcher-32 hex length, input discarded
Repository
https://github.com/sadri-dridi/named-mcp-utilities
Listing
From the official MCP registry (active).
Recent checks of Fletcher-32 hex length, input discarded
CheckedResultHandshake
1 hour agoHandshake completed30 ms
20 hours agoHandshake completed21 ms
2 days agoHandshake completed43 ms
3 days agoHandshake completed27 ms
4 days agoHandshake completed32 ms
5 days agoHandshake completed30 ms
6 days agoHandshake completed20 ms
8 days agoHandshake completed5.69 s
11 days agoHandshake completed159 ms
13 days agoHandshake completed51 ms
15 days agoHandshake completed81 ms
18 days agoHandshake completed26 ms
20 days agoHandshake completed17 ms
22 days agoHandshake completed18 ms
24 days agoHandshake completed31 ms
26 days agoHandshake completed16 ms
27 days agoHandshake completed29 ms
29 days agoHandshake completed35 ms

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

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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Fletcher-32 hex length, input discarded and makes no claim about it beyond what these checks measured.