Remote MCP · Endpoint

URLpipe MCP server

No. URLpipe answered an MCP handshake 1 hour ago.

UpLast checked 1 hour 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
621 ms
Tools exposed
17 tools
Uptime, last 30 days
100% from 16 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
1 hour agoHandshake completed621 ms
1 day agoHandshake completed460 ms
4 days agoHandshake completed440 ms
6 days agoHandshake completed441 ms
7 days agoHandshake completed432 ms
9 days agoHandshake completed161 ms
10 days agoHandshake completed361 ms
11 days agoHandshake completed413 ms
14 days agoHandshake completed426 ms
15 days agoHandshake completed432 ms
17 days agoHandshake completed423 ms
18 days agoHandshake completed416 ms
20 days agoHandshake completed427 ms
21 days agoHandshake completed414 ms
22 days agoHandshake completed162 ms
22 days agoHandshake completed438 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 URLpipe and makes no claim about it beyond what these checks measured.