The split architecture is the design: the tools live on Kali, the MCP server can sit elsewhere and talk over HTTP. Beyond running nmap or sqlmap, it manages persistent SSH and reverse-shell sessions with status and cleanup, and file transfers are checksum-verified. This is offensive tooling — run it against systems you are authorized to test, in the Docker test mode while you learn it.
A two-part server — a Kali-side service holding the tools, and an MCP server that talks to it over HTTP — exposing 31 tools for scanning, exploitation and session management.
- Scanning and exploitation — nmap_scan, gobuster_scan, dirb_scan, nikto_scan, sqlmap_scan, hydra_attack, wpscan_analyze, enum4linux_scan, run_john_crack and metasploit_run
- SSH sessions — start_ssh_session, execute_ssh_command, get_ssh_status, stop_ssh_session and list_ssh_sessions
- Reverse shells — start_reverse_shell_listener, execute_shell_command, get_shell_status, stop_reverse_shell and list_reverse_shell_sessions
- File transfer with SHA256 verification — upload_to_kali, download_from_kali, plus SSH and reverse-shell transfer with chunking for large files
- execute_command for arbitrary commands and server_health for status; a --test flag spins up a Docker environment
The Kali-side service runs on Kali Linux and needs the penetration-testing tools installed; the MCP server can run on any system and reaches it over HTTP, so the two can be on different machines. Configure the MCP client to connect to the Kali server per install.md. The --test option manages Docker test containers with SSH on localhost:2222 and reverse-shell listeners on 4444 and 4445.