railguard vs Zscaler Zero Trust Exchange
railguard is a plugin bundle for AI coding tools published by railyard-dev. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). 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-19. 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 | ||
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 0.5.1 Forks (GitHub): 5 Stars (GitHub): 39 Not marked · First seen |
Listed Version: 0.15.0 Forks (GitHub): 33 Stars (GitHub): 49 Not marked · First seen |
| Official MCP Registry | Not listed | Listed Version: 0.15.4 Downloads/month (PyPI): 1 348 Downloads/week (PyPI): 370 Forks (GitHub): 33 Stars (GitHub): 49 Not marked · First seen |
| Claude Code: claude-plugins-official | Not listed | Listed Version: 0.15.4 Forks (GitHub): 33 Stars (GitHub): 49 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:a3951ea456e1 Forks (GitHub): 33 Pulls (Docker Hub): 7 159 Stars (Docker Hub): 0 Stars (GitHub): 49 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 | railguard | Zscaler Zero Trust Exchange |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 5 (better) |
| Stars (GitHub) (differs) | 39 (worse) | 49 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 7 159 |
| Forks (GitHub) (differs) | 5 (worse) | 33 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (zscaler-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares (differs) | Not published | 302 |
| Environment variables it asks for (differs) | Not published | 10, secrets among them: 5 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 3 | 28 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/railyard-dev/railguard | github.com/zscaler/zscaler-mcp-server |
| Changes in the last 7 days (differs) | 0 | 2 |
| 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
railguard
Railguard is a safer, context-aware alternative to --dangerously-skip-permissions for Claude Code. Instead of choosing between approving every command manually or giving Claude unrestricted access, Railguard sits in the middle. It intercepts every tool call — Bash, Write, Edit, Read — and makes policy-based decisions: allow safe commands instantly, block dangerous ones automatically, and ask for human approval when it's not sure. Out of the box, Railguard comes with 29 default rules covering destructive operations like terraform destroy, rm -rf, DROP TABLE, and git force-push. It detects evasion attempts (base64 encoding, chr construction, variable substitution, shell wrapping), restricts file access with path fencing (blocking ~/.ssh, ~/.aws, /etc), snapshots every file write for one-click rollback, and logs every decision to a structured audit trail. Everything is customizable through a simple railguard.yaml file in your project directory.
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
railguard As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install railguard@claude-community
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 railguard publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of railguard publish no settings it asks for, so we do not compare settings.
What it can do: railguard · What it can do: Zscaler Zero Trust Exchange · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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 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.