ThreatDown MCP vs Zscaler Zero Trust Exchange
ThreatDown MCP is an MCP server published by Servosity. Marketplaces we read that list it: 2 (Official MCP Registry, Community GitHub marketplaces). 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-10-27. 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: 0.1.3 Forks (GitHub): 13 Stars (GitHub): 63 Not marked · First seen |
Listed Version: 0.15.4 Downloads/month (PyPI): 1 348 Downloads/week (PyPI): 520 Forks (GitHub): 35 Stars (GitHub): 52 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.15.4 Forks (GitHub): 35 Stars (GitHub): 52 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:a3951ea456e1 Forks (GitHub): 35 Pulls (Docker Hub): 7 439 Stars (Docker Hub): 0 Stars (GitHub): 51 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 0.15.0 Forks (GitHub): 35 Stars (GitHub): 52 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 | ThreatDown MCP | Zscaler Zero Trust Exchange |
|---|---|---|
| Marketplaces that list it (differs) | 2 (worse) | 5 (better) |
| Stars (GitHub) (differs) | 63 (better) | 52 (worse) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 7 439 |
| Forks (GitHub) (differs) | 13 (worse) | 35 (better) |
| Last release (differs) | 2026-10-23 | Not published |
| Where it runs (differs) | On your machine (https://github.com/Servosity/msp-skills/releases/download/threatdown-v0.1.3/threatdown-mcp.mcpb) | On your machine (zscaler-mcp) |
| Transport | stdio | stdio |
| Tools it declares (differs) | Not published | 302 |
| Environment variables it asks for (differs) | 9, secrets among them: 3 | 10, secrets among them: 5 |
| Parts of the bundle (differs) | Not a bundle | 28 |
| Licence (differs) | Apache-2.0 | MIT |
| Repository (differs) | github.com/servosity/msp-skills | github.com/zscaler/zscaler-mcp-server |
| Changes in the last 7 days (differs) | 6 | 4 |
| First seen (differs) | 2026-10-15 | 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
ThreatDown MCP
Every ThreatDown OneView API, plus fleet-wide stale-endpoint, health and seat reports across all
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
ThreatDown MCP As a Claude Code plugin
/plugin marketplace add servosity/msp-skills
/plugin install threatdown@msp-skills
Requires: THREATDOWN_CLIENT_ID (secret), THREATDOWN_CLIENT_SECRET (secret), THREATDOWN_MCP_HTTP_TOKEN (secret)
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 ThreatDown MCP publish no list of tools, so we do not compare tools.
Settings each asks for
Only ThreatDown MCP asks for
PRINTING_PRESS_CLIENT_PROFILETHREATDOWN_BASE_URLTHREATDOWN_CLIENT_ID (secret)THREATDOWN_CLIENT_SECRET (secret)THREATDOWN_MCP_HTTP_TOKEN (secret)THREATDOWN_MCP_READ_ONLYTHREATDOWN_OAUTH_SCOPETHREATDOWN_TOKEN_URLTHREATDOWN_USER_AGENT
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: ThreatDown MCP · 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 public marketplace files in GitHub repositories of their authors. 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.