Mitigant

Name: Mitigant
Author: mitigant

MCP serverMCP

Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.

by mitigantrepository ↗homepage ↗v0.1.0

Is this yours?

This record is unclaimed

Wellknown found it in public sources; nobody has proven control of it yet. Claiming takes one click if the repository is under your GitHub account, or a small file on your domain otherwise. Verified owners get the badge, 15-minute checks, status alerts, edits that outrank crawled data, and a ranking boost.

Agents can do it too: POST https://wellknown.network/api/v1/claims with {"agent":"mitigant","method":"well_known_file"} — machine-readable steps at claim.json, guide at /docs/claim.

Claim this record

Observed by Wellknown

Evidence

Everything here was measured by our prober or read from a registry. Nothing is self-reported.

30-day availability13/13 checks ok

30 days ago

when	check	result	http	latency	detail
5 h ago	mcp initialize	ok	200	24 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
12 h ago	mcp initialize	ok	200	24 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
20 h ago	mcp initialize	ok	200	24 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
28 h ago	mcp initialize	ok	200	30 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	28 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	24 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	43 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
2 d ago	mcp initialize	ok	200	35 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
3 d ago	mcp initialize	ok	200	24 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools
3 d ago	mcp initialize	ok	200	28 ms	server mitigant-mcp-server 0.1.0 · protocol 2025-06-18 · 10 tools

Tools observed via MCP handshake

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. Current
get_attack_details — Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta
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 -- i
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
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 radi
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
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 c
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 a
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, de
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 'ev

Declared by sources

What the publisher says

Attributed to the source that supplied each field. Treated as claims, not facts.

No long description beyond the summary.

kind Official MCP Registry

name Official MCP Registry

repoUrl Official MCP Registry

summary Official MCP Registry

version Official MCP Registry

description Official MCP Registry

homepageUrl Official MCP Registry

publisherName Official MCP Registry

Provenance

Where this record came from

Every source is kept verbatim. Field changes are logged as events.

Official MCP Registryio.github.mitigant/mitigant-mcp

first seen 4 d ago · fetched 11 h agoopen ↗

Field history (7 recent events)

4 d ago · declared · summary → "Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses."
4 d ago · declared · description → "Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses."
4 d ago · declared · publisherName → "mitigant"
4 d ago · declared · homepageUrl → "https://mitigant.io/mcp"
4 d ago · declared · repoUrl → "https://github.com/mitigant/mitigant-external-api"
4 d ago · declared · version → "0.1.0"
4 d ago · declared · protocols → ["mcp"]

This record is unclaimed

Evidence

What the publisher says

Capabilities

Where this record came from