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).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 174 ms |
| 2 days ago | Handshake completed | 173 ms |
| 4 days ago | Handshake completed | 169 ms |
| 6 days ago | Handshake completed | 149 ms |
| 7 days ago | Handshake completed | 193 ms |
| 9 days ago | Handshake completed | 166 ms |
| 10 days ago | Handshake completed | 164 ms |
| 11 days ago | Handshake completed | 131 ms |
| 14 days ago | Handshake completed | 127 ms |
| 15 days ago | Handshake completed | 132 ms |
| 17 days ago | Handshake completed | 157 ms |
| 18 days ago | Handshake completed | 114 ms |
| 19 days ago | Handshake completed | 114 ms |
| 20 days ago | Handshake completed | 147 ms |
| 21 days ago | Credentials required | — |
| 21 days ago | Credentials required | — |
| 23 days ago | Credentials 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.