updated 2026-08-12 05:02 UTC

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 u

MCP Servers Python Grade D Listed MIT
29.7/100
Rank #768 of 1283
Compare Zscaler Zero Trust Exchange

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

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

Open compare tool Suggest correction
Listing state
Listed
Evidence coverage
Grade C · 2/5 signals
Last push
2026-08-10 · 2d ago
Recent change
Rank +1

Is Zscaler Zero Trust Exchange safe? Zscaler Zero Trust Exchange scores 29.7/100 (Grade D), ranked #768 of 1283 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; no OSSF Scorecard result yet; 47% of recent commits are signed; last pushed 2026-08-10. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#358 Perplexity Comet MCP — 30.0 (D) → #359 Apideck Libraries MCP — 29.9 (D) → #361 Wechat Devtools MCP — 29.7 (D) → #362 Strava MCP — 29.5 (D) →

Quick Trust Read

What Would Improve It
Add or improve OSSF Scorecard coverage so safety checks are easier to verify.
Recent Changes
2026-08-10
Rank Moved
Rank dropped 40 spots (#729 → #769)
2026-08-08
Newly Listed
First tracked at rank #724
Maintainer Checklist
Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent Get email alerts for Zscaler Zero Trust Exchange View MCP Servers Report missing data
54.8
Activity sub-score · out of 100
#360
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 D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-08-12 05:02 UTC · Repo last pushed 2 days ago

Rank Trend

2026-08-11 2026-08-12

Activity & Reach

Stars
44
Forks
24
Last Push
2026-08-10
2 days ago
Commits (4 wk)
11
Downloads (7d)
764
pypi
HN mentions (30d)
—
Open Issues
4
Rank Change
▲1
was #769

Analysis

HVTrust Dimensions vs MCP Servers

29.7 / 100 · 67.0% confidence

Zscaler Zero Trust Exchange MCP Servers average (761 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
2.4 / 25
2.6 below avg 5.0
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.5 below avg 13.3
Transparency50% declared license · 50% OSSF Scorecard
8.5 / 17
in line with avg 8.8
Maintenance60% last-push freshness · 40% commit activity
16.2 / 20
3.8 above avg 12.4
AdoptionLog-scaled stars · package downloads
7.8 / 20
2.0 above avg 5.8

Activity Inputs

54.8 / 100
StarsRepository reach
9.9 / 30
FreshnessLast push recency
24.7 / 25
ActivityRecent commits
13.5 / 25
CommunityFork signal
6.5 / 20

Supply Chain Trust

Package Provenance
None
No package attestations found
OSSF Scorecard
—
Not available
Signed Commits
47%
of last 100 commits verified

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?
No OpenSSF Scorecard data is currently published for Zscaler Zero Trust Exchange. Maintainers can enable the Scorecard GitHub Action to get a public score; without it, automated supply-chain hygiene is harder for outsiders to verify.
Is Zscaler Zero Trust Exchange actively maintained?
Actively maintained. The repository was pushed to within the last 2 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?
47% 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Listed 1Rank 1
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
HVTrust 29.7 Grade D
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)
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON