Remote MCP · Endpoint

SecScan MCP server

No. SecScan answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://secscan.us/api/mcp

The last check completed an MCP handshake.

Registry name
us.secscan/secscan
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
174 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Scan, monitor and fix a live web app from your editor: graded security reports with fix prompts.
Listing
From the official MCP registry (active).
Recent checks of SecScan
CheckedResultHandshake
1 hour agoHandshake completed174 ms
2 days agoHandshake completed173 ms
4 days agoHandshake completed169 ms
6 days agoHandshake completed149 ms
7 days agoHandshake completed193 ms
9 days agoHandshake completed166 ms
10 days agoHandshake completed164 ms
11 days agoHandshake completed131 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed132 ms
17 days agoHandshake completed157 ms
18 days agoHandshake completed114 ms
19 days agoHandshake completed114 ms
20 days agoHandshake completed147 ms
21 days agoCredentials required—
21 days agoCredentials required—
23 days agoCredentials required—

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