MCP ZAP Server runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 30 Oct 2026.
Safe, self-hosted ZAP operator for guided AI security scans and reports.
What the code does
We read the source, 2 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
subprocess.run(["tar", "--uid", "0", "--gid", "0", "--uname", "root", "--gname", "root",
child = spawn(command, args, { cwd, env, shell: false, detached: process.platform !== 'win32', stdio: ['ignore', 'pipe', 'pipe'] });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to MCP ZAP Server
same job, measured the same wayTrigger security scans and read reports/vulnerabilities via the hosted Scannd API. Free: 2 scans/mo.
MCP server for SecObserve: triage findings, import scan reports and SBOMs, generate VEX.
Offline security scanning for AI-generated code: seven open-source scanners in one MCP server.
MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.
MCP server for self-hosted Laserfiche repositories — search and read documents from Claude.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
MCP server for Rootly — incidents, alerts, escalations, and post-incident reports.
MCP server for Huntress — accounts, organizations, agents, incidents, and reports.
MCP ZAP Server — questions
Answers built from our own checks of this server.