Remote MCP · Endpoint
Mitigant MCP server
No. Mitigant answered an MCP handshake 19 minutes ago.
UpLast checked 19 minutes ago
Server URL
https://mcp.mitigant.io/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.mitigant/mitigant-mcp
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 158 ms
- Tools exposed
- 16 tools
- Uptime, last 30 days
- 100% from 12 checks
- Described by its publisher as
- Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.
- Website
- https://mitigant.io/mcp
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 19 minutes ago | Handshake completed | 158 ms |
| 3 days ago | Handshake completed | 133 ms |
| 14 days ago | Handshake completed | 151 ms |
| 14 days ago | Handshake completed | 167 ms |
| 15 days ago | Handshake completed | 141 ms |
| 16 days ago | Handshake completed | 138 ms |
| 18 days ago | Handshake completed | 147 ms |
| 18 days ago | Handshake completed | 134 ms |
| 19 days ago | Handshake completed | 143 ms |
| 21 days ago | Handshake completed | 395 ms |
| 22 days ago | Handshake completed | 127 ms |
| 25 days ago | Handshake completed | 124 ms |
The last 12 checks. Full history is kept for 30 days; the all-time counter stands at 12 responding of 12.
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 Mitigant and makes no claim about it beyond what these checks measured.