io.github.mitigant/mitigant-mcp
up checked
Unclaimed · Unverified
Agent searches it appeared in, last 30 days: 0. Run this server? Claim the listing: verified label, uptime alerts and analytics.
Publisher-provided title
Mitigant
Publisher-provided description
Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.
Summary by lookupd
Launches automated, self-cleaning attack emulations on connected cloud accounts and retrieves the resulting logs and evidence for defense…
Install
Claude Code, remote (streamable-http)
claude mcp add --transport http mitigant https://mcp.mitigant.io/mcp
Codex, remote (streamable-http)
codex mcp add mitigant --url https://mcp.mitigant.io/mcp
Cursor, remote (streamable-http) → .cursor/mcp.json
{
"mcpServers": {
"mitigant": {
"url": "https://mcp.mitigant.io/mcp"
}
}
}Other clients: docs. Or tell your agent: Set up lookupd for me: read https://lookupd.com/agent.md and follow it.
Tools (14 tools)
Publisher-provided text
list_attacksBrowse Mitigant's attack actions -- atomic tests that each emulate one attacker technique -- that you can launch on their own against AWS, Azure or GCP. Currentget_attack_detailsFull description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than talaunch_attackRun 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 wilist_cloud_accountsList the cloud accounts available for attack emulation -- any account not listed here cannot be attacked, so check this before guessing an account_no for launchlist_scenariosList Mitigant's attack scenarios -- multi-step chains that combine several attack actions run in sequence, so treat a scenario as having the combined blast radiget_scenario_detailsFull details for one attack scenario -- description, impact, and the step-by-step composition, by the scenario key from list_scenarios. A scenario runs severallaunch_scenarioRun 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 multiget_attack_statusGet the current report for a previously launched attack, including its clean-up state. Returns the attack report plus a 'cleanup' summary with cleanUpComplete alist_recent_attacksList 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 noget_contextCheck 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 iclean_up_attackClean 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, deget_attack_evidenceGet the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'evlist_threat_actorsList every real-world threat actor Mitigant's catalog tracks (name, description, references). Not scoped to a cloud service. Use this to find an actor's exact nget_attacks_by_threat_actorFind the managed attacks that demonstrate a named threat actor's real techniques, for one cloud service -- e.g. 'which Azure attacks demonstrate Scattered Spide
Details
- Version: 0.1.0
- Transports: streamable-http
- Uptime (7 days): 100%
- Median latency: 567 ms
- First indexed:
- Last seen in registry:
- Repository: https://github.com/mitigant/mitigant-external-api
- Website: https://mitigant.io/mcp
Badge for your README
Shows this live status and links here; updates hourly.
[](https://lookupd.com/servers/io.github.mitigant/mitigant-mcp)
- 62033 servers
- Last crawl: 2026-11-11T15:38:39.561Z
- API base:
https://api.lookupd.com - MCP URL:
https://api.lookupd.com/mcp