Is Mcpcap safe to use?

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

What is the trust score for Mcpcap?

Mcpcap scores 69.7/100 on HVTracker's evidence-weighted HVTrust scale. It has 51 GitHub stars and is categorized under MCP Servers.

Mcpcap

mcpcap/mcpcap

Network analysis for the AI age

MCP Servers Python Listed MIT

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

OSSF Scorecard 5.3 / 10

Provenance Attested

Signed commits 91%

Last push 72d ago

Compare Mcpcap

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Suggest a correction

In detail: Mcpcap scores 69.7/100 (Grade B), ranked #339 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 5.3/10; 91% of recent commits are signed; last pushed 2026-07-16. Every point is earned from checkable signals — never paid placement. How scoring works →

How Mcpcap compares in MCP Servers

#204 Xcode: MCP Bridge Wrapper for Cursor 69.8 +0.1
#205 Robinhood Portfolio Research 69.7 ±0
#206 Mcpcap 69.7 this agent
#207 Excalidraw Architect 69.5 −0.2
#208 ServiceNow MCP Server 69.2 −0.5

Bars show each HVTrust score; the tick marks Mcpcap’s 69.7.

Where the 69.7 comes from

HVTrust dimensions vs the MCP Servers average

69.7 / 100 · 100.0% confidence

Mcpcap MCP Servers average (775 agents)

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

18.7 / 25

8.4 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.0 / 17

0.8 above avg 12.2

Maintenance60% last-push freshness · 40% commit activity

7.2 / 20

4.9 below avg 12.1

AdoptionLog-scaled stars · package downloads

6.8 / 20

in line with avg 7.2

Quick Trust Read

What Would Improve It

Improve adoption to lift the weakest part of the trust profile.

Recent Changes

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

Maintainer Checklist

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

Refresh maintenance signals The repo was last pushed 72 days ago. Fresh activity helps separate stable projects from stale ones.

Compare with another agent Get email alerts for Mcpcap View MCP Servers Report missing data

30.9

Activity sub-score · out of 100

#206

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-07-16

72 days ago

Commits (4 wk)

Downloads (7d)

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▼8

was #331

Analysis

Activity Inputs

30.9 / 100

StarsRepository reach

10.3 / 30

FreshnessLast push recency

15.0 / 25

ActivityRecent commits

0.0 / 25

CommunityFork signal

5.5 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

5.3 / 10

OpenSSF Scorecard · scanned Sep 24, 2026

Signed Commits

91%

of last 100 commits verified

Binary-Artifacts 10

Branch-Protection 8

CI-Tests 10

CII-Best-Practices 0

Code-Review 1

Contributors 10

Dangerous-Workflow 10

Dependency-Update-Tool 10

Fuzzing 0

License 10

Maintained 0

Packaging 10

Pinned-Dependencies 0

SAST 2

Security-Policy 0

Signed-Releases -1

Token-Permissions 9

Vulnerabilities 0

Common questions about Mcpcap

Mcpcap 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 Mcpcap publish package provenance?

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

Does Mcpcap have an OpenSSF Scorecard?

Mcpcap has an OpenSSF Scorecard score of 5.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 Mcpcap actively maintained?

Slowing down. Last push was 72 days ago — keep an eye on whether activity resumes.

What license does Mcpcap use?

Mcpcap ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.

Are Mcpcap's commits signed?

91% of the last 100 commits to Mcpcap 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

Mcpcap appears to expose MCP server capabilities.

Detailed evidence is not shown in the public view.

External Service Dependencies

None detected

No clear third-party provider dependency detected.

Credential signal: No explicit API-key/config marker detected.

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 Mcpcap'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

Mcp Status Changed

Detected MCP server support changed: none → implemented

2026-09-23

Provenance Added

Package provenance attestation detected

Maintain Mcpcap?

For maintainers

HVTrust scores Mcpcap 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

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 772 spots (#1094 → #322)

2026-09-23

HVTrust Changed

HVTrust up 47.8pts (22.3 → 70.1)

2026-09-22

Newly Listed

First tracked at rank #1094

2026-09-21

Removed From Active Tracking

Removed from active tracking

2026-09-11

Rank Moved

Rank dropped 11 spots (#291 → #302)

2026-09-08

Rank Moved

Rank dropped 12 spots (#273 → #285)

2026-09-07

Rank Moved

Rank dropped 13 spots (#260 → #273)

2026-09-06

Rank Moved

Rank dropped 10 spots (#250 → #260)

2026-09-05

Rank Moved

Rank dropped 55 spots (#195 → #250)

2026-09-03

Scorecard Added

OSSF Scorecard: 5.3/10

2026-09-03

Grade Changed

Trust grade C → B

2026-09-03

Rank Moved

Rank rose 225 spots (#412 → #187)

2026-09-03

HVTrust Changed

HVTrust up 10.9pts (60.8 → 71.7)

2026-09-02

Rank Moved

Rank dropped 14 spots (#398 → #412)

2026-09-01

Rank Moved

Rank dropped 11 spots (#387 → #398)

2026-08-31

Rank Moved

Rank dropped 35 spots (#352 → #387)

2026-08-26

Rank Moved

Rank dropped 28 spots (#313 → #341)

2026-08-24

Rank Moved

Rank dropped 18 spots (#295 → #313)

2026-08-22

Rank Moved

Rank rose 13 spots (#310 → #297)

2026-08-19

Rank Moved

Rank dropped 16 spots (#293 → #309)

2026-08-17

Rank Moved

Rank rose 17 spots (#307 → #290)

2026-08-16

Rank Moved

Rank dropped 12 spots (#295 → #307)

2026-08-15

Rank Moved

Rank dropped 26 spots (#269 → #295)

2026-08-13

Rank Moved

Rank dropped 17 spots (#251 → #268)

2026-08-12

Rank Moved

Rank rose 13 spots (#264 → #251)

2026-08-10

Rank Moved

Rank dropped 20 spots (#244 → #264)

2026-08-08

Newly Listed

First tracked at rank #241

GitHub → PyPI: mcpcap

Embed Badge Badge guide for maintainers →

For maintainers

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