Remote MCP · Endpoint

UTF-1 signature bytes, input discarded MCP server

No. UTF-1 signature bytes, 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/utf1-sig/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/utf1-sig
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
55 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
UTF-1 signature bytes, input discarded
Listing
From the official MCP registry (active).
Recent checks of UTF-1 signature bytes, input discarded
CheckedResultHandshake
1 hour agoHandshake completed55 ms
17 hours agoHandshake completed21 ms
2 days agoHandshake completed108 ms
3 days agoHandshake completed16 ms
4 days agoHandshake completed17 ms
5 days agoHandshake completed16 ms
6 days agoHandshake completed164 ms
8 days agoHandshake completed130 ms
11 days agoHandshake completed379 ms
13 days agoHandshake completed127 ms
15 days agoHandshake completed98 ms
18 days agoHandshake completed16 ms
20 days agoHandshake completed82 ms
22 days agoHandshake completed917 ms
24 days agoHandshake completed17 ms
26 days agoHandshake completed12 ms
27 days agoHandshake completed28 ms
29 days agoHandshake completed23 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.

Listing data comes from the official MCP registry. Glide is not affiliated with UTF-1 signature bytes, input discarded and makes no claim about it beyond what these checks measured.