Unicode Security MCP
Local checks for Unicode confusables, mixed scripts, invisible controls, and suspicious identifiers.
Description from the maker (original English)
Safe, self-hosted ZAP operator for guided AI security scans and reports.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
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_KEYValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into 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"
}
}
}
}Run this in your terminal
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.1Fill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"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"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
ZAP_API_URL envZAP_API_PORT envMCP_SERVER_TOOLS_SURFACE envMCP_SECURITY_MODE envMCP_SECURITY_ENABLED envMCP_SECURITY_ALLOW_PLACEHOLDER_API_KEY envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026
The registry name was verified with the GitHub account dtkmn, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: ZAP_API_KEY, MCP_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.17.1) reached the registry 17 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Docker on your computer.
In the same category: Unicode Security MCP, Osv MCP, Epss MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Local checks for Unicode confusables, mixed scripts, invisible controls, and suspicious identifiers.
MCP server for OSV open source vulnerability data and package security checks.
Exploit Prediction Scoring System scores: how likely a CVE will be exploited in the next 30 days.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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:
Only the beginning is shown; read the rest in the repo