MCP ZAP Server

Name: MCP ZAP Server
Author: dtkmn

作者：dtkmn版本 0.17.1i★ –i在你的电脑上运行

注册名称io.github.dtkmn/mcp-zap-server

安装

概览

作者提供的说明（英文原文）

Safe, self-hosted ZAP operator for guided AI security scans and reports.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i非常新★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: Streamable HTTP
分类: 网络安全
你需要填写：ZAP_API_KEY, MCP_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： ZAP_API_URL, ZAP_API_PORT, ZAP_API_KEY, MCP_API_KEY, MCP_SERVER_TOOLS_SURFACE, MCP_SECURITY_MODE, MCP_SECURITY_ENABLED, MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

Docker已安装 Docker

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "zap": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_URL",
        "-e",
        "ZAP_API_PORT",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "-e",
        "MCP_SERVER_TOOLS_SURFACE",
        "-e",
        "MCP_SECURITY_MODE",
        "-e",
        "MCP_SECURITY_ENABLED",
        "-e",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_URL": "your-value",
        "ZAP_API_PORT": "your-value",
        "ZAP_API_KEY": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_SERVER_TOOLS_SURFACE": "your-value",
        "MCP_SECURITY_MODE": "your-value",
        "MCP_SECURITY_ENABLED": "your-value",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add zap --env ZAP_API_URL=your-value --env ZAP_API_PORT=your-value --env ZAP_API_KEY=your-value --env MCP_API_KEY=your-value --env MCP_SERVER_TOOLS_SURFACE=your-value --env MCP_SECURITY_MODE=your-value --env MCP_SECURITY_ENABLED=your-value --env MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY=your-value -- docker run -i --rm -e ZAP_API_URL -e ZAP_API_PORT -e ZAP_API_KEY -e MCP_API_KEY -e MCP_SERVER_TOOLS_SURFACE -e MCP_SECURITY_MODE -e MCP_SECURITY_ENABLED -e MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY ghcr.io/dtkmn/mcp-zap-server:v0.17.1

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "zap": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_URL",
        "-e",
        "ZAP_API_PORT",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "-e",
        "MCP_SERVER_TOOLS_SURFACE",
        "-e",
        "MCP_SECURITY_MODE",
        "-e",
        "MCP_SECURITY_ENABLED",
        "-e",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_URL": "your-value",
        "ZAP_API_PORT": "your-value",
        "ZAP_API_KEY": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_SERVER_TOOLS_SURFACE": "your-value",
        "MCP_SECURITY_MODE": "your-value",
        "MCP_SECURITY_ENABLED": "your-value",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "zap": {
      "type": "stdio",
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "ZAP_API_URL",
        "-e",
        "ZAP_API_PORT",
        "-e",
        "ZAP_API_KEY",
        "-e",
        "MCP_API_KEY",
        "-e",
        "MCP_SERVER_TOOLS_SURFACE",
        "-e",
        "MCP_SECURITY_MODE",
        "-e",
        "MCP_SECURITY_ENABLED",
        "-e",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY",
        "ghcr.io/dtkmn/mcp-zap-server:v0.17.1"
      ],
      "env": {
        "ZAP_API_URL": "your-value",
        "ZAP_API_PORT": "your-value",
        "ZAP_API_KEY": "your-value",
        "MCP_API_KEY": "your-value",
        "MCP_SERVER_TOOLS_SURFACE": "your-value",
        "MCP_SECURITY_MODE": "your-value",
        "MCP_SECURITY_ENABLED": "your-value",
        "MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

ZAP_API_URL env
Hostname or URL of a separately running ZAP daemon reachable from this container.
ZAP_API_PORT env
ZAP API port.
ZAP_API_KEY 机密必填 env
API key configured on the ZAP daemon.
MCP_API_KEY 机密必填 env
API key clients must send as X-API-Key.
MCP_SERVER_TOOLS_SURFACE env
Tool surface to expose. Use guided for the safer default workflow, including report readback. Use expert only when clients need raw ZAP tools outside the guided surface.
MCP_SECURITY_MODE env
MCP_SECURITY_ENABLED env
MCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY env

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月8日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 dtkmn 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“网络安全”中的其他服务器比较i

星标数多于此分类中其他 1004 个服务器的 0%
发布到注册中心的时间比此分类中其他 1004 个服务器的 70% 更新
基础检查结果等于或优于此分类中其他 1004 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

MCP ZAP Server 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：ZAP_API_KEY, MCP_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.17.1）于17天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Docker。

有什么可以替代它？

同一分类中有：Unicode Security MCP, Osv MCP, Epss MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：↓ 每周下载量i★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Unicode Security MCP

Local checks for Unicode confusables, mixed scripts, invisible controls, and suspicious identifiers.

作者：mrfentmen非常新↓ 50/周今天更新

在你的电脑上运行

安装

Osv MCP

MCP server for OSV open source vulnerability data and package security checks.

作者：mrfentmen非常新↓ 64/周今天更新

在你的电脑上运行

安装

Epss MCP

Exploit Prediction Scoring System scores: how likely a CVE will be exploited in the next 30 days.

作者：mrfentmen非常新↓ 152/周今天更新

在你的电脑上运行

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

MCP ZAP Server

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

Note This project is not affiliated with or endorsed by the ZAP project. It is an independent implementation.

mcp-zap-server exposes ZAP through MCP over streamable HTTP so agentic tools can run operator-controlled security workflows without brittle glue scripts or unsafe scanner access.

Use it when you want:

safe agentic scanning with guided defaults for spider, active scan, passive scan, API imports, findings, and reports
operator control through API-key or JWT auth, tool scopes, runtime policy bundles, rate limits, and audit events
self-hosted deployment with Docker Compose for local adoption and Helm for Kubernetes
one guided tool catalog with queue-managed scan starts, findings baselines, reports and explicit operator recovery

Full documentation: danieltse.org/mcp-zap-server

An experimental headless Apple Silicon package bundles Java and ZAP for HTTP workflows. It is a maintainer-built local preview; public downloads are not available, and supplied previews are unsigned. The private ChatGPT connection guide explains Secure MCP Tunnel prerequisites and access to a local scanner.

Watch the demo: browser demo or YouTube

Quick Start

Prerequisites:

Docker 20.10+
Docker Compose v2 or newer (docker compose) with --wait and --wait-timeout support
your own MCP client with Streamable HTTP and custom-header support

This source selects image v0.17.1. Verify that the matching GitHub release and Linux AMD64/ARM64 images are published before starting it. Until then, use the published v0.16.0 release or build local source through the contributor setup. Read the 0.17.1 upgrade guide before changing an existing installation. Settings and selected versions are preserved; set IMAGE_TAG in .env deliberately when upgrading.

Prefer to ask Codex to handle setup? Manually install the optional MCP ZAP Connect plugin, then ask it to check prerequisites, start the Docker stack, configure your private MCP connection and verify status. The skill can help install missing prerequisites with your approval, then recheck and continue setup. Scanning is a separate request. The commands below remain available without the plugin.

For Cursor Desktop Free, follow the guided Cursor setup. Use a local Agent chat with available Cursor allowance to set up the scanner, check status, then request a demo crawl and report separately.

Claude Code local preview uses the same scanner and setup skill in a local Claude Code session.

For Claude Desktop Free, follow the download, setup and first-scan guide. The macOS MCPB preview adds agent-callable setup tools around the same Docker scripts and reuses existing installations. Choose a scanner release that includes the Desktop .mcpb, matching guide and checksum files. If those assets are not listed, use the local build instructions. This extension is separate from the Claude Code plugin.

git clone https://github.com/dtkmn/mcp-zap-server.git

cd mcp-zap-server

./bin/bootstrap-local.sh --start

This creates missing settings, preserves existing keys and workspace data, and starts a versioned release image. It reports ready after container health and authenticated MCP checks pass. The packaged client uses * for the curated guided tools; run scans only when requested. Existing settings retain their permissions. See quick-start permissions for the default and optional per-client restrictions.

Use Self-Serve First Run for version selection, configuration, stopping/restarting, startup timeouts, and recovery. For source builds, use the contributor setup.

Connect your MCP client:

MCP endpoint for host-side clients: http://localhost:7456/mcp
Authentication: send MCP_API_KEY from .env in the X-API-Key header
MCP client setup and authentication

The stack runs the MCP server, ZAP, and demo targets. Install and configure your preferred MCP client separately.

After connecting, try this first prompt:

Use the guided ZAP tools to crawl http://juice-shop:3000. Wait for the crawl

and passive analysis to finish, show a findings summary, generate an HTML report, and read it back through MCP. Do not run an active scan.

Expect a completed crawl, a findings summary, and a report the client can read. Use the container URL http://juice-shop:3000 for this scan; the host preview http://localhost:3001 is for your browser. Finding counts vary; a connection or scan error is not a clean result.

The default stack binds published ports to loopback. Review Quick Start Security before changing access or scan-target settings. Agent install notes cover setup permissions and standalone OCI use.

Discovery Metadata

This source includes 0.17.1 MCP Registry metadata in .mcp/server.json. Metadata in source does not publish a registry version or image. Check the MCP Registry and use metadata from the same published version as the image you deploy. The image includes the MCP server name expected by registry and catalog tooling. The published 0.16.0 version and its immutable digest remain documented in the 0.16.0 release guide.

Docker Compose remains the easiest installation path because the MCP server is designed to operate with a ZAP sidecar and explicit auth keys. The OCI package metadata is for advanced standalone installs where ZAP is already running and reachable from the MCP container.

What You Get

Guided scans: intent-first tools for spider, active scan, passive scan, API imports, findings, reports, and scan history.
Guided tool catalog: policy inspection, authentication setup and queued scan operations with status and stop controls.
Authentication: API key mode by default, optional JWT mode with refresh and revocation support.
Runtime policy bundles: configured dry-run and enforcement modes for guided tool calls.
Scan queue and history: queued active, traditional spider, AJAX Spider, and Client Spider jobs with claim-based recovery, durable Postgres state, and evidence export.
Extension contracts: experimental policy, protection, evidence metadata, and extension metadata APIs with sample extension packaging.
Operational guardrails: request body limits, rate limits, workspace quotas, tool-scope authorization, structured logs, metrics, and audit events.
Deployment paths: local Docker Compose, published JVM container images, and Helm charts for Kubernetes.

See the Client Spider guide for browser setup, authenticated guided crawling and reports.

Version 0.17.1

The 0.17.1 release and upgrade guide describes neutral recorded-findings responses, authoritative explicit target denies, permission-aware next actions, and the local client setup options. Publication of the tag, images, registry version and Desktop downloads must be verified separately in GitHub Releases. Use a version with verified published images until the matching distribution is available. The v0.17.0 GitHub release is incomplete: its Desktop assets are absent and its image-release workflow did not complete. See the upgrade guide for availability checks.

Version 0.16.0

See the 0.16.0 release and upgrade guide for that release's behavior and requirements.

Version 0.15.0

See the 0.15.0 release and upgrade guide for that release's behavior and requirements.

Version 0.14.0

See the 0.14.0 release and upgrade guide for that release's behavior and requirements.

The release notes archive and changelog cover earlier versions. For changes to older MCP integrations, use Upgrading to Guided Tools. Verify the matching image and distribution in GitHub Releases before deployment.

Security Defaults

The default posture is intentionally conservative:

api-key mode is the base runtime default.
none mode is for explicit local dev/test only.
Docker Compose binds published ports to loopback by default.
The Java 25 JVM image uses a digest-pinned distroless runtime with no shell or package manager; debug it through logs, metrics, and external diagnostic containers rather than installing tools into the application container.
URL validation blocks localhost, private networks, and link-local targets by default.
Target authentication is optional and profiles default to an empty list. When enabled, guided auth binds an exact server-side credential reference and login settings to one approved origin; callers provide only profileId and targetUrl.
Public auth exchange endpoints are rate-limited.
MCP request bodies have a hard early size cap.

For a first private AWS deployment without Kubernetes, use AWS EC2 with Docker Compose and its standalone example.

For Kubernetes, use the EKS infrastructure starter to create a dedicated evaluation cluster in an existing VPC, then deploy with the existing Helm chart. Follow the walkthrough for network configuration, JWT authentication, persistent storage and deployment checks.

Production and shared deployments should review:

Security Modes
JWT Authentication
Optional Target Form-Login
[Authenticated Scanning Reference](https://danieltse.org/mcp-zap-server/scanning/authenticated-scanning-best-practices/

只显示了开头部分；其余内容请在仓库中阅读

MCP ZAP Server

概览

PopNx MCP 的三大支柱

它能帮你做什么

安装

安装之前

需要你填写的值

它能做什么

基础检查i

作者与仓库一致

仍在维护

有许可证

端点有响应

使用 OAuth 登录

工具描述中没有隐藏指令

与“网络安全”中的其他服务器比较i

常见问题

替代选择

Unicode Security MCP

Osv MCP

Epss MCP

作者的 README

Quick Start

Discovery Metadata

What You Get

Version 0.17.1

Version 0.16.0

Version 0.15.0

Version 0.14.0

Security Defaults