Zscaler Zero Trust Exchange vs org.proxykey/proxykey
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). org.proxykey/proxykey is an MCP server published by proxykey.org. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-21. 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 |   Zscaler Zero Trust Exchange |  org.proxykey/proxykey |
|---|---|---|
| Official MCP Registry | Listed Version: 0.15.4 Downloads/month (PyPI): 1 348 Downloads/week (PyPI): 370 Forks (GitHub): 34 Stars (GitHub): 51 Not marked · First seen |
Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-official | Listed Version: 0.15.4 Forks (GitHub): 34 Stars (GitHub): 51 Not marked · First seen |
Not listed |
| Docker MCP Catalog | Listed Version: sha256:a3951ea456e1 Forks (GitHub): 34 Pulls (Docker Hub): 7 181 Stars (Docker Hub): 0 Stars (GitHub): 51 Not marked · First seen |
Not listed |
| Claude Code: claude-plugins-community | Listed Version: 0.15.0 Forks (GitHub): 34 Stars (GitHub): 51 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 | Zscaler Zero Trust Exchange | org.proxykey/proxykey |
|---|---|---|
| Marketplaces that list it (differs) | 5 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 51 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 7 181 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 34 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (zscaler-mcp) | Remote server (mcp.proxykey.org/mcp) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 302 | Not published |
| Environment variables it asks for (differs) | 10, secrets among them: 5 | Not published |
| Parts of the bundle (differs) | 28 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/zscaler/zscaler-mcp-server | github.com/neostorm112-boop/proxykey-mcp |
| 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 | Responded 3 days 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
Zscaler Zero Trust Exchange
Manage Zscaler Zero Trust Exchange via 400+ tools — ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.
org.proxykey/proxykey
Issue, rotate and revoke scoped API-key passes for 25+ providers — the agent never sees a real key
How to run each
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-mcpRequires: ZSCALER_CLIENT_ID (secret), ZSCALER_CLIENT_SECRET (secret), ZSCALER_CUSTOMER_ID, ZSCALER_VANITY_DOMAIN
org.proxykey/proxykey As a remote MCP server
claude mcp add --transport http proxykey https://mcp.proxykey.org/mcp --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only org.proxykey/proxykey has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of org.proxykey/proxykey publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of org.proxykey/proxykey publish no settings it asks for, so we do not compare settings.
What it can do: Zscaler Zero Trust Exchange · What it can do: org.proxykey/proxykey · 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.