Remote MCP · Endpoint
SecurityScan MCP server
No. SecurityScan answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://apisecurityscan.net/mcp
The last check completed an MCP handshake.
- Registry name
- net.apisecurityscan/securityscan
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 362 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 19 checks
- Described by its publisher as
- Scan GitHub-hosted AI skills for vulnerabilities: prompt injection, malware, OWASP LLM Top 10.
- Website
- https://apisecurityscan.net/
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 362 ms |
| 1 day ago | Handshake completed | 340 ms |
| 2 days ago | Handshake completed | 379 ms |
| 3 days ago | Handshake completed | 295 ms |
| 4 days ago | Handshake completed | 318 ms |
| 5 days ago | Handshake completed | 328 ms |
| 6 days ago | Handshake completed | 283 ms |
| 8 days ago | Handshake completed | 283 ms |
| 11 days ago | Handshake completed | 326 ms |
| 13 days ago | Handshake completed | 643 ms |
| 16 days ago | Handshake completed | 426 ms |
| 18 days ago | Handshake completed | 336 ms |
| 20 days ago | Handshake completed | 390 ms |
| 22 days ago | Handshake completed | 331 ms |
| 24 days ago | Handshake completed | 392 ms |
| 26 days ago | Handshake completed | 321 ms |
| 27 days ago | Handshake completed | 561 ms |
| 29 days ago | Handshake completed | 316 ms |
| 29 days ago | Handshake completed | 305 ms |
The last 19 checks. Full history is kept for 30 days; the all-time counter stands at 29 responding of 29.
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 SecurityScan and makes no claim about it beyond what these checks measured.