Zscaler Zero Trust Exchange
Zscaler Integration MCP Server is a Model Context Protocol (MCP) server designed for managing Several Zscaler Products using Large Language Models (LLMs).
Is Zscaler Zero Trust Exchange safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare Zscaler Zero Trust Exchange
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Zscaler Zero Trust Exchange scores 47.8/100 (Grade D), ranked #1070 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.9/10; recent commits are unsigned; last pushed 2026-10-27. Every point is earned from checkable signals — never paid placement. How scoring works →
How Zscaler Zero Trust Exchange could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Publish build provenance for its packagesPyPI Trusted Publishing attestations +14.7 → 62.5 C · #346 of 778
- Raise the OSSF Scorecard from 3.9 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +10.6 → 58.4 C · #402 of 778
- Sign every commit0% signed today +5.0 → 52.8 C · #513 of 778
Chain of custody
Scanners check what the code says. This traces who ships Zscaler Zero Trust Exchange and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Unsigned
github.com/zscaler/zscaler-mcp-server, MIT, last pushed 2026-10-27. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.9/10 (scanned Nov 7, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases8
- Dangerous Workflow0
- Token Permissions0
- Pinned Dependencies5
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests -1CII-Best-Practices 0Code-Review 0Contributors 10Dangerous-Workflow 0Dependency-Update-Tool 10Fuzzing 0License 10Maintained 9Packaging 10Pinned-Dependencies 5SAST 0Security-Policy 0Signed-Releases 8Token-Permissions 0Vulnerabilities 0 -
Published packages Not linked
- PyPI zscaler-mcp Source link isn't a GitHub repo No build attestation
Without a build attestation, nothing proves the published files were built from this repository.
Changes to this chain
- 2026-08-27 OSSF Scorecard: 4.8/10
Evidence behind this score
Coverage B: 3 of 5 independent evidence types found.
- GitHub repository data
- Package downloads
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues Zscaler Zero Trust Exchange’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How Zscaler Zero Trust Exchange compares in MCP Servers
- #602 Ryaker Appstore Connect MCP 48.0 +0.2
- #603 Kylas CRM 47.9 +0.1
- #604 Zscaler Zero Trust Exchange 47.8 this agent
- #605 Cortex Gateway 47.7 −0.1
- #606 Mistral MCP 47.7 −0.1
Bars show each HVTrust score; the tick marks Zscaler Zero Trust Exchange’s 47.8.
Where the 47.8 comes from
HVTrust dimensions vs the MCP Servers average
47.8 / 100 · 100.0% confidenceZscaler Zero Trust Exchange MCP Servers average (778 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
40.9 / 100Common questions about Zscaler Zero Trust Exchange
Does Zscaler Zero Trust Exchange publish package provenance?
Does Zscaler Zero Trust Exchange have an OpenSSF Scorecard?
Is Zscaler Zero Trust Exchange actively maintained?
What license does Zscaler Zero Trust Exchange use?
Are Zscaler Zero Trust Exchange's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Zscaler Zero Trust Exchange's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Zscaler Zero Trust Exchange?
For maintainers
HVTrust scores Zscaler Zero Trust Exchange from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/zscaler-zero-trust-exchange)
<a href="https://hvtracker.net/agents/zscaler-zero-trust-exchange"><img src="https://hvtracker.net/badge/zscaler-zero-trust-exchange.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON