Remote MCP · Endpoint

ULID shape check MCP server

No. ULID shape check answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/ulid-shape/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/ulid-shape
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
14 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
ULID shape check
Listing
From the official MCP registry (active).
Recent checks of ULID shape check
CheckedResultHandshake
1 hour agoHandshake completed14 ms
8 days agoHandshake completed33 ms
9 days agoHandshake completed34 ms
11 days agoHandshake completed27 ms
12 days agoHandshake completed52 ms
13 days agoHandshake completed50 ms
14 days agoHandshake completed17 ms
15 days agoHandshake completed23 ms
16 days agoHandshake completed131 ms
19 days agoHandshake completed38 ms
22 days agoHandshake completed35 ms
24 days agoHandshake completed20 ms
26 days agoHandshake completed19 ms
28 days agoHandshake completed25 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 ULID shape check and makes no claim about it beyond what these checks measured.