Remote MCP · Endpoint

Utility 123 MCP server

No. Utility 123 answered an MCP handshake 17 minutes ago.

UpLast checked 17 minutes ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/util-123/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/util-123
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
31 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Small public utility for autonomous clients.
Listing
From the official MCP registry (active).
Recent checks of Utility 123
CheckedResultHandshake
17 minutes agoHandshake completed31 ms
9 days agoHandshake completed87 ms
9 days agoHandshake completed27 ms
11 days agoHandshake completed32 ms
12 days agoHandshake completed21 ms
13 days agoHandshake completed27 ms
14 days agoHandshake completed16 ms
15 days agoHandshake completed26 ms
16 days agoHandshake completed172 ms
19 days agoHandshake completed16 ms
22 days agoHandshake completed33 ms
24 days agoHandshake completed18 ms
26 days agoHandshake completed68 ms
28 days agoHandshake completed17 ms

The last 14 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 Utility 123 and makes no claim about it beyond what these checks measured.