Is Wireshark MCP safe to use?

Wireshark MCP has an HVTrust score of 62.2/100 (Grade C), ranked #296 of 1283 tracked AI agent projects. This score reflects verifiable supply-chain integrity, transparency, maintenance, and adoption signals.

What is the trust score for Wireshark MCP?

Wireshark MCP scores 62.2/100 on HVTracker's evidence-weighted HVTrust scale. It has 197 GitHub stars and is categorized under MCP Servers.

Wireshark MCP

bx33661/Wireshark-MCP

Wireshark-MCP，Give your AI assistant a packet analyzer. Drop a .pcap file, ask questions in plain English — get answers

MCP Servers Python Grade C Listed MIT

62.2/100

Rank #296 of 1283

Compare Wireshark MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →

Promising trust profile, but some evidence still deserves review.

Open compare tool Suggest correction

Listing state

Listed

Evidence coverage

Grade B · 3/5 signals

Last push

2026-08-03 · 9d ago

Recent change

Rank +1

Is Wireshark MCP safe? Wireshark MCP scores 62.2/100 (Grade C), ranked #296 of 1283 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; no OSSF Scorecard result yet; recent commits are unsigned; last pushed 2026-08-03. Every point is earned from checkable signals — never paid placement. How scoring works →

Ranked neighbours in MCP Servers

#98 Excel Vision MCP — 62.4 (C) → #99 YADE MCP Server — 62.2 (C) → #101 FHIR MCP Server — 62.0 (C) → #102 Robinhood Portfolio Research — 61.8 (C) →

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 18 spots (#274 → #292)

2026-08-08

Newly Listed

First tracked at rank #268

Maintainer Checklist

Add Scorecard coverage Expose the repository to OpenSSF Scorecard checks so supply-chain posture is easier to verify.

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

54.5

Activity sub-score · out of 100

#100

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 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-08-12

Activity & Reach

Stars

197

Forks

Last Push

2026-08-03

9 days ago

Commits (4 wk)

Downloads (7d)

453

pypi

HN mentions (30d)

—

Open Issues

Rank Change

▲1

was #297

Analysis

HVTrust Dimensions vs MCP Servers

62.2 / 100 · 100.0% confidence

Wireshark MCP MCP Servers average (761 agents)

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

7.5 / 25

2.5 above avg 5.0

Identity / Provenance60% listing status · 40% build provenance

18.0 / 18

4.7 above 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

13.1 / 20

0.7 above avg 12.4

AdoptionLog-scaled stars · package downloads

9.1 / 20

3.3 above avg 5.8

Activity Inputs

54.5 / 100

StarsRepository reach

13.8 / 30

FreshnessLast push recency

23.8 / 25

ActivityRecent commits

10.5 / 25

CommunityFork signal

6.3 / 20

Supply Chain Trust

Package Provenance

Verified

pypi attestation

OSSF Scorecard

—

Not available

Signed Commits

of last 100 commits verified

Is Wireshark MCP safe?

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

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

Does Wireshark MCP have an OpenSSF Scorecard?

No OpenSSF Scorecard data is currently published for Wireshark MCP. 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 Wireshark MCP actively maintained?

Maintained. Last push was 9 days ago.

What license does Wireshark MCP use?

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

Are Wireshark MCP's commits signed?

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

Wireshark MCP 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

Maintain Wireshark MCP?

For maintainers

HVTrust scores Wireshark MCP 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-08-10

Rank Moved

Rank dropped 18 spots (#274 → #292)

2026-08-08

Newly Listed

First tracked at rank #268

GitHub → PyPI: wireshark-mcp

Embed Badge Badge guide for maintainers →

For maintainers

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