Remote MCP · Endpoint

Utility 137 MCP server

No. Utility 137 answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/util-137
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
19 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
Small public utility for autonomous clients.
Listing
From the official MCP registry (active).
Recent checks of Utility 137
CheckedResultHandshake
1 day agoHandshake completed19 ms
3 days agoHandshake completed16 ms
5 days agoHandshake completed22 ms
6 days agoHandshake completed51 ms
8 days agoHandshake completed105 ms
9 days agoHandshake completed16 ms
12 days agoHandshake completed12 ms
13 days agoHandshake completed42 ms
15 days agoHandshake completed29 ms
16 days agoHandshake completed18 ms
17 days agoHandshake completed17 ms
19 days agoHandshake completed20 ms
19 days agoHandshake completed154 ms
20 days agoHandshake completed32 ms
21 days agoHandshake completed13 ms
23 days agoHandshake completed13 ms

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

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 137 and makes no claim about it beyond what these checks measured.