Ext Ops Panel
Open dashboard
Comparison

compliance-checks vs com.stackhawk/stackhawk

compliance-checks is a plugin bundle for AI coding tools published by cyberagentic. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-13. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplacecompliance-checkscom.stackhawk/stackhawk
Claude Code: claude-plugins-community Listed
Version: c5d5a7d
No figure published
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.1
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 270
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

compliance-checks vs com.stackhawk/stackhawk
Factcompliance-checkscom.stackhawk/stackhawk
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub9
Pulls (Docker Hub) (differs)No figure on Docker Hub31 270
Forks (GitHub) (differs)No figure on GitHub8
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (stackhawk-mcp)
Transport (differs)Not statedstdio
Tools it declares (differs)Not published7
Environment variables it asks for (differs)Not published1, secrets among them: 1
Licence (differs)Not statedNOASSERTION
Repository (differs)github.com/cyberagentic/compliance-checksgithub.com/stackhawk/stackhawk-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

compliance-checks

In its own words, on Claude Code: claude-plugins-community:

EU regulatory compliance checks for businesses. Assess whether your organisation is affected by NIS-2, classify AI systems under the EU AI Act, check GDPR compliance before introducing new applications, review technical security measures (TOMs), and audit data processing agreements. Each check asks a few targeted questions and produces a structured report with a clear risk rating and actionable next steps.

com.stackhawk/stackhawk

In its own words, on Official MCP Registry:

An MCP server that provides interaction with StackHawk's security scanning platform.

How to run each

compliance-checks

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 Code
claude mcp add --env "STACKHAWK_API_KEY=<YOUR_STACKHAWK_API_KEY>" --transport stdio stackhawk -- uvx stackhawk-mcp

Requires: 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 compliance-checks publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of compliance-checks publish no settings it asks for, so we do not compare settings.

What it can do: compliance-checks · What it can do: com.stackhawk/stackhawk · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built