Ext Ops Panel
Open dashboard
Comparison

com.stackhawk/stackhawk vs ThreatLocker MCP

com.stackhawk/stackhawk is an MCP server published by stackhawk.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). ThreatLocker MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). As of our marketplace pass on 2026-10-14. 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
Marketplacecom.stackhawk/stackhawkThreatLocker MCP
Official MCP Registry Listed
Version: 1.1.1
Downloads/month (PyPI): 160
Downloads/week (PyPI): 47
Forks (GitHub): 8
Stars (GitHub): 9
Not marked · First seen
Listed
Version: 0.3.8
Forks (GitHub): 12
Stars (GitHub): 59
Not marked · First seen
Docker MCP Catalog Listed
Version: sha256:f5c273bf008b
Forks (GitHub): 8
Pulls (Docker Hub): 31 286
Stars (Docker Hub): 0
Stars (GitHub): 9
Not marked · First seen
Not listed

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

com.stackhawk/stackhawk vs ThreatLocker MCP
Factcom.stackhawk/stackhawkThreatLocker MCP
Marketplaces that list it22
Stars (GitHub) (differs)9 (worse)59 (better)
Pulls (Docker Hub) (differs)31 286No figure on Docker Hub
Forks (GitHub) (differs)8 (worse)12 (better)
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (stackhawk-mcp)On your machine (https://github.com/Servosity/msp-skills/releases/download/threatlocker-v0.3.8/threatlocker-mcp.mcpb)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 15, secrets among them: 2
Licence (differs)NOASSERTIONApache-2.0
Repository (differs)github.com/stackhawk/stackhawk-mcpgithub.com/servosity/msp-skills
Changes in the last 7 days (differs)04
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

com.stackhawk/stackhawk

In its own words, on Official MCP Registry:

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

ThreatLocker MCP

In its own words, on Official MCP Registry:

Every ThreatLocker Portal API feature, plus the write operations the read-only tools lack and a

How to run each

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)

ThreatLocker MCP As a Claude Code plugin

Claude Code
/plugin marketplace add servosity/msp-skills
/plugin install threatlocker@msp-skills

Requires: PRINTING_PRESS_CLIENT_PROFILE (secret), THREATLOCKER_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 ThreatLocker MCP publish no list of tools, so we do not compare tools.

Settings each asks for

Only com.stackhawk/stackhawk asks for

  • STACKHAWK_API_KEY (secret)

Only ThreatLocker MCP asks for

  • PRINTING_PRESS_CLIENT_PROFILE (secret)
  • THREATLOCKER_API_KEY (secret)
  • THREATLOCKER_BASE_URL
  • THREATLOCKER_ORG_ID
  • THREATLOCKER_USER_AGENT

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: com.stackhawk/stackhawk · What it can do: ThreatLocker MCP · Compare two other plugins

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. Data comes from public marketplace files in GitHub repositories of their authors. 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