Action1 MCP by usefulapi
Read endpoints, missing updates, CVE vulnerabilities, installed software and reports in Action1.
作者による説明(英語の原文)
Safe, self-hosted ZAP operator for guided AI security scans and reports.
この3つを1つのスコアにまとめることはしません。意見、測定、人気はそれぞれ別のものだからです。
このサーバーのやさしい解説はまだ書いていません。以下はレジストリから読み取った事実です。
使っているAIアプリを選んで、設定をコピーしてください。
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「秘密」と表示された値は、あなたのアカウントの鍵です。絶対に人に教えたり、チャットに貼り付けたりしないでください。
必要なもの
どのアプリを使っていますか?
上でアプリを選んでください。選んだアプリを覚えておくので、次からはボタンに「…にインストール」と表示されます。
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/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"
}
}
}
}ブラウザがアプリを開いてよいか確認し、そのあとアプリが設定を表示して確認を求めます。キーの値は空欄のままなので、自分で入力してください。
プロジェクトの .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 envZAP_API_PORT envMCP_SERVER_TOOLS_SURFACE envMCP_SECURITY_MODE envMCP_SECURITY_ENABLED envMCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY envこの設定は、作者のレジストリ登録情報から作成しています。READMEと違う場合は、READMEに従ってください。
パソコンで動くサーバーです。インストールすると、ツール一覧がAIアプリに表示されます。
誰でも見られる情報をチェックしており、コードは読んでいません。当てはまらない項目は数に入れていません。 · 2026年11月8日にチェック
レジストリ名は、リポジトリを所有するGitHubアカウント dtkmn で確認済みです
このリポジトリはまだGitHubから読み取っていません
このリポジトリはまだGitHubから読み取っていません
これはパソコンで動くため、インターネット上のエンドポイントはありません
パソコンで動き、代わりにローカルの設定を使います
パソコンで動くサーバーです。ツール一覧を読み取れるのは、インターネット上のエンドポイントがある場合だけです
レジストリでこのカテゴリにある有効なすべてのサーバーと比較しています。スターは、公開者がリポジトリの所有者である場合だけ数えます。
当てはまる基本チェック1項目のうち1項目に合格しました。コードは読んでいません。キーやトークンを追加する前に、サーバーがどんなアクセスを求めているかを確認し、必要な権限だけを持つキーを使ってください。
入力が必要なもの:ZAP_API_KEY, MCP_API_KEY
あなたのパソコンで動きます。必要なときにAIアプリが起動し、データは作者のサーバーを通りません(サーバー自体がオンラインサービスを呼び出す場合を除きます)。
GitHubリポジトリの最終更新は–、最新バージョン(0.17.1)がレジストリに届いたのは16 日前です。
Claude Desktop、Claude Code、Cursor、VS CodeなどのMCP対応アプリで使えます。パソコンにDockerも必要です。
同じカテゴリには:Action1 MCP by usefulapi, ipdata MCP by usefulapi, MaxMind minFraud MCP by usefulapi
同じカテゴリで、ほかの作者が作ったサーバー。スターの多い順。
カードの見方:★ GitHubスターi3つの柱:レビュー · チェック · 利用状況i更新=最新バージョンをレジストリに公開した日i
Read endpoints, missing updates, CVE vulnerabilities, installed software and reports in Action1.
Look up location, network, company and threat data for IP addresses and ASNs in ipdata.
MCP server for MaxMind minFraud — score transactions for fraud risk from your AI assistant.
作者のリポジトリから書かれたとおりにコピーしたものです。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:
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
Prerequisites:
docker compose) with --wait and --wait-timeout supportThis 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:
http://localhost:7456/mcpMCP_API_KEY from .env in the X-API-Key headerThe 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.
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.
See the Client Spider guide for browser setup, authenticated guided crawling and reports.
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.
See the 0.16.0 release and upgrade guide for that release's behavior and requirements.
See the 0.15.0 release and upgrade guide for that release's behavior and requirements.
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.
The default posture is intentionally conservative:
api-key mode is the base runtime default.none mode is for explicit local dev/test only.profileId and targetUrl.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:
冒頭だけを表示しています。続きはリポジトリで読めます