Remote MCP · Endpoint

URL path only MCP server

No. URL path only answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://agent-observatory-sensor.nolimit-observatory.workers.dev/s/url-path/mcp

The last check completed an MCP handshake.

Registry name
io.github.sadri-dridi/url-path
Transport
Streamable HTTP
Protocol negotiated
2025-03-26
Handshake latency
575 ms
Tools exposed
31 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
URL path only
Listing
From the official MCP registry (active).
Recent checks of URL path only
CheckedResultHandshake
34 minutes agoHandshake completed575 ms
8 days agoHandshake completed8.46 s
9 days agoHandshake completed57 ms
11 days agoHandshake completed30 ms
12 days agoHandshake completed17 ms
13 days agoHandshake completed52 ms
14 days agoHandshake completed54 ms
14 days agoHandshake completed314 ms
16 days agoHandshake completed456 ms
19 days agoHandshake completed49 ms
21 days agoHandshake completed219 ms
24 days agoHandshake completed29 ms
26 days agoHandshake completed49 ms
28 days agoHandshake completed21 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 URL path only and makes no claim about it beyond what these checks measured.