home / mcp / security testing mcp server
Provides penetration testing tools via MCP gateway for educational and authorized security testing.
Configuration
View docs{
"mcpServers": {
"avi686-security-mcp-server": {
"command": "docker",
"args": [
"run",
"-i",
"--rm",
"--network=host",
"-v",
"/var/run/docker.sock:/var/run/docker.sock",
"-v",
"/path/to/your/home/.docker/mcp:/mcp",
"docker/mcp-gateway",
"--catalog=/mcp/catalogs/docker-mcp.yaml",
"--catalog=/mcp/catalogs/custom.yaml",
"--config=/mcp/config.yaml",
"--registry=/mcp/registry.yaml",
"--tools-config=/mcp/tools.yaml",
"--transport=stdio"
],
"env": {
"MAX_THREADS": "10",
"SCAN_TIMEOUT": "300",
"DIRB_WORDLIST": "common.txt",
"DEFAULT_INTENSITY": "T3"
}
}
}
}You can use this MCP server to run educational penetration testing tools via a centralized MCP gateway. It provides a safe, authorized way to explore popular Kali Linux tools through standardized MCP workflows, enabling you to perform security testing in a controlled environment.
Interact with the MCP gateway from your MCP client to run security testing tools. You will dispatch tool requests such as port scans, web vulnerability checks, and directory brute forcing through a consistent MCP interface. The gateway coordinates tool execution, collects results, and returns structured responses for your workflow.
Prerequisites: ensure Docker is installed on your machine and you have a network path to run containers.
1. Clone the project repository and build the container image.
git clone https://github.com/avi686/security-mcp-server.git
cd security-mcp-server
docker build -t security-mcp-server .Set up MCP configuration and register catalogs for your gateway setup. You will reference both the default MCP catalogs and your custom catalog when starting the gateway.
mkdir -p ~/.docker/mcp/catalogsStart the gateway container with the required catalogs and configuration. The gateway runs as a stdio MCP server and connects to your local MCP catalogs and registry.
docker run -i --rm --network=host \
-v /var/run/docker.sock:/var/run/docker.sock \
-v /path/to/your/home/.docker/mcp:/mcp \
docker/mcp-gateway \
--catalog=/mcp/catalogs/docker-mcp.yaml \
--catalog=/mcp/catalogs/custom.yaml \
--config=/mcp/config.yaml \
--registry=/mcp/registry.yaml \
--tools-config=/mcp/tools.yaml \
--transport=stdioRestart your MCP client (Claude Desktop or other client) to establish a connection to the gateway. Ensure your client references the gateway with the correct stdio transport and the included catalogs.
You can issue requests like scanning a host for open ports, testing a WordPress site, or performing SQL injection tests through the gateway. Typical examples include asking the client to run an nmap scan or a nikto scan against a target.
Adjust tool behavior with environment variables as needed. Common controls include timeouts, intensity, wordlists, and thread counts. Use the exact variable names shown in your environment configuration.
Use only with proper authorization and in compliance with all applicable laws. Do not scan systems you do not own or have explicit permission to assess. Handle results responsibly and protect any data you encounter.
Network port scanning and service detection with multiple scan types.
Web vulnerability scanning with plugin support.
SQL injection testing with advanced options.
WordPress vulnerability scanning with API token support.
Directory and file brute forcing with custom wordlists.
Exploit database searching with filters.
Network discovery and connectivity testing.
Execute custom commands with whitelisted tools.