Remote MCP · Endpoint

localscreenshot MCP server

No. localscreenshot answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://api.localscreenshot.com/mcp/free

The last check completed an MCP handshake.

Registry name
com.localscreenshot/localscreenshot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Screenshot API for AI agents. Any public page as image or PDF, banners hidden, 227 countries.
Listing
From the official MCP registry (active).
Recent checks of localscreenshot
CheckedResultHandshake
1 hour agoHandshake completed303 ms
22 hours agoHandshake completed299 ms
2 days agoHandshake completed321 ms
3 days agoHandshake completed308 ms
4 days agoHandshake completed356 ms
5 days agoHandshake completed304 ms
6 days agoHandshake completed492 ms
8 days agoHandshake completed324 ms
11 days agoHandshake completed316 ms
13 days agoHandshake completed304 ms
15 days agoHandshake completed303 ms
18 days agoHandshake completed319 ms
20 days agoHandshake completed315 ms
22 days agoHandshake completed338 ms
24 days agoHandshake completed406 ms

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

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