Remote MCP · Endpoint

url2image MCP server

No. url2image answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://url2image.com/mcp

The last check completed an MCP handshake.

Registry name
com.url2image/url2image
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
861 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Capture batches of public web pages in a real browser and download the screenshots as a zip.
Listing
From the official MCP registry (active).
Recent checks of url2image
CheckedResultHandshake
1 hour agoHandshake completed861 ms
2 days agoHandshake completed866 ms
4 days agoHandshake completed861 ms
5 days agoHandshake completed866 ms
7 days agoHandshake completed1.19 s
8 days agoHandshake completed872 ms
9 days agoHandshake completed909 ms
12 days agoHandshake completed691 ms
13 days agoHandshake completed869 ms
15 days agoHandshake completed889 ms
16 days agoHandshake completed1.04 s
18 days agoHandshake completed857 ms
19 days agoHandshake completed865 ms
20 days agoHandshake completed861 ms
20 days agoHandshake completed865 ms
21 days agoHandshake completed860 ms
22 days agoHandshake completed866 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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 url2image and makes no claim about it beyond what these checks measured.