Zscaler Zero Trust Exchange
PYPI · ZSCALER-MCP · 2 COMPONENTS · SCANNED SEP 20
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 Security100
- No malware found by supply-chain analysis.Pass
- 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 31 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 Management83
- Stability observed for 25 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.
- 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.
- 7 Sept 26 −3
- Stability: pass → 0.83 functional
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 20 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 →
zdx_get_device_deep_trace ~69
Get one ZDX deep-trace session. Read-only. The SDK returns a single-element list; the trace record is unwrapped, timestamps ISO-normalized, and shaped to the identity fields.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | yes | – |
| trace_id | string | yes | – |
No output schema declared.
No examples provided.
zdx_get_software_details ~230
Expand one ZDX software key into its per-user/device install rows. Read-only. Returns the users and devices that have the given `software_key` installed. Obtain the key from `zdx_list_software`.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| device_ids | – | – | – |
| geo_id | – | – | – |
| location_id | – | – | – |
| 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… |
| software_key | string | yes | – |
| user_ids | – | – | – |
No output schema declared.
No examples provided.
zdx_get_web_probes ~215
List web probes for an app on a ZDX device (full records). Read-only. Call this BEFORE `zdx_start_deeptrace` to obtain the `web_probe_id` the deep-trace payload needs.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | – |
| device_id | string | yes | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_alert_affected_devices ~237
List devices affected by a ZDX alert. Read-only. Returns one identifying row per affected device. Filter by location/department/geo, location groups, and the `since` HOURS window.
| Name | Type | Req | Description |
|---|---|---|---|
| alert_id | string | yes | – |
| department_id | – | – | – |
| geo_id | – | – | – |
| limit | – | – | – |
| location_groups | – | – | – |
| location_id | – | – | – |
| offset | – | – | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_alerts ~260
List ongoing ZDX alerts. Read-only. Returns one triage row per ongoing alert (id, rule, severity, type, start time, impacted-device count). Filter by location/department/geo and the `since` HOURS window (max 336h). Use a returned alert `id` with `zdx_get_alert` or `zdx_list_alert_affected_devices`.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| geo_id | – | – | – |
| limit | – | – | – |
| location_id | – | – | – |
| offset | – | – | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_application_users ~269
List users/devices that accessed a ZDX application, as curated rows. Read-only. Returns one triage row per user (id, name, email, ZDX score). Filter by `score_bucket` (poor/okay/good), location/department/geo, and the `since` HOURS window (default 2h). Use a returned `id` with `zdx_get_application_user`.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | – |
| department_id | – | – | – |
| geo_id | – | – | – |
| location_id | – | – | – |
| 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… |
| score_bucket | – | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_applications ~241
List active ZDX applications. Read-only. Returns one row per application (id, name, ZDX score, impact signals). Filter by location/department/geo and the `since` HOURS window. Use a returned `id` with `zdx_get_application`, `zdx_get_application_metric`, or `zdx_list_application_users`.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| geo_id | – | – | – |
| location_id | – | – | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_cloudpath_probes ~218
List cloud-path probes for an app on a ZDX device (full records). Read-only. Call this BEFORE `zdx_start_deeptrace` to obtain the `cloudpath_probe_id` the deep-trace payload needs.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | – |
| device_id | string | yes | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_deeptrace_top_processes ~205
List the top processes captured during a ZDX deep trace (full records). Read-only. Returns the process groups captured during the session — useful for spotting resource-intensive processes impacting performance.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | yes | – |
| 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… |
| trace_id | string | yes | – |
No output schema declared.
No examples provided.
zdx_list_departments ~204
List ZDX departments as curated id/name rows. Read-only. Use a returned `id` as the `department_id` scope filter on other ZDX tools. `since` is in HOURS (default 2h).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_device_deep_traces ~221
List deep-trace sessions for a ZDX device (full records). Read-only. Returns one row per trace (id, status, session name, app, ISO timestamps). Use a returned `trace_id` with the deep-trace metric/event tools or `zdx_get_device_deep_trace`.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | yes | – |
| 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.
zdx_list_devices ~272
List active ZDX devices. Read-only. Returns one identifying row per device (id, hostname, owning user). Filter by email, user ID, MAC/IP, location/department/geo, and the `since` HOURS window. Use a returned device `id` with `zdx_get_device` or the deep-trace / probe tools.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| emails | – | – | – |
| geo_id | – | – | – |
| location_id | – | – | – |
| mac_address | – | – | – |
| offset | – | – | – |
| private_ipv4 | – | – | – |
| 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… |
| since | – | – | – |
| user_ids | – | – | – |
No output schema declared.
No examples provided.
zdx_list_historical_alerts ~237
List historical (ended) ZDX alerts. Read-only. Like `zdx_list_alerts` but for alert rules that have an Ended On date. `since` is in HOURS (default 2h, max 14 days = 336h).
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| geo_id | – | – | – |
| limit | – | – | – |
| location_id | – | – | – |
| offset | – | – | – |
| 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… |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_locations ~203
List ZDX locations as curated id/name rows. Read-only. Use a returned `id` as the `location_id` scope filter on other ZDX tools. `since` is in HOURS (default 2h).
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | – | – | – |
| since | – | – | – |
No output schema declared.
No examples provided.
zdx_list_software ~240
List the ZDX software inventory. Read-only. Returns one row per software title (key, name, vendor, version, install/user counts). Filter by location/department/geo/user/device. Use a returned `software_key` with `zdx_get_software_details` to see who has it.
| Name | Type | Req | Description |
|---|---|---|---|
| department_id | – | – | – |
| device_ids | – | – | – |
| geo_id | – | – | – |
| location_id | – | – | – |
| 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… |
| user_ids | – | – | – |
No output schema declared.
No examples provided.
zeasm_get_finding_details ~68
Get the full detail for one EASM finding. Read-only. Adds description, country, CISA/EPSS exploitation-likelihood signals, and scan provenance on top of the triage fields.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
zeasm_get_finding_evidence ~85
Get the scan evidence attributed to one EASM finding. Read-only. Returns the evidence `content` (the subset of scan output attributable to this finding) and its `source_type`. The content can be large free-form scanner text and is preserved verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
zeasm_get_finding_scan_output ~72
Get the complete scan output for one EASM finding. Read-only. Returns the full scan `content` and its `source_type`. The content can be large free-form scanner text and is preserved verbatim.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
zeasm_get_lookalike_domain ~98
Get full detail for one EASM lookalike domain. Read-only. Adds description, registrar/registrant + lifecycle dates, and remediation guidance on top of the triage fields. Look the domain up by its `lookalike_raw` name (from `zeasm_list_lookalike_domains`).
| Name | Type | Req | Description |
|---|---|---|---|
| lookalike_raw | string | yes | – |
| org_id | string | yes | – |
No output schema declared.
No examples provided.
zeasm_list_findings ~238
List EASM findings for an organization. Read-only. Returns one triage row per finding (id, category, type, status, risk level/score, impacted asset, first/last seen) rather than the raw SDK record. Use the returned `id` with `zeasm_get_finding_details`, `zeasm_get_finding_evidence`, or `zeasm_get_finding_scan_output`.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | – |
| 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.
zeasm_list_lookalike_domains ~235
List EASM lookalike domains for an organization. Read-only. Returns one triage row per detected lookalike/impersonation domain (the lookalike, the domain it impersonates, risk, registration state, deception methods). Use the returned `lookalike_raw` with `zeasm_get_lookalike_domain` for full detail.
| Name | Type | Req | Description |
|---|---|---|---|
| org_id | string | yes | – |
| 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.
zeasm_list_organizations ~219
List ZEASM organizations. Read-only. Returns one row per organization configured in the EASM Admin Portal, carrying just the `id` + `name`. Use the returned `id` as the `org_id` argument for `zeasm_list_findings`, `zeasm_list_lookalike_domains`, and the other EASM tools.
| Name | Type | Req | Description |
|---|---|---|---|
| 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.
zia_geo_search ~193
Resolve ZIA geo data by coordinates, by IP, or by city prefix (read-only).
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| ip | – | – | – |
| latitude | – | – | – |
| longitude | – | – | – |
| prefix | – | – | – |
| 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.
zia_get_activation_status ~20
Get the current ZIA configuration activation status.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_advanced_settings ~22
Get the ZIA tenant-wide Advanced Settings object.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_atp_malware_inspection ~28
Get the ZIA malware inspection (traffic-direction toggles).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_atp_malware_policy ~28
Get the ZIA malware policy (file-handling toggles).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_atp_malware_protocols ~29
Get the ZIA malware protocol toggles (HTTP/FTP).
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_atp_security_exceptions ~27
Get the ZIA ATP security-exception bypass URL allowlist.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_atp_settings ~22
Get the ZIA tenant-wide ATP policy block.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_cloud_app_control_rule ~43
Get a single ZIA Cloud App Control rule by category + ID.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
| rule_type | string | yes | – |
No output schema declared.
No examples provided.
zia_get_cloud_firewall_dns_rule ~37
Get a single ZIA Cloud Firewall DNS rule by ID with member references.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_cloud_firewall_ips_rule ~37
Get a single ZIA Cloud Firewall IPS rule by ID with member references.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_cloud_firewall_rule ~35
Get a single ZIA Cloud Firewall rule by ID with member references.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_file_type_control_rule ~36
Get a single ZIA File Type Control rule by ID with member references.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_gre_tunnel ~31
Get a single ZIA GRE tunnel by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| tunnel_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_ip_destination_group ~34
Get a single ZIA IP destination group by ID with full members.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_ip_source_group ~36
Get a single ZIA IP source group by ID with its full member list.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_ips_signature_rule ~35
Get a single ZIA custom IPS signature rule by ID with its body.
| Name | Type | Req | Description |
|---|---|---|---|
| rule_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_location ~31
Get a single ZIA location by ID with its full configuration.
| Name | Type | Req | Description |
|---|---|---|---|
| location_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_location_group ~29
Get a single ZIA location group by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_malware_settings ~26
Get the ZIA 16-field malware threat-class settings block.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_mobile_advanced_settings ~23
Get the ZIA Mobile Advanced Threat Settings object.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_network_app ~29
Get a single ZIA network application by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| app_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_network_app_group ~33
Get a single ZIA network application group by ID with members.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_network_service ~33
Get a single ZIA network service by ID with its port definitions.
| Name | Type | Req | Description |
|---|---|---|---|
| service_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_network_svc_group ~34
Get a single ZIA network service group by ID with members.
| Name | Type | Req | Description |
|---|---|---|---|
| group_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_rule_label ~29
Get a single ZIA rule label by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| label_id | string | yes | – |
No output schema declared.
No examples provided.
zia_get_sandbox_behavioral_analysis ~23
Get the ZIA Sandbox behavioral-analysis configuration.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
zia_get_sandbox_file_hash_count ~29
Get the ZIA Sandbox custom file-hash blocklist usage/quota.
Input schema present but exposes no named parameters.
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 78 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.