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
- 761 ms
- Tools exposed
- 5 tools
- Uptime, last 30 days
- 100% from 18 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).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 761 ms |
| 1 day ago | Handshake completed | 847 ms |
| 2 days ago | Handshake completed | 843 ms |
| 3 days ago | Handshake completed | 901 ms |
| 4 days ago | Handshake completed | 853 ms |
| 5 days ago | Handshake completed | 1.49 s |
| 6 days ago | Handshake completed | 863 ms |
| 9 days ago | Handshake completed | 839 ms |
| 12 days ago | Handshake completed | 870 ms |
| 14 days ago | Handshake completed | 870 ms |
| 16 days ago | Handshake completed | 870 ms |
| 18 days ago | Handshake completed | 873 ms |
| 20 days ago | Handshake completed | 861 ms |
| 22 days ago | Handshake completed | 866 ms |
| 24 days ago | Handshake completed | 861 ms |
| 26 days ago | Handshake completed | 866 ms |
| 27 days ago | Handshake completed | 1.19 s |
| 28 days ago | Handshake completed | 872 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 url2image and makes no claim about it beyond what these checks measured.