Zscaler Zero Trust Exchange

Zscaler Integration MCP Server is a Model Context Protocol (MCP) server designed for managing Several Zscaler Products u

MCP Servers Python Grade C Listed MIT
54.4/100
Rank #629 of 1320
Compare Zscaler Zero Trust Exchange

Thin or incomplete trust evidence. Review carefully before production use.

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade B · 3/5 signals
Last push
2026-08-24 · 11d ago
Recent change
Rank +5

Is Zscaler Zero Trust Exchange safe? Zscaler Zero Trust Exchange scores 54.4/100 (Grade C), ranked #629 of 1320 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.8/10; 50% of recent commits are signed; last pushed 2026-08-24. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-09-04
Rank Moved
Rank dropped 12 spots (#617 → #629)
2026-09-03
Rank Moved
Rank dropped 37 spots (#580 → #617)
2026-09-02
Rank Moved
Rank dropped 29 spots (#551 → #580)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 4.8/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.
53.9
Activity sub-score · out of 100
#306

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 →

Signals refreshed 2026-09-04 14:33 UTC · Repo last pushed 11 days ago

Rank Trend

2026-08-11 2026-09-04

Activity & Reach

Stars
50
Forks
27
Last Push
2026-08-24
11 days ago
Commits (4 wk)
11
Downloads (7d)
515
pypi
HN mentions (30d)
Open Issues
1
Rank Change
▼12
was #617

Analysis

HVTrust Dimensions vs MCP Servers

54.4 / 100 · 100.0% confidence

Zscaler Zero Trust Exchange MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
8.5 / 25
1.0 below avg 9.5
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.6 below avg 13.4
Transparency50% declared license · 50% OSSF Scorecard
12.6 / 17
0.8 above avg 11.8
Maintenance60% last-push freshness · 40% commit activity
15.6 / 20
3.4 above avg 12.2
AdoptionLog-scaled stars · package downloads
7.7 / 20
1.5 above avg 6.2

Activity Inputs

53.9 / 100
StarsRepository reach
10.2 / 30
FreshnessLast push recency
23.5 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
6.7 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
4.8 / 10
OpenSSF Scorecard · scanned Aug 30, 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 9

Is Zscaler Zero Trust Exchange safe?

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.8/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?
Maintained. Last push was 11 days ago.
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

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
Rank 10Listed 1HVTrust 1Grade 1Scorecard 1
2026-09-04
Rank Moved
Rank dropped 12 spots (#617 → #629)
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

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 54.4 Grade C
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