Remote MCP · Endpoint

URLpipe MCP server

No. URLpipe answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://urlpipe.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.urlpipe/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
362 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Read any page with its JavaScript run: Markdown, screenshots, metadata, console errors, Lighthouse.
Listing
From the official MCP registry (active).
Recent checks of URLpipe
CheckedResultHandshake
56 minutes agoHandshake completed362 ms
3 days agoHandshake completed446 ms
12 days agoHandshake completed485 ms
13 days agoHandshake completed471 ms
15 days agoHandshake completed432 ms
15 days agoHandshake completed448 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed465 ms
18 days agoHandshake completed227 ms
20 days agoHandshake completed458 ms
22 days agoHandshake completed149 ms
25 days agoHandshake completed439 ms
27 days agoHandshake completed459 ms
29 days agoHandshake completed466 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 URLpipe and makes no claim about it beyond what these checks measured.