Mitigant
io.github.mitigant/mitigant-mcp · v0.1.0 · MCP 2025-11-25
Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.
Reachability
reachable
checked 2026-10-26 05:30 UTC
Registry status active
Tools pinned 10
c9135f0d78b7
Tools last changed
unchanged since first capture 2026-10-26
Provenance
Registry namespace io.github.mitigant
(GitHub-account verified by the official registry)
Repository
github.com/mitigant/mitigant-external-api
repo gone
Website
https://mitigant.io/mcp
Remote endpoints
https://mcp.mitigant.io/mcp (streamable-http)
Observed changes
| When (UTC) | Event | Detail |
|---|---|---|
| 2026-10-26 05:30 | first capture | 10 tools pinned |
Pinned tool definitions (10)
| Tool | Description |
|---|---|
| list_attacks | Browse Mitigant's attack actions -- atomic tests that each emulate one attacker technique -- that you can launch on their own against AWS, Azure or GCP. Currently 111 attack actions (AWS 49, Azure 36, GCP 26). Returns each action's... |
| get_attack_details | Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than targeting your existing infrastructure (they may still read or use existing... |
| launch_attack | Run an attack against a cloud account connected to Mitigant and return the result once it finishes. This performs real actions on real cloud infrastructure -- it is not a simulation. Confirm with the user before calling: if their... |
| list_cloud_accounts | List the cloud accounts available for attack emulation -- any account not listed here cannot be attacked, so check this before guessing an account_no for launch_attack. An empty result means no accounts are onboarded for attack... |
| list_scenarios | List Mitigant's attack scenarios -- multi-step chains that combine several attack actions run in sequence, so treat a scenario as having the combined blast radius of every step. Currently 45 scenarios (AWS 26, Azure 12, GCP 7). Returns... |
| get_scenario_details | Full details for one attack scenario -- description, impact, and the step-by-step composition, by the scenario key from list_scenarios. A scenario runs several attacks in sequence; this returns every step, not just the first. Result... |
| launch_scenario | Run a multi-step attack chain against a cloud account connected to Mitigant and return the result once every step finishes. This performs real actions on real cloud infrastructure, as several attacks in sequence -- it is not a... |
| get_attack_status | Get the current report for a previously launched attack, including its clean-up state. Returns the attack report plus a 'cleanup' summary with cleanUpComplete and a plain-language statement. Only tell the user the account is back to its... |
| clean_up_attack | Clean up a previously launched attack, restoring the cloud resources it changed back to their pre-attack state. Clean-up is normally AUTOMATIC after a short, deliberate inspection window (so the team can verify the attack and collect... |
| get_attack_evidence | Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'evidence' summary (counts, sources, and a plain-language statement) plus the... |
Get alerted when this changes.
Email the moment io.github.mitigant/mitigant-mcp drifts, dies, or revives.
Status badge
[](https://toolpin.dev/servers/io.github.mitigant/mitigant-mcp)
Maintain this server? Add the badge to your README. It links your users to this live status page.