{"$schema":"https://wellknown.network/schemas/agent-record-v1.json","schemaVersion":"1","id":"ag_77sszmv6h6sr","handle":"mitigant","url":"https://wellknown.network/agents/mitigant","links":{"self":"https://wellknown.network/agents/mitigant/record.json","html":"https://wellknown.network/agents/mitigant","markdown":"https://wellknown.network/agents/mitigant/record.md","api":"https://wellknown.network/api/v1/agents/mitigant","status":"https://wellknown.network/api/v1/agents/mitigant/status","claim":"https://wellknown.network/agents/mitigant/claim","claimApi":"https://wellknown.network/api/v1/claims","claimDescriptor":"https://wellknown.network/agents/mitigant/claim.json","badge":"https://wellknown.network/agents/mitigant/badge.svg","openapi":"https://wellknown.network/openapi.json","history":"https://wellknown.network/api/v1/agents/mitigant/history","tools":"https://wellknown.network/api/v1/agents/mitigant/tools"},"ard":{"identifier":"urn:air:mcp.mitigant.io:server:mitigant","type":"application/mcp-server-card+json"},"kind":"mcp_server","declared":{"name":"Mitigant","summary":"Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.","description":"Run real, auto-recovered cloud attacks on AWS, Azure and GCP to test your defenses.","publisher":{"name":"mitigant","url":null},"homepage":"https://mitigant.io/mcp","repository":"https://github.com/mitigant/mitigant-external-api","version":"0.1.0","license":null,"protocols":["mcp"],"tags":[],"pricing":null,"endpoints":[{"url":"https://mcp.mitigant.io/mcp","type":"mcp_streamable_http","auth":null,"probeable":true}],"skills":null,"tools":null,"extra":{"updatedAt":"2026-10-25T12:57:10.937397Z","publishedAt":"2026-10-25T12:57:10.937397Z","registryName":"io.github.mitigant/mitigant-mcp"},"attribution":{"kind":"mcp_registry","name":"mcp_registry","repoUrl":"mcp_registry","summary":"mcp_registry","version":"mcp_registry","description":"mcp_registry","homepageUrl":"mcp_registry","publisherName":"mcp_registry"}},"derived":{"capabilities":[{"slug":"infra.cloud","name":"Cloud Platforms","confidence":1,"provenance":"derived"},{"slug":"content.writing","name":"Writing & Editing","confidence":0.51,"provenance":"derived"}],"categories":["content","infra"],"language":"en"},"observed":{"status":"live","statusReason":"Responded 6h ago.","lastOkAt":"2026-10-30T15:25:18.393Z","lastProbedAt":"2026-10-30T15:25:18.393Z","statusComputedAt":"2026-10-30T15:27:42.160Z","reliability30d":{"probes":13,"successRate":1,"p50Ms":28,"basis":"service","measures":{"availability":"availability","latency":"response time","tools":"tool surface observed","summary":"Checks reached the service itself."},"checks":{"total":13,"ok":13,"authBoundaryOk":0,"serviceOk":13,"note":"Counted from the observation rows for the window, checks of the server only (HTTP, A2A card, MCP initialize). ok = authBoundaryOk + serviceOk. `probes` is the sum of daily rollups and includes registry checks, so it can differ from `total`."}},"latestObservations":[{"at":"2026-10-30T15:25:18.393Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":24,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-30T08:24:19.544Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":24,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-30T00:23:47.289Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":24,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-29T16:25:10.151Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":30,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-29T08:25:06.754Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":28,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-29T01:28:39.799Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":24,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-28T17:31:04.551Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":43,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-28T10:29:10.269Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":35,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-28T03:26:59.643Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":24,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}},{"at":"2026-10-27T20:28:31.978Z","kind":"mcp_initialize","ok":true,"httpStatus":200,"latencyMs":28,"error":null,"detail":{"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"toolCount":10,"toolsHash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","serverName":"mitigant-mcp-server","capabilities":["logging","tools"],"serverVersion":"0.1.0","protocolVersion":"2025-06-18"}}],"tools":[{"name":"list_attacks","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. Current"},{"name":"get_attack_details","description":"Full description, impact, MITRE mapping, and orchestration type (PROVISIONED or INLINE -- PROVISIONED attacks create and destroy their own target rather than ta"},{"name":"launch_attack","description":"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"},{"name":"list_cloud_accounts","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"},{"name":"list_scenarios","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 radi"},{"name":"get_scenario_details","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 "},{"name":"launch_scenario","description":"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"},{"name":"get_attack_status","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 a"},{"name":"clean_up_attack","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, de"},{"name":"get_attack_evidence","description":"Get the evidence Mitigant collected for a previously launched attack -- what the account's own logging (CloudTrail, GuardDuty) recorded about it. Returns an 'ev"}],"package":null,"toolSurface":{"id":"ts_c25cp77bfjp9","endpointId":"ep_3qtez32mes73","hash":"c5dd861c17c82d7ea67c033bd895a449fa823adbeaad7920c7f8dca2da64cf9a","toolCount":10,"serverName":"mitigant-mcp-server","serverVersion":"0.1.0","protocolVersion":"2025-06-18","firstSeenAt":"2026-10-26T23:23:48.932Z","lastSeenAt":"2026-10-30T15:25:18.404Z","observations":13,"toolNames":["list_attacks","get_attack_details","launch_attack","list_cloud_accounts","list_scenarios","get_scenario_details","launch_scenario","get_attack_status","clean_up_attack","get_attack_evidence"],"distinctSurfaces":1},"endpointFacts":[]},"verification":{"claimed":false,"claimedAt":null,"proofs":[]},"provenance":{"sources":[{"source":"mcp_registry","key":"io.github.mitigant/mitigant-mcp","url":"https://registry.modelcontextprotocol.io/v0/servers/io.github.mitigant%2Fmitigant-mcp","firstSeenAt":"2026-10-26T22:20:41.699Z","fetchedAt":"2026-10-30T09:22:27.931Z","normalizedAt":"2026-10-30T09:22:27.931Z"}]},"firstSeenAt":"2026-10-26T22:20:41.699Z","updatedAt":"2026-10-30T15:28:35.243Z"}