com.stackhawk/stackhawk vs SSO Auth Bridge
com.stackhawk/stackhawk is an MCP server published by stackhawk.com. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). SSO Auth Bridge is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). 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
| Marketplace |  com.stackhawk/stackhawk | |
|---|---|---|
| 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: 1.0.0 No figure published 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
| Fact | com.stackhawk/stackhawk | SSO Auth Bridge |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 9 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 31 286 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 8 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (stackhawk-mcp) | Remote server (sso-auth-bridge-mcp.vercel.app/api/mcp) |
| Transport (differs) | stdio | SSE |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/stackhawk/stackhawk-mcp | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Answered with HTTP 402 (43 h ago) |
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
An MCP server that provides interaction with StackHawk's security scanning platform.
SSO Auth Bridge
SAML and OIDC authentication integration orchestrator.
How to run each
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)
SSO Auth Bridge As a remote MCP server
claude mcp add --transport sse sso-auth-bridge https://sso-auth-bridge-mcp.vercel.app/api/mcp --header "payment-signature: <YOUR_PAYMENT_SIGNATURE>"Requires: payment-signature header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SSO Auth Bridge has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of SSO Auth Bridge publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of SSO Auth Bridge publish no settings it asks for, so we do not compare settings.
What it can do: com.stackhawk/stackhawk · What it can do: SSO Auth Bridge · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.