Is Zscaler Zero Trust Exchange safe to use?

Zscaler Zero Trust Exchange has an HVTrust score of 51.5/100 (Grade C), ranked #901 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Zscaler Zero Trust Exchange?

Zscaler Zero Trust Exchange scores 51.5/100 on HVTracker's evidence-weighted HVTrust scale. It has 51 GitHub stars and is categorized under MCP Servers.

Zscaler Zero Trust Exchange

zscaler/zscaler-mcp-server

Zscaler Integration MCP Server is a Model Context Protocol (MCP) server designed for managing Several Zscaler Products using Large Language Models (LLMs).

MCP Servers Python Listed MIT

Is Zscaler Zero Trust Exchange safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 4.3 / 10

Provenance None

Signed commits 50%

Last push 5d ago

Compare Zscaler Zero Trust Exchange

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Zscaler Zero Trust Exchange scores 51.5/100 (Grade C), ranked #901 of 1325 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 4.3/10; 50% of recent commits are signed; last pushed 2026-09-21. Every point is earned from checkable signals — never paid placement. How scoring works →

How Zscaler Zero Trust Exchange compares in MCP Servers

#509 IT Glue 51.6 +0.1
#510 Brainstorm MCP 51.6 +0.1
#511 Zscaler Zero Trust Exchange 51.5 this agent
#512 YouTube Research MCP 51.4 −0.1
#513 Tomyud1 Godot MCP 51.4 −0.1

Bars show each HVTrust score; the tick marks Zscaler Zero Trust Exchange’s 51.5.

Where the 51.5 comes from

HVTrust dimensions vs the MCP Servers average

51.5 / 100 · 100.0% confidence

