Getting it into your agent
One page per mod, every tool's command on it. A separate URL per tool would split the same page into five that compete with each other.
git clone --depth 1 https://github.com/bx33661/Wireshark-MCPWrote this? Show the measurements
A badge with what this costs and how it scanned, read live from this page, so it follows the numbers instead of freezing them. Markdown for a README, HTML for a documentation site or a project page.
[](https://agentmods.dev/mcp/bx33661/wireshark-mcp/mcp-wireshark-mcp)<a href="https://agentmods.dev/mcp/bx33661/wireshark-mcp/mcp-wireshark-mcp"><img src="https://agentmods.dev/badge/mcp/bx33661/wireshark-mcp/mcp-wireshark-mcp/github.svg" alt="Measured on agentmods" height="20"></a>Or the 80×15 button, for a site that already has a row of RSS and ATOM ones. Only the verdict fits; the numbers stay here.
<a href="https://agentmods.dev/mcp/bx33661/wireshark-mcp/mcp-wireshark-mcp"><img src="https://agentmods.dev/badge/mcp/bx33661/wireshark-mcp/mcp-wireshark-mcp.svg" alt="Reviewed on agentmods" width="80" height="20"></a>Grade A, and why
wireshark-mcp scanned grade A with 0 findings against 26 rules in 11 categories — prompt injection, anti-refusal, data exfiltration, privilege escalation, supply chain, agent snooping, system-prompt leakage, SSRF and excessive agency — measured 1mo ago.
A static scan of the body, not an audit. Every finding is printed with the line that produced it so you can judge whether it matters here. A mod is markdown that instructs an agent; that is exactly why what it instructs is worth reading.
Nothing flagged
None of the 26 patterns this scan looks for appear in this file: no shell pipes, no recursive deletes, no credential paths, no hidden text, no instruction-override or anti-refusal phrasing, no agent-config snooping. That is not a guarantee, it is the absence of the things that are checkable.
What it actually says
{
"wireshark-mcp": {
"command": "uvx",
"args": [
"wireshark-mcp"
],
"env": {}
}
}What this file has done since we first saw it
Hashed on every crawl. A supply-chain change to an agent config is a question of when, not whether, so the history is kept rather than the latest state alone.
- 1mo ago First seen · 9 lines scan A f0b39fc5e641
wireshark-mcp is an MCP server published in the GitHub repository bx33661/Wireshark-MCP (360 stars, last pushed 3d ago), licensed MIT. Its token cost is not measured: an MCP server costs its tool schemas, not its config file. A static security scan graded it A with 0 findings. No closer match exists in the catalogue, so it is treated as the original; first seen 2026-08-30.
Other mcp servers, from other repositories
mitm-mcp
MCP server "mitm-mcp" as configured in mplogas/mitmproxy-mcp. Runs locally from the mitm-mcp Python package.
wireshark-mcp
A Model Context Protocol (MCP) server for Wireshark / tshark packet analysis. Runs locally from the wireshark-mcp Python package.
tshark-mcp
MCP server for using TShark to analyze network packets. Runs locally from the tshark-mcp Python package.
dbgprobe-mcp-server
Debug probe Model Context Protocol server for AI agents and developer tooling. Runs locally from the dbgprobe-mcp-server Python package. Needs 9 environment variables to run.
broken-link-checker-mcp
MCP server "broken-link-checker-mcp" as configured in davinoishi/BLC-ground. Runs locally from the broken-link-checker-mcp Python package.
docs-langchain
MCP server "docs-langchain", hosted remotely at docs.langchain.com, as configured in langchain-ai/langchain.