{"id":"io.github.mitigant/mitigant-mcp","slug":"io-github-mitigant-mitigant-mcp","title":"Mitigant","description":"Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.","version":"0.1.0","publisher":{"kind":"github","id":"mitigant","label":"@mitigant on GitHub","url":"https://github.com/mitigant"},"website":"https://mitigant.io/mcp","repository":"https://github.com/mitigant/mitigant-external-api","remotes":[{"type":"streamable-http","url":"https://mcp.mitigant.io/mcp","headers":[{"description":"Your Mitigant API key, generated in the Mitigant web app under Settings -> Application Keys. The server scopes every call to that key's organization and role.","isRequired":true,"isSecret":true,"name":"apiToken"}]}],"packages":[],"published":"2026-10-25","updated":"2026-10-25","status":"online","auth":"","latency_ms":1047,"checked":"2026-11-19","uptime":100,"checks":3,"tools":[{"name":"list_attacks","title":"","description":"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 128 attack actions (AWS 66, Azure 36, GCP 26). Returns each action's attackName (show this to the user) and attackType (an opaque id -- pass this, not attackName, to get_attack_details or launch_attack), what it does, its impact, the MIT","read_only":true},{"name":"get_attack_details","title":"","description":"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, production-viable choice; INLINE attacks find and attack an existing resource in the account) for one attack, by ","read_only":true},{"name":"launch_attack","title":"","description":"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 again (that would start a second attack). This performs real actions on real cloud infrastructure -- it","read_only":false},{"name":"list_cloud_accounts","title":"","description":"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 may still exist in Mitigant for other purposes (e.g. posture scanning) without being eligible here. Each","read_only":true},{"name":"list_scenarios","title":"","description":"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 50 scenarios (AWS 31, Azure 12, GCP 7). Returns each scenario's scenarioName (show this to the user) and scenarioKey (an opaque id -- pass this, not scenarioName, to get_scenario_details or launch_scenario), plus","read_only":true},{"name":"get_scenario_details","title":"","description":"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 scenarioKey you passed in (an opaque id, not for display).","read_only":true},{"name":"launch_scenario","title":"","description":"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 poll get_attack_status with that attackId, and never launch it again (that would start a second scenario","read_only":false},{"name":"get_attack_status","title":"","description":"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 -- while anything is pending or failed, clean-up is not done, so report it as in progress and check again rat","read_only":true},{"name":"list_recent_attacks","title":"","description":"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 long-running scenario is still running or has failed -- then pass the attackId to get_attack_status, get_a","read_only":true},{"name":"get_context","title":"","description":"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 attempt them; use list_attacks' allowedOnDemo field (or list_scenarios demo_only:true) to pick ones that ru","read_only":true},{"name":"clean_up_attack","title":"","description":"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 than waiting out that window. It is NOT a fix for a stall, and it ends that window early -- removing the","read_only":false},{"name":"get_attack_evidence","title":"","description":"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 console entry. Use it to show the user what their defenses saw, especially during the clean-up inspecti","read_only":true},{"name":"list_threat_actors","title":"","description":"List every real-world threat actor Mitigant's catalog tracks (name, description, references, other names the actor is known by with the source of each, and the tools it uses). Not scoped to a cloud service. Use this to find an actor's exact name (e.g. 'Storm-0940', 'Scattered Spider') before calling get_attacks_by_threat_actor, or to summarize what an actor is known for directly from its descripti","read_only":true},{"name":"get_attacks_by_threat_actor","title":"","description":"Find the managed attacks that demonstrate a named threat actor's real techniques, for one cloud service -- e.g. 'which Azure attacks demonstrate Scattered Spider', or to plan a red team exercise around one actor's known behavior. Get the actor's exact name from list_threat_actors first. Each result includes the same fields as list_attacks, plus matchedThreatActorTechniques: exactly which of that a","read_only":true},{"name":"list_adversary_tools","title":"","description":"List the tools and frameworks attackers use that Mitigant's catalog tracks, for example the AI attack framework ARTEX, Pacu, AADInternals, ROADTools, Peirates and AndroxGh0st. Each has a name, description, references, whether it is AI-driven (agentic), and the threat actors reported to use it. A tool is not an attack on its own: to run attacks that reproduce what a tool is reported to do, take its","read_only":true},{"name":"get_attacks_by_adversary_tool","title":"","description":"Find the managed attacks that reproduce what a named adversary tool is reported to do, for one cloud service -- e.g. 'which AWS attacks reproduce ARTEX', or 'run what Pacu does'. The tool itself is not an attack; these are the attacks whose technique is one the tool is reported to use. Get the exact name from list_adversary_tools first. Each result includes the same fields as list_attacks, plus ma","read_only":true}],"server_info":{"name":"mitigant-mcp-server","title":"Mitigant","version":"0.1.0","description":"Run real, automatically-cleaned-up cloud attacks against AWS, Azure, and GCP to test your defenses, and see what your logging recorded about each one.","websiteUrl":"https://mitigant.io"},"category":"cloud","tags":["security"],"kind":"remote","source":"registry","submitted":{},"first_party":false,"domain_rank":null,"score":100,"indexable":true,"first_seen":"2026-10-25","stars":0,"badges":["new"],"sponsor":null,"page":"https://agentsindex.org/agents/io-github-mitigant-mitigant-mcp/"}