Remote MCP · Endpoint

Snap Screenshots MCP server

No. Snap Screenshots answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://snap.i2dev.com/mcp

The last check completed an MCP handshake.

Registry name
com.i2dev/snap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
120 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Screenshot any public web page from an AI agent. Free without signup, or with an API key.
Listing
From the official MCP registry (active).
Recent checks of Snap Screenshots
CheckedResultHandshake
1 hour agoHandshake completed120 ms
2 days agoHandshake completed40 ms
4 days agoHandshake completed45 ms
6 days agoHandshake completed107 ms
8 days agoHandshake completed41 ms
10 days agoHandshake completed173 ms
12 days agoHandshake completed36 ms
14 days agoHandshake completed35 ms
16 days agoHandshake completed102 ms
17 days agoHandshake completed125 ms
18 days agoHandshake completed176 ms
20 days agoHandshake completed53 ms
22 days agoHandshake completed44 ms
24 days agoHandshake completed40 ms

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

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