Remote MCP · Endpoint

Web Scan MCP server

No. Web Scan answered an MCP handshake 45 minutes ago.

UpLast checked 45 minutes ago

Server URL

https://preflight-api.agentmarket.lol/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.ankitkumarjha515/web-scan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
940 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Audit any live URL: 85 SEO, AI-search, security, leaked-key and speed checks, with fixes to verify.
Listing
From the official MCP registry (active).
Recent checks of Web Scan
CheckedResultHandshake
45 minutes agoHandshake completed940 ms
3 days agoHandshake completed771 ms
12 days agoHandshake completed703 ms
13 days agoHandshake completed255 ms
14 days agoHandshake completed772 ms
15 days agoHandshake completed1.03 s
16 days agoHandshake completed695 ms
17 days agoHandshake completed791 ms
18 days agoHandshake completed828 ms
19 days agoHandshake completed794 ms
22 days agoHandshake completed882 ms
25 days agoHandshake completed642 ms
27 days agoHandshake completed1.06 s

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

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