bots.st/mitigant
Mitigant
Emulate and recover cloud attack simulations
2736 ms
answered our call
- State
- Answered
- Protocol
- MCP 2025-06-18
- Tools listed
- 12
- Answered
- 3 of the last 3 calls
How to reach it
- MCP, HTTP
https://mcp.mitigant.io/mcpNeeds header apiToken
What it can do
| Tool | What it says it does |
|---|---|
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 evidence first); calling this kicks it off immediately rather… |
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 resources along the way), so they're the lower-risk… |
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 raw records, each with an evidenceUrl that opens the matching… |
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 pre-attack state when cleanup.cleanUpComplete is true… |
get_context | Check this account's context before planning or launching: whether it is a Mitigant DEMO account and what that allows. Call this first on a new connection. If isDemo is true, every attack or scenario with allowedOnDemo=false WILL be rejected at launch -- treat those as not runnable and don't… |
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 includes scenarioName (show this to the user) alongside the… |
launch_attack | Run an attack against a cloud account connected to Mitigant. Returns the result if it finishes within wait_seconds (default 20); otherwise it returns at once with the attackId and status RUNNING while the attack keeps running -- then poll get_attack_status with that attackId, and never launch it… |
launch_scenario | Run a multi-step attack chain against a cloud account connected to Mitigant. Returns the result if every step finishes within wait_seconds (default 20); a multi-step scenario usually takes longer, so expect it to return at once with the attackId and status RUNNING while it keeps running -- then… |
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 attackName (show this to the user) and attackType (an opaque id… |
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 emulation (for that cloud, or at all), not a failure -- the account… |
list_recent_attacks | List your own recent attack and scenario runs for a cloud account, most recent first, each with its attackId and status. Use this to recover an attackId you no longer have -- for example when a launch_attack / launch_scenario call's connection dropped before it returned, or to check whether a… |
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 each scenario's scenarioName (show this to the user) and… |
In its maker's words
Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.
- Website
- mitigant.io/mcp
- Source
- github.com/mitigant/mitigant-external-api
- Publisher
- mitigant
- Listed from
- the official MCP Registry as
io.github.mitigant/mitigant-mcp - Version
- 0.1.0, updated 25 Oct 2026
- Kinds of work
- Security and trust
The domain it lives on
- mitigant.io
- registered 3 May 2020 (6 years ago), at NAMECHEAP INC, its name does not resolve now
From our own crawl of domain names: registry records and the home page as our crawler last saw it.
Every call we made
| When | What happened | Time |
|---|---|---|
| Answered | 2736 ms | |
| Answered | 2507 ms | |
| Answered | 635 ms |
Next door
- paidforAssess an x402 seller before payment
- WhisperDNS-verifiable agent networking and control
- EchelonGraph CVE & ExposureCVE and internet exposure lookups
- RevClamp MCP ServerAudits payments, disputes, and VAT compliance
- APIEmpresas: Spanish company dataKYB checks using CIF, directors, sanctions, tenders, BORME
Is this your bot? Claim its address to add a verified badge and keep the listing current.