OWASP ZAP MCP Server vs Zscaler Zero Trust Exchange
OWASP ZAP MCP Server is an MCP server published by pierre3. Marketplaces we read that list it: 1 (Official MCP Registry). Zscaler Zero Trust Exchange is an MCP server published by zscaler. Marketplaces we read that list it: 5 (Official MCP Registry, Claude Code: claude-plugins-official, Docker MCP Catalog, Claude Code: claude-plugins-community, Community GitHub marketplaces). As of our marketplace pass on 2026-11-07. 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 | ||
|---|---|---|
| Official MCP Registry | Listed Version: 1.1.0 Forks (GitHub): 0 Stars (GitHub): 4 Not marked · First seen |
Listed Version: 0.15.4 Downloads/month (PyPI): 1 348 Downloads/week (PyPI): 2 399 Forks (GitHub): 34 Stars (GitHub): 55 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.15.4 Forks (GitHub): 34 Stars (GitHub): 55 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:a3951ea456e1 Forks (GitHub): 34 Pulls (Docker Hub): 7 540 Stars (Docker Hub): 0 Stars (GitHub): 55 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.15.0 Forks (GitHub): 34 Stars (GitHub): 55 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 | OWASP ZAP MCP Server | Zscaler Zero Trust Exchange |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 5 (better) |
| Stars (GitHub) (differs) | 4 (worse) | 55 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 7 540 |
| Forks (GitHub) (differs) | 0 (worse) | 34 (better) |
| Last release (differs) | Not published | 2026-11-04 |
| Where it runs (differs) | On your machine (dotnet-zap-mcp) | On your machine (zscaler-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 302 |
| Environment variables it asks for (differs) | 2, secrets among them: 0 | 10, secrets among them: 5 |
| Parts of the bundle (differs) | Not a bundle | 28 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/pierre3/dotnet-zap-mcp | github.com/zscaler/zscaler-mcp-server |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen | 2026-10-11 | 2026-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
OWASP ZAP MCP Server
MCP server for OWASP ZAP vulnerability scanning with Docker management
Zscaler Zero Trust Exchange
Manage Zscaler Zero Trust Exchange via 400+ tools — ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.
How to run each
OWASP ZAP MCP Server
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Zscaler Zero Trust Exchange As a local MCP server: PyPI package
claude mcp add --env "ZSCALER_CLIENT_ID=<YOUR_ZSCALER_CLIENT_ID>" --env "ZSCALER_CLIENT_SECRET=<YOUR_ZSCALER_CLIENT_SECRET>" --env "ZSCALER_CUSTOMER_ID=<YOUR_ZSCALER_CUSTOMER_ID>" --env "ZSCALER_VANITY_DOMAIN=<YOUR_ZSCALER_VANITY_DOMAIN>" --transport stdio zscaler-mcp-server -- uvx zscaler-mcp
Requires: ZSCALER_CLIENT_ID (secret), ZSCALER_CLIENT_SECRET (secret), ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of OWASP ZAP MCP Server publish no list of tools, so we do not compare tools.
Settings each asks for
Only OWASP ZAP MCP Server asks for
ZAP_API_KEYZAP_BASE_URL
Only Zscaler Zero Trust Exchange asks for
ZSCALER_CLIENT_ID (secret)ZSCALER_CLIENT_SECRET (secret)ZSCALER_CLOUD (secret)ZSCALER_CUSTOMER_ID (secret)ZSCALER_MCP_DISABLED_SERVICESZSCALER_MCP_DISABLED_TOOLSZSCALER_MCP_SKIP_CONFIRMATIONSZSCALER_MCP_WRITE_ENABLEDZSCALER_MCP_WRITE_TOOLSZSCALER_VANITY_DOMAIN (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: OWASP ZAP MCP Server · What it can do: Zscaler Zero Trust Exchange · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.