Remote MCP · Endpoint

CurlShot MCP server

No. CurlShot answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://curlshot.com/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.SergiuPogor/curlshot
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
368 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Screenshots of any public web page as PNG, JPEG, WebP, PDF or a scrolling video.
Listing
From the official MCP registry (active).
Recent checks of CurlShot
CheckedResultHandshake
56 minutes agoHandshake completed368 ms
3 days agoHandshake completed364 ms
12 days agoHandshake completed369 ms
13 days agoHandshake completed381 ms
14 days agoHandshake completed3.01 s
15 days agoHandshake completed407 ms
17 days agoHandshake completed681 ms
18 days agoHandshake completed420 ms
18 days agoHandshake completed365 ms
20 days agoHandshake completed472 ms
22 days agoHandshake completed404 ms
25 days agoHandshake completed396 ms
27 days agoHandshake completed617 ms
29 days agoHandshake completed417 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 16 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 CurlShot and makes no claim about it beyond what these checks measured.