dhi.io/stackhawk-mcp
StackHawk MCP Server
A Model Context Protocol server that connects AI assistants and LLM-powered IDEs to the StackHawk application security testing platform.
pushed 14 hours ago
linux/amd64, linux/arm64
40.68 MB
for linux/amd64
144
for linux/amd64
Active support
-
Build Level 3
Tamper-evident proof of how and from what sources this image was built. Build Level 3 is the highest the SLSA build track defines.
CycloneDX SBOM + SPDX SBOM
A software bill of materials in both CycloneDX and SPDX formats so it drops straight into your existing tooling. Audit exactly what you're shipping.
A Vulnerability Exploitability exchange document, Docker's assessment of which CVEs actually affect this image and which don't apply, so you can focus on real risk instead of chasing false positives.
Available
A link to everything used to build the image, package source code, Git repos, and build files, so you can audit or reproduce the build and stay compliant with open source licenses.
Every known vulnerability in this image, shown in full rather than hidden. The VEX data flags which ones actually apply, so you can tell real exposure from noise before you ship.
Exactly what changed in this build, down to the package bumps and fixes behind the version you're pulling.
Verifies no keys, tokens, or credentials were accidentally baked into the image.
The image layers were scanned for known malware signatures before publishing.
About StackHawk MCP Server
The StackHawk MCP Server is a Model Context Protocol (MCP) server that connects AI coding assistants and LLM-powered IDEs to the StackHawk application security testing platform. It exposes StackHawk's dynamic application security testing (DAST) capabilities as MCP tools so that AI assistants can help set up scanning, run security scans, and triage findings directly from a developer's workflow.
The server provides tools to:
- Set up StackHawk scanning for a project
- Run dynamic application security scans
- Triage and review vulnerability findings
- Validate StackHawk YAML configuration files against the official schema
Configuration
The server authenticates to StackHawk using an API key supplied through the STACKHAWK_API_KEY environment variable.
This value is a secret and must be provided at runtime; it is never baked into the image. The optional
STACKHAWK_BASE_URL environment variable can be used to point at a different StackHawk endpoint.
The server communicates over the MCP standard input/output (stdio) transport, which is the deployment model used by MCP clients such as Claude Desktop, Cursor, and GitHub Copilot.
For more details, see the upstream project.
About Docker Hardened Images
Docker Hardened Images are built to meet the highest security and compliance standards. They provide a trusted foundation for containerized workloads by incorporating security best practices from the start.
Why use Docker Hardened Images?
These images are published with near-zero known CVEs, include signed provenance, and come with a complete Software Bill of Materials (SBOM) and VEX metadata. They're designed to secure your software supply chain while fitting seamlessly into existing Docker workflows.
Trademarks
This listing is prepared by Docker. All third-party product names, logos, and trademarks are the property of their respective owners and are used solely for identification. Docker claims no interest in those marks, and no affiliation, sponsorship, or endorsement is implied.