AI-powered penetration testing MCP server
Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"tengu": {
"command": "<see-readme>",
"args": []
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
AI-powered penetration testing MCP server
No automated test available for this server. Check the GitHub README for setup instructions.
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
No package registry to scan.
This server is missing a description. Tools and install config are also missing.If you've used it, help the community.
Add informationBe the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
An evil MCP server used for redteam testing
MCP server for Atomic Red Team
Signed receipts for agent, API, and MCP interactions. Portable and offline-verifiable.
MCP Security Weekly
Get CVE alerts and security updates for Tengu and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
"In Japanese mythology, the Tengu is a fierce mountain spirit — master strategist, warrior, and trainer of samurai. In cybersecurity, it guides you through every phase of the hunt."
From recon to report — AI-assisted pentesting in one command.
Tengu is an MCP server that turns Claude into a penetration testing copilot. It orchestrates 80 security tools — from Nmap to Metasploit — with built-in safety controls, audit logging, and professional reporting.
Use Claude as an interactive pentest copilot — you direct the engagement, Claude picks the right tools and chains them together automatically.
git clone https://github.com/rfunix/tengu.git && cd tengu
make docker-build
make docker-up
Connect Claude Code to the running server:
claude mcp add --transport sse tengu http://localhost:8000/sse
Then ask Claude: Do a full pentest on http://192.168.1.100
Claude chains tools automatically: validate_target → whatweb → nmap → nikto →
nuclei → sqlmap → correlate_findings → generate_report
| Command | What it starts |
|---|---|
make docker-up | Tengu MCP server (:8000) |
make docker-lab | + Juice Shop, DVWA (safe practice targets) |
make docker-pentest | + Metasploit, OWASP ZAP (real-world targets) |
make docker-full | + Metasploit, ZAP, and lab targets |
Scan custom targets without editing files:
TENGU_ALLOWED_HOSTS="192.168.1.0/24,10.0.0.0/8" make docker-up
Choose the right size for your use case:
| Tier | Size | MCP Tools | Use case |
|---|---|---|---|
minimal | ~480MB | 17 | Lightweight analysis, CVE research, reporting |
core | ~7GB | 47 | Full pentest toolkit (default) |
full | ~8GB | 80 | Everything + AD, wireless, stealth/OPSEC |
TENGU_TIER=minimal make docker-build # lightweight
TENGU_TIER=core make docker-build # defa
... [View full README on GitHub](https://github.com/rfunix/tengu#readme)