runLABSCO SUMMARY
A Kali box an agent can drive, with the whole assessment lifecycle exposed as tools.
Instead of one wrapper per binary, it maps the actual stages of an engagement — recon, enumeration, scanning, credential testing, payload generation — onto tools an assistant can chain, with the tooling isolated in a container rather than installed on your machine.
What it is
A Kali Linux container that speaks MCP. The security tools run inside the container and the results come back to your client, over SSE or stdio.
What you get
- Reconnaissance: port scanning with nmap presets, DNS and subdomain enumeration, network discovery, and an automated recon pass that chains them
- Web assessment: site spidering, form and header analysis, TLS inspection, web enumeration, and a combined web audit
- Vulnerability work: a vulnerability scan, plus exploit search against the software it identifies
- Credential testing with hydra, and a credential store so the same set is not re-entered on every call
- Payload and reverse-shell generation for the target you name
Requirements
Docker — build the image or run it with docker compose. The container listens on port 8000; your client connects over SSE at http://localhost:8000/sse, or over stdio. Everything executes inside the container, so what it can reach is what that container can reach.
Setup effort
Run a container — build the image from the repository, then point your client at it
USE CASES
Mapping an unfamiliar host from scratch
Start with the automated recon pass, then narrow: a port scan with the right preset, DNS enumeration, and the subdomains that did not show up anywhere obvious.
Auditing a web application you are responsible for
Spider the site, then read what the crawl found — forms, response headers and TLS configuration — pulled together as one audit.
Turning a scan result into a known issue
Run the vulnerability scan, then search for public exploits matching what it identified, so the finding arrives with its context.
Testing whether credentials hold up
Point hydra at the service, keeping the credential set in the store rather than in every call.
Seeing what the network looks like from inside
Discover live hosts, enumerate what they serve, and prepare a payload or a callback for the box you have agreed to test.
35 tools
Listed in project docs. Your client may show a different list.
fetchresourcesport_scandns_enumnetwork_discoverysubdomain_enumrecon_autovulnerability_scanweb_enumerationweb_auditspider_websiteform_analysisheader_analysisssl_analysishydra_attackcredential_storepayload_generatereverse_shellexploit_searchencode_decodehash_identifyenum_sharesparse_nmapparse_tool_outputsave_outputcreate_reportfile_analysisdownload_filesession_createsession_listsession_switchsession_statussession_deletesession_historyBEFORE YOU INSTALL
What to know first
Tools you get
35 tools named in the project's documentation.
Requires
docker on PATH
INSTALLATION
Connect your client
Build the image from the repository, then point your client at it.
Server setup
git clone https://github.com/k3nn3dy-ai/kali-mcp
cd kali-mcp
docker compose up --build -d