Remote MCP · Endpoint

webcap MCP server

No. webcap answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://webcap.shoutsid.fyi/mcp

The last check completed an MCP handshake.

Registry name
io.github.shoutsid-lab/webcap
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
398 ms
Tools exposed
8 tools
Uptime, last 30 days
87.5% from 16 checks
Described by its publisher as
Screenshot, extract or audit any URL. Paid per call in USDC over x402; free tools need no wallet.
Listing
From the official MCP registry (active).
Recent checks of webcap
CheckedResultHandshake
1 hour agoHandshake completed398 ms
1 day agoFailed - the server returned an HTTP error—
4 days agoHandshake completed360 ms
6 days agoHandshake completed351 ms
7 days agoHandshake completed313 ms
9 days agoHandshake completed302 ms
10 days agoHandshake completed325 ms
11 days agoFailed - the request timed out—
14 days agoHandshake completed302 ms
15 days agoHandshake completed383 ms
17 days agoHandshake completed304 ms
18 days agoHandshake completed295 ms
20 days agoHandshake completed285 ms
21 days agoHandshake completed305 ms
22 days agoHandshake completed292 ms
22 days agoHandshake completed340 ms

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

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