Is MCP ZAP Server safe to use?

MCP ZAP Server has an HVTrust score of 59.9/100 (Grade C), ranked #631 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 ZAP Server?

MCP ZAP Server scores 59.9/100 on HVTracker's evidence-weighted HVTrust scale. It has 66 GitHub stars and is categorized under MCP Servers.

MCP ZAP Server

dtkmn/mcp-zap-server

Give AI agents a safe, self-hosted ZAP operator for guided web security scans, findings, reports, and production guardrails.

MCP Servers Java Listed Apache-2.0

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

OSSF Scorecard 7.5 / 10

Provenance None

Signed commits 15%

Last push today

Compare MCP ZAP Server

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: MCP ZAP Server scores 59.9/100 (Grade C), ranked #631 of 1325 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 7.5/10; 15% of recent commits are signed; last pushed 2026-09-26. Every point is earned from checkable signals — never paid placement. How scoring works →

How MCP ZAP Server compares in MCP Servers

#351 SAS MCP Server 60.1 +0.2
#352 Teamwork MCP 60.1 +0.2
#353 MCP ZAP Server 59.9 this agent
#354 Wavyrai reMarkable MCP Server 59.9 ±0
#355 OpenResearch MCP 59.9 ±0

Bars show each HVTrust score; the tick marks MCP ZAP Server’s 59.9.

Where the 59.9 comes from

HVTrust dimensions vs the MCP Servers average

59.9 / 100 · 100.0% confidence

MCP ZAP Server MCP Servers average (775 agents)

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

10.1 / 25

in line with 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

14.9 / 17

2.7 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

19.3 / 20

7.2 above avg 12.1

AdoptionLog-scaled stars · package downloads

4.4 / 20