Zscaler Zero Trust Exchange MCP Servers average (775 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits

7.9 / 25

2.4 below avg 10.3

Identity / Provenance60% listing status · 40% build provenance

10.8 / 18

2.6 below avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

12.2 / 17

in line with avg 12.2

Maintenance60% last-push freshness · 40% commit activity

11.7 / 20

in line with avg 12.1

AdoptionLog-scaled stars · package downloads

9.7 / 20

2.5 above avg 7.2

Quick Trust Read

What Would Improve It

Publish package provenance or release attestations for stronger supply-chain evidence.

Recent Changes

2026-09-25

Rank Moved

Rank dropped 13 spots (#888 → #901)

2026-09-24

Grade Changed

Trust grade D → C

2026-09-24

Rank Moved

Rank rose 53 spots (#941 → #888)

Maintainer Checklist

Raise Scorecard signals Current OSSF Scorecard is 4.3/10. Tighten the weakest checks to improve public safety evidence.

Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.

Compare with another agent Get email alerts for Zscaler Zero Trust Exchange View MCP Servers Report missing data

41.6

Activity sub-score · out of 100

#511

In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C 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

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-21

5 days ago

Commits (4 wk)

Downloads (7d)

14,357

docker+pypi

HN mentions (30d)

—

Open Issues

Rank Change

was #901

Analysis

Activity Inputs

41.6 / 100

StarsRepository reach

10.3 / 30

FreshnessLast push recency

24.3 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

7.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

4.3 / 10

OpenSSF Scorecard · scanned Sep 25, 2026

Signed Commits

50%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 0

CI-Tests 9

CII-Best-Practices 0

Code-Review 0

Contributors 10

Dangerous-Workflow 0

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 5

SAST 0

Security-Policy 0

Signed-Releases 8

Token-Permissions 0

Vulnerabilities 2

Common questions about Zscaler Zero Trust Exchange

Public trust evidence for Zscaler Zero Trust Exchange is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.

Does Zscaler Zero Trust Exchange publish package provenance?

No published build provenance is currently detected for Zscaler Zero Trust Exchange. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.

Does Zscaler Zero Trust Exchange have an OpenSSF Scorecard?

Zscaler Zero Trust Exchange has an OpenSSF Scorecard score of 4.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.

Is Zscaler Zero Trust Exchange actively maintained?

Actively maintained. The repository was pushed to within the last 5 day(s).

What license does Zscaler Zero Trust Exchange use?

Zscaler Zero Trust Exchange ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Zscaler Zero Trust Exchange's commits signed?

50% of the last 100 commits to Zscaler Zero Trust Exchange are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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

Scored in HVTrust

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 Server Support

high confidence

Implemented

Zscaler Zero Trust Exchange appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

4 detected

Public provider/service dependencies detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Declared

Declared plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

low confidence

Unknown

Package source metadata is missing or inconclusive

Detailed evidence is not shown in the public view.

MCP signal live
External deps live
Tool / plugin surface live
Package provenance drift live

How this surface has changed

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.

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history

2026-09-25

Rank Moved

Rank dropped 13 spots (#888 → #901)

2026-09-24

Grade Changed

Trust grade D → C

2026-09-24

Rank Moved

Rank rose 53 spots (#941 → #888)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → declared

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependencies: Amazon Bedrock, Anthropic, Google Gemini, OpenAI

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Rank Moved

Rank rose 96 spots (#1037 → #941)

2026-09-23

HVTrust Changed

HVTrust up 25.5pts (24.0 → 49.5)

2026-09-22

Newly Listed

First tracked at rank #1037

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-18

Grade Changed

Trust grade C → D

2026-09-18

Rank Moved

Rank dropped 45 spots (#911 → #956)

2026-09-18

Activity Score Changed

Activity score down 6pts (47 → 41)

2026-09-17

Grade Changed

Trust grade D → C

2026-09-17

Rank Moved

Rank rose 12 spots (#923 → #911)

2026-09-15

Grade Changed

Trust grade C → D

2026-09-13

Rank Moved

Rank dropped 12 spots (#910 → #922)

2026-09-12

Rank Moved

Rank dropped 20 spots (#890 → #910)

2026-09-11

Rank Moved

Rank dropped 14 spots (#876 → #890)

2026-09-09

Rank Moved

Rank dropped 48 spots (#823 → #871)

2026-09-08

Rank Moved

Rank dropped 65 spots (#758 → #823)

2026-09-07

Rank Moved

Rank dropped 15 spots (#743 → #758)

2026-09-06

Rank Moved

Rank dropped 26 spots (#717 → #743)

2026-09-05

Rank Moved

Rank dropped 74 spots (#643 → #717)

2026-09-04

Rank Moved

Rank dropped 26 spots (#617 → #643)

2026-09-03

Rank Moved

Rank dropped 37 spots (#580 → #617)

2026-09-02

Rank Moved

Rank dropped 29 spots (#551 → #580)

2026-09-01

Rank Moved

Rank dropped 11 spots (#540 → #551)

2026-08-31

Rank Moved

Rank dropped 35 spots (#505 → #540)

2026-08-29

Rank Moved

Rank dropped 24 spots (#485 → #509)

2026-08-27

Scorecard Added

OSSF Scorecard: 4.8/10

2026-08-27

Grade Changed

Trust grade D → C

2026-08-27

Rank Moved

Rank rose 417 spots (#895 → #478)

2026-08-27

HVTrust Changed

HVTrust up 25.2pts (29.7 → 54.9)

2026-08-26

Rank Moved

Rank dropped 112 spots (#783 → #895)

2026-08-16

Rank Moved

Rank dropped 16 spots (#764 → #780)

2026-08-10

Rank Moved

Rank dropped 40 spots (#729 → #769)

2026-08-08

Newly Listed

First tracked at rank #724

GitHub → PyPI: zscaler-mcp

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/zscaler-zero-trust-exchange.svg)](https://hvtracker.net/agents/zscaler-zero-trust-exchange)
            
HTML:
            <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

Data sources
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.3 · Raw JSON