Remote MCP · Endpoint

Priority u=/i= pair count, value discarded MCP server

No. Priority u=/i= pair count, 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/priority-ok/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/priority-ok
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
38 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Priority u=/i= pair count, value discarded
Listing
From the official MCP registry (active).
Recent checks of Priority u=/i= pair count, value discarded
CheckedResultHandshake
1 hour agoHandshake completed38 ms
18 hours agoHandshake completed69 ms
2 days agoHandshake completed19 ms
3 days agoHandshake completed15 ms
4 days agoHandshake completed28 ms
5 days agoHandshake completed32 ms
6 days agoHandshake completed23 ms
8 days agoHandshake completed314 ms
11 days agoHandshake completed24 ms
13 days agoHandshake completed22 ms
15 days agoHandshake completed64 ms
18 days agoHandshake completed15 ms
20 days agoHandshake completed157 ms
22 days agoHandshake completed14 ms
24 days agoHandshake completed22 ms
26 days agoHandshake completed16 ms
27 days agoHandshake completed14 ms
29 days agoHandshake completed31 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 Priority u=/i= pair count, value discarded and makes no claim about it beyond what these checks measured.