2.8 below 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 rose 14 spots (#647 → #633)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintainer Checklist

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

63.9

Activity sub-score · out of 100

#353

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 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 →

Rank Trend

2026-08-11 2026-09-26

Activity & Reach

Stars

Forks

Last Push

2026-09-26

today

Commits (4 wk)

Downloads (7d)

—

HN mentions (30d)

—

Open Issues

Rank Change

▲2

was #633

Analysis

Activity Inputs

63.9 / 100

StarsRepository reach

11.0 / 30

FreshnessLast push recency

25.0 / 25

ActivityRecent commits

22.9 / 25

CommunityFork signal

5.0 / 20

Supply Chain Trust

Package Provenance

None

No package attestations found

OSSF Scorecard

7.5 / 10

OpenSSF Scorecard · scanned Sep 23, 2026

Signed Commits

15%

of last 100 commits verified

Binary-Artifacts 9

Branch-Protection 5

CI-Tests 10

CII-Best-Practices 0

Code-Review 0

Contributors 0

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 10

Packaging 10

Pinned-Dependencies 10

SAST 10

Security-Policy 10

Signed-Releases -1

Token-Permissions 7

Vulnerabilities 10

Common questions about MCP ZAP Server

MCP ZAP Server 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 ZAP Server publish package provenance?

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

Does MCP ZAP Server have an OpenSSF Scorecard?

MCP ZAP Server has an OpenSSF Scorecard score of 7.5/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 ZAP Server actively maintained?

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

What license does MCP ZAP Server use?

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

Are MCP ZAP Server's commits signed?

15% of the last 100 commits to MCP ZAP Server 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

MCP ZAP Server appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

low confidence

None detected

No clear third-party provider dependency detected.

Credential signal: API keys or service config markers documented.

Tool / Plugin Surface

high confidence

Extensions

Extension based plugin/integration surface detected.

Detailed evidence is not shown in the public view.

Package Provenance Drift

N/A

No package source configured

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 ZAP Server'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 → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

Maintain MCP ZAP Server?

For maintainers

HVTrust scores MCP ZAP Server 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 rose 14 spots (#647 → #633)

2026-09-23

Tool Surface Changed

Detected tool/plugin surface changed: none → extension-based

2026-09-23

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Grade Changed

Trust grade D → C

2026-09-23

Rank Moved

Rank dropped 22 spots (#622 → #644)

2026-09-23

HVTrust Changed

HVTrust up 26.2pts (33.1 → 59.3)

2026-09-22

Newly Listed

First tracked at rank #622

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-20

Rank Moved

Rank dropped 10 spots (#625 → #635)

2026-09-17

Rank Moved

Rank rose 22 spots (#649 → #627)

2026-09-16

Grade Changed

Trust grade D → C

2026-09-16

Rank Moved

Rank rose 531 spots (#1180 → #649)

2026-09-16

HVTrust Changed

HVTrust up 19.6pts (39.1 → 58.7)

2026-09-15

Grade Changed

Trust grade C → D

2026-09-15

Rank Moved

Rank dropped 558 spots (#622 → #1180)

2026-09-15

HVTrust Changed

HVTrust down 20.4pts (59.5 → 39.1)

2026-09-14

Grade Changed

Trust grade D → C

2026-09-14

Rank Moved

Rank rose 542 spots (#1164 → #622)

2026-09-14

HVTrust Changed

HVTrust up 19.5pts (40.0 → 59.5)

2026-09-13

Grade Changed

Trust grade C → D

2026-09-13

Rank Moved

Rank dropped 537 spots (#627 → #1164)

2026-09-13

HVTrust Changed

HVTrust down 19.4pts (59.4 → 40.0)

2026-09-12

Rank Moved

Rank rose 77 spots (#704 → #627)

2026-09-12

Activity Score Changed

Activity score up 6pts (52 → 58)

2026-09-11

Rank Moved

Rank dropped 32 spots (#672 → #704)

2026-09-10

Grade Changed

Trust grade D → C

2026-09-10

Rank Moved

Rank rose 494 spots (#1166 → #672)

2026-09-10

HVTrust Changed

HVTrust up 18.7pts (38.9 → 57.6)

2026-09-09

Grade Changed

Trust grade C → D

2026-09-09

Rank Moved

Rank dropped 499 spots (#667 → #1166)

2026-09-09

HVTrust Changed

HVTrust down 18.5pts (57.4 → 38.9)

2026-09-07

Rank Moved

Rank dropped 51 spots (#608 → #659)

2026-09-06

Rank Moved

Rank dropped 24 spots (#584 → #608)

2026-09-05

Rank Moved

Rank dropped 99 spots (#485 → #584)

2026-09-04

Rank Moved

Rank dropped 13 spots (#472 → #485)

2026-09-03

Rank Moved

Rank dropped 24 spots (#448 → #472)

2026-09-02

Rank Moved

Rank dropped 17 spots (#431 → #448)

2026-08-31

Rank Moved

Rank dropped 33 spots (#390 → #423)

2026-08-30

Rank Moved

Rank rose 13 spots (#403 → #390)

2026-08-29

Scorecard Added

OSSF Scorecard: 7.5/10

2026-08-29

Grade Changed

Trust grade D → C

2026-08-29

Rank Moved

Rank rose 679 spots (#1082 → #403)

2026-08-29

HVTrust Changed

HVTrust up 36.7pts (22.5 → 59.2)

2026-08-28

Rank Moved

Rank dropped 14 spots (#1068 → #1082)

2026-08-27

Rank Moved

Rank dropped 16 spots (#1052 → #1068)

2026-08-26

Rank Moved

Rank dropped 116 spots (#936 → #1052)

2026-08-25

Rank Moved

Rank dropped 18 spots (#918 → #936)

2026-08-24

Rank Moved

Rank dropped 14 spots (#904 → #918)

2026-08-21

Rank Moved

Rank rose 14 spots (#924 → #910)

2026-08-19

Rank Moved

Rank dropped 11 spots (#915 → #926)

2026-08-17

Rank Moved

Rank rose 16 spots (#931 → #915)

2026-08-16

Rank Moved

Rank dropped 29 spots (#902 → #931)

2026-08-13

Rank Moved

Rank dropped 20 spots (#875 → #895)

2026-08-12

Rank Moved

Rank rose 14 spots (#889 → #875)

2026-08-10

Rank Moved

Rank dropped 57 spots (#828 → #885)

2026-08-08

Newly Listed

First tracked at rank #823

GitHub →

Embed Badge Badge guide for maintainers →

For maintainers

Markdown:
            [![HVTrust](https://hvtracker.net/badge/mcp-zap-server.svg)](https://hvtracker.net/agents/mcp-zap-server)
            
HTML:
            <a href="https://hvtracker.net/agents/mcp-zap-server"><img src="https://hvtracker.net/badge/mcp-zap-server.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON