Remote MCP · Endpoint

Sonyflake timestamp bits, value discarded MCP server

No. Sonyflake timestamp bits, value discarded answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/sonyflake-ts/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/sonyflake-ts
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
27 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 19 checks
Described by its publisher as
Sonyflake timestamp bits, value discarded
Listing
From the official MCP registry (active).
Recent checks of Sonyflake timestamp bits, value discarded
CheckedResultHandshake
1 hour agoHandshake completed27 ms
13 hours agoHandshake completed77 ms
1 day agoHandshake completed25 ms
3 days agoHandshake completed14 ms
4 days agoHandshake completed19 ms
4 days agoHandshake completed17 ms
5 days agoHandshake completed25 ms
7 days agoHandshake completed16 ms
8 days agoHandshake completed141 ms
11 days agoHandshake completed29 ms
14 days agoHandshake completed16 ms
16 days agoHandshake completed37 ms
18 days agoHandshake completed117 ms
20 days agoHandshake completed95 ms
22 days agoHandshake completed125 ms
24 days agoHandshake completed23 ms
26 days agoHandshake completed17 ms
28 days agoHandshake completed13 ms
29 days agoHandshake completed39 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 Sonyflake timestamp bits, value discarded and makes no claim about it beyond what these checks measured.