Is MCP Zuul safe to use?

MCP Zuul has an HVTrust score of 72.4/100 (Grade B), ranked #277 of 1325 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for MCP Zuul?

MCP Zuul scores 72.4/100 on HVTracker's evidence-weighted HVTrust scale. It has 21 GitHub stars and is categorized under MCP Servers.

MCP Zuul

imatza-rh/mcp-zuul

MCP server for Zuul CI - debug build failures, search logs, manage pipelines, and monitor jobs from Claude, Cursor, or any MCP client

MCP Servers Python Listed Apache-2.0

Is MCP Zuul safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 6.4 / 10

Provenance Attested

Signed commits 19%

Last push 7d ago

Compare MCP Zuul

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP Zuul scores 72.4/100 (Grade B), ranked #277 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 6.4/10; 19% of recent commits are signed; last pushed 2026-09-19. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP Zuul compares in MCP Servers

Bars show each HVTrust score; the tick marks MCP Zuul’s 72.4.

Where the 72.4 comes from

HVTrust dimensions vs the MCP Servers average

72.4 / 100 · 100.0% confidence

MCP Zuul MCP Servers average (775 agents)

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

16.4 / 25

6.1 above avg 10.3

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.6 above avg 13.4

Transparency50% declared license · 50% OSSF Scorecard

13.9 / 17

1.7 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

13.2 / 20

1.1 above avg 12.1

AdoptionLog-scaled stars · package downloads

5.9 / 20

1.3 below avg 7.2

Quick Trust Read

What Would Improve It

Increase the share of verified signed commits for clearer maintainer identity.

Recent Changes

2026-09-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintainer Checklist

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

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 MCP Zuul View MCP Servers Report missing data

47.0

Activity sub-score · out of 100

#165

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 B 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-19

7 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #279

Analysis

Activity Inputs

47.0 / 100

StarsRepository reach

8.1 / 30

FreshnessLast push recency

24.0 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

4.2 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

6.4 / 10

OpenSSF Scorecard · scanned Sep 18, 2026

Signed Commits

19%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 3

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 3

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 8

SAST 10

Security-Policy 10

Signed-Releases 0

Token-Permissions 0

Vulnerabilities 10

Common questions about MCP Zuul

MCP Zuul has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.

Does MCP Zuul publish package provenance?

Yes. MCP Zuul's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.

Does MCP Zuul have an OpenSSF Scorecard?

MCP Zuul has an OpenSSF Scorecard score of 6.4/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 MCP Zuul actively maintained?

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

What license does MCP Zuul use?

MCP Zuul ships under Apache-2.0. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are MCP Zuul's commits signed?

19% of the last 100 commits to MCP Zuul 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

medium confidence

Implemented

MCP Zuul appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

high confidence

1 detected

Public provider/service dependencies detected.

Google Gemini

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

None detected

No clear plugin system or broad tool surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

high confidence

Match

Published package metadata matches the tracked repo

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 MCP Zuul'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

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-02

Provenance Added

Package provenance attestation detected

Maintain MCP Zuul?

For maintainers

HVTrust scores MCP Zuul 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-23

Provider Added

Runtime surface grew — new detected provider dependency: Google Gemini

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

2026-09-23

Grade Changed

Trust grade D → B

2026-09-23

Rank Moved

Rank rose 542 spots (#821 → #279)

2026-09-23

HVTrust Changed

HVTrust up 44.0pts (28.4 → 72.4)

2026-09-22

Newly Listed

First tracked at rank #821

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-17

Rank Moved

Rank dropped 54 spots (#221 → #275)

2026-09-15

Rank Moved

Rank dropped 34 spots (#186 → #220)

2026-09-07

Rank Moved

Rank dropped 11 spots (#157 → #168)

2026-09-05

Rank Moved

Rank dropped 27 spots (#128 → #155)

2026-09-02

Provenance Added

Package provenance attestation detected

2026-09-02

Grade Changed

Trust grade C → B

2026-09-02

Rank Moved

Rank rose 231 spots (#350 → #119)

2026-09-02

HVTrust Changed

HVTrust up 14.8pts (62.8 → 77.6)

2026-09-01

Scorecard Added

OSSF Scorecard: 6.3/10

2026-09-01

Grade Changed

Trust grade D → C

2026-09-01

Rank Moved

Rank rose 656 spots (#1006 → #350)

2026-09-01

HVTrust Changed

HVTrust up 27.9pts (34.9 → 62.8)

2026-08-31

Rank Moved

Rank dropped 28 spots (#978 → #1006)

2026-08-30

Rank Moved

Rank dropped 52 spots (#926 → #978)

2026-08-29

Rank Moved

Rank dropped 50 spots (#876 → #926)

2026-08-28

Rank Moved

Rank dropped 29 spots (#847 → #876)

2026-08-27

Rank Moved

Rank dropped 27 spots (#820 → #847)

2026-08-26

Rank Moved

Rank dropped 109 spots (#711 → #820)

2026-08-16

Rank Moved

Rank dropped 10 spots (#702 → #712)

2026-08-10

Rank Moved

Rank dropped 39 spots (#674 → #713)

2026-08-08

Newly Listed

First tracked at rank #673

GitHub → PyPI: mcp-zuul

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-zuul.svg)](https://hvtracker.net/agents/mcp-zuul)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-zuul"><img src="https://hvtracker.net/badge/mcp-zuul.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