Zscaler Zero Trust Exchange
PYPI · ZSCALER-MCP · 2 COMPONENTS · SCANNED SEP 21
Manage Zscaler Zero Trust Exchange via 400+ tools — ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 85 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 32 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 37993 tokens (~149/item across 254 items; 254 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
- Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage77
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 19% of tool parameters carry a description.Partial
- Structured output schemas are declared (4% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 254 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 254 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
How do I install the Zscaler Zero Trust Exchange MCP server?
Zscaler Zero Trust Exchange runs locally as a PyPI package, launched with uvx zscaler-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · zscaler-mcp
claude mcp add zscaler-zscaler-mcp-server -- uvx zscaler-mcp
{
"mcpServers": {
"zscaler-zscaler-mcp-server": {
"command": "uvx",
"args": [
"zscaler-mcp"
]
}
}
} {
"servers": {
"zscaler-zscaler-mcp-server": {
"command": "uvx",
"args": [
"zscaler-mcp"
]
}
}
} codex mcp add zscaler-zscaler-mcp-server -- uvx zscaler-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"zscaler-zscaler-mcp-server": {
"type": "local",
"command": [
"uvx",
"zscaler-mcp"
],
"enabled": true
}
}
} openclaw mcp add zscaler-zscaler-mcp-server --command uvx --arg zscaler-mcp
mcp_servers:
zscaler-zscaler-mcp-server:
command: "uvx"
args: ["zscaler-mcp"] {
"McpServers": {
"zscaler-zscaler-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"zscaler-mcp"
]
}
}
} assistant mcp add zscaler-zscaler-mcp-server -t stdio -c uvx -a zscaler-mcp
{
"mcpServers": {
"zscaler-zscaler-mcp-server": {
"command": "uvx",
"args": [
"zscaler-mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +16
- Malware scan: unverified → pass ▲ security
- Stability: 0.97 → pass security
- 16 Sept 26 −14
- Malware scan: pass → unverified ▼ security
- 14 Sept 26 +13
- Malware scan: unverified → pass ▲ security
- Stability: pass → 0.87 functional
- 12 Sept 26 +1
- Stability: 0.97 → pass security
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed pypi/zscaler-mcp@0.15.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 85 packages
| Packages resolved | 85 |
|---|---|
| Stale | 7 |
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
ztw_list_network_services ~183
List ZTW network services. Optionally filter by `protocol` or `search`. Read-only.
| Name | Type | Req | Description |
|---|---|---|---|
| locale | – | – | – |
| protocol | – | – | – |
| query | – | – | Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get… |
| search | – | – | – |
No output schema declared.
No examples provided.
ztw_list_public_account_details ~171
List ZTW public-cloud account details (read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| page | – | – | – |
| page_size | – | – | – |
| query | – | – | Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get… |
No output schema declared.
No examples provided.
ztw_list_public_cloud_info ~182
List ZTW public-cloud account info (read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| cloud_type | – | – | – |
| page | – | – | – |
| page_size | – | – | – |
| query | – | – | Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get… |
| search | – | – | – |
No output schema declared.
No examples provided.
ztw_list_roles ~190
List ZTW admin roles (read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| include_api_roles | – | – | – |
| include_auditor_role | – | – | – |
| include_partner_role | – | – | – |
| query | – | – | Optional JMESPath expression applied to the results after the API call, for client-side filtering and projection. Examples: "[?enabled==`true`]", "[*].{name: name, id: id}", "length(@)". Omit to get… |
| role_ids | – | – | – |
| search | – | – | – |
No output schema declared.
No examples provided.
What is the Zscaler Zero Trust Exchange MCP server?
Zscaler Zero Trust Exchange is an MCP server listed in the public MCP registry as io.github.zscaler/zscaler-mcp-server. Manage Zscaler Zero Trust Exchange via 400+ tools, ZPA, ZIA, ZDX, ZCC, ZTW, ZMS, EASM, and more. This page covers its PyPI package (zscaler-mcp).
Is the Zscaler Zero Trust Exchange MCP server safe to use?
Zscaler Zero Trust Exchange scores 64 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Zscaler Zero Trust Exchange MCP server expose?
Zscaler Zero Trust Exchange exposes 254 tools: zeasm_list_findings, zeasm_get_finding_details, zeasm_get_finding_evidence, zeasm_get_finding_scan_output, zeasm_list_lookalike_domains, and 249 more. Their descriptions and schemas cost roughly 37,993 tokens of context every time the server is loaded.
Is the Zscaler Zero Trust Exchange MCP server still maintained?
Zscaler Zero Trust Exchange is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.