- Home
- MCP servers
- Security Testing
Security Testing
- other
0
GitHub Stars
other
Language
6 months ago
First Indexed
3 months ago
Catalog Refreshed
Documentation & install
Readme and setup notes from the catalogue, plus a client-ready config you can copy for your MCP host.
Installation
Add the following to your MCP client configuration file.
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.
How to use
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.
How to install
Prerequisites: ensure Docker is installed on your machine and you have a network path to run containers.
- 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 .
Configuration and startup
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/catalogs
Run the MCP gateway
Start 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=stdio
Restart and connect from your MCP client
Restart 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.
Usage examples
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.
Environment variables
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.
Security and legal notes
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.
Available tools
nmap_scan
Network port scanning and service detection with multiple scan types.
nikto_scan
Web vulnerability scanning with plugin support.
sqlmap_test
SQL injection testing with advanced options.
wpscan_test
WordPress vulnerability scanning with API token support.
dirb_scan
Directory and file brute forcing with custom wordlists.
searchsploit_lookup
Exploit database searching with filters.
ping_sweep
Network discovery and connectivity testing.
custom_scan
Execute custom commands with whitelisted tools.