incident-response-playbook-creator vs com.stackhawk/stackhawk
incident-response-playbook-creator is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑22.
incident-response-playbook-creator is a plugin bundle for AI coding tools published by Diego Consolini. No marketplace we read lists it any more. com.stackhawk/stackhawk is an MCP server published by stackhawk.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-22. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace |  com.stackhawk/stackhawk | |
|---|---|---|
| Community marketplace diegocconsolini/claudeskillcollection | Removed on 2026-10-22 Version: 2.2.0 Forks (GitHub): 0 Stars (GitHub): 7 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.1.1 Downloads/month (PyPI): 160 Downloads/week (PyPI): 47 Forks (GitHub): 8 Stars (GitHub): 9 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:f5c273bf008b Forks (GitHub): 8 Pulls (Docker Hub): 31 361 Stars (Docker Hub): 0 Stars (GitHub): 9 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | incident-response-playbook-creatorno longer listed · | com.stackhawk/stackhawk |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 2 |
| Stars (GitHub) (differs) | 7 | 9 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 31 361 |
| Forks (GitHub) (differs) | 0 | 8 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (stackhawk-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 7 |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence (differs) | MIT | NOASSERTION |
| Repository (differs) | github.com/diegocconsolini/claudeskillcollection | github.com/stackhawk/stackhawk-mcp |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-16 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of incident-response-playbook-creator
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Generate NIST CSF 2.0-aligned cybersecurity policies for small and mid-size businesses. Five production-ready generators (Acceptable Use, Incident Response, Password & MFA, Data…
-
Production incident response system with incident management workflows, intelligent debugging, runbook automation, and postmortem generation. Handles incident detection, triage…
-
The compliance specialist your AI calls: ISO 27001, SOC 2, GDPR, NIS 2, DORA and more.
-
Create professional playbooks, SOPs, and Scribe-style step guides with process maps and agent-executable SOP files.
-
Generate structured incident reports and post-mortems
-
Production incident management, triage workflows, and automated incident resolution
What each says it does
incident-response-playbook-creator
Professional incident response playbook generator based on NIST SP 800-61r3 (April 2025). Creates comprehensive, customized IR documentation for ransomware, data breach, and phishing incidents with GDPR Article 33/34 and HIPAA breach notification guidance. Includes NIST CSF 2.0 function mapping and 110KB of authoritative reference data.
com.stackhawk/stackhawk
An MCP server that provides interaction with StackHawk's security scanning platform.
How to run each
incident-response-playbook-creator
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
com.stackhawk/stackhawk As a local MCP server: PyPI package
claude mcp add --env "STACKHAWK_API_KEY=<YOUR_STACKHAWK_API_KEY>" --transport stdio stackhawk -- uvx stackhawk-mcpRequires: STACKHAWK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of incident-response-playbook-creator publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of incident-response-playbook-creator publish no settings it asks for, so we do not compare settings.
What it can do: incident-response-playbook-creator · What it can do: com.stackhawk/stackhawk · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.