Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
tengu — AI-powered penetration testing MCP server | Kitploit
Tools/GitHubGitHub/rfunix/tengu
OSINT (Open Source Intelligence)Penetration Testing FrameworksReconnaissanceVulnerability ScannersExploit FrameworksWeb SecurityNetwork SecurityCloud SecurityLearning & EducationRed TeamingAI Security
588337 months agoReviewed by Kitploit

Most Popular

View all →

Discover the most used tools by our community.

Explore all tools

Browse our collection of tools

View all tools →
Share
GitHub
rfunix/tengu

tengu

AI-powered penetration testing MCP server

View Repository

Tengu — Pentesting MCP Server

Tengu

"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.

CI License Python MCP Tools Version Agent


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.

  • What is it? An MCP server that connects Claude to industry-standard pentest tools
  • Why use it? Automates recon and scanning while keeping the human in control of exploits
  • Who is it for? Pentesters, red teamers, security students, and consulting firms

Key Features

  • 80 Tools — Nmap, Metasploit, SQLMap, Nuclei, Hydra, Burp-compatible ZAP, and more
  • AI-Orchestrated — Claude decides the next tool based on previous findings
  • Safety First — Allowlist, rate limiting, audit logs, and human-in-the-loop for destructive actions
  • Auto Reports — Correlate findings and generate professional pentest reports (MD/HTML/PDF)
  • 35 Workflows — Pre-built prompts for full pentest, web app, AD, cloud, and more
  • 20 Resources — Built-in OWASP Top 10, MITRE ATT&CK, PTES, and pentest checklists
  • Stealth Layer — Optional Tor/SOCKS5 proxy routing, UA rotation, and timing jitter

MCP Server Mode (Copilot)

Use Claude as an interactive pentest copilot — you direct the engagement, Claude picks the right tools and chains them together automatically.

Tengu copilot demo

Quick Start

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

Docker Profiles

CommandWhat it starts
make docker-upTengu 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

Image Tiers

Choose the right size for your use case:

TierSizeMCP ToolsUse case
minimal~480MB17Lightweight analysis, CVE research, reporting
core~7GB47Full pentest toolkit (default)
full~8GB80Everything + AD, wireless, stealth/OPSEC
TENGU_TIER=minimal make docker-build   # lightweight
TENGU_TIER=core    make docker-build   # default
TENGU_TIER=full    make docker-build   # everything

All tiers include all 35 prompts and 20 resources — only the binary tools differ.

Manual Install (without Docker)

Prerequisites: Python 3.12+, uv, Kali Linux (recommended)

git clone https://github.com/rfunix/tengu.git && cd tengu

# Install Python dependencies
uv sync

# Install external pentesting tools (Kali/Debian)
make install-tools

# Run the MCP server (stdio transport)
uv run tengu

Connect Claude Code:

claude mcp add --scope user tengu -- uv run --directory /path/to/tengu tengu

Configure allowed targets in tengu.toml:

[targets]
allowed_hosts = ["192.168.1.0/24", "example.com"]

For Claude Desktop, VM/SSE remote setup, and advanced configurations, see docs/deployment-guide.md.

Configuration Reference

[targets]
# REQUIRED: Only these hosts will be scanned
allowed_hosts = ["192.168.1.0/24", "example.com"]
blocked_hosts = []  # Always blocked, even if in allowed_hosts

[stealth]
enabled = false  # Route traffic through Tor/proxy

[stealth.proxy]
enabled = false
type = "socks5h"
host = "127.0.0.1"
port = 9050

[osint]
shodan_api_key = ""  # Required for shodan_lookup

[tools.defaults]
scan_timeout = 300   # seconds

See docs/configuration-reference.md for the full reference.


Autonomous Agent Mode

Run a fully autonomous pentest without manual tool invocation. The agent uses Claude as its strategic brain and Tengu as its execution toolset, following the PTES methodology from recon through reporting.

Tengu autonomous agent demo

Quick Start

cp .env.example .env
# Edit .env: set ANTHROPIC_API_KEY and TENGU_AGENT_TARGET

Lab targets (Juice Shop, DVWA):

make docker-lab
make docker-agent          # default model (sonnet)
make docker-agent-haiku    # cheaper — claude-haiku-4-5, max_tokens=1024
make docker-agent-sonnet   # balanced — claude-sonnet-4-6, max_tokens=4096

Real-world pentests (Tengu + MSF + ZAP, no lab containers):

make docker-pentest
make docker-agent

View reports in browser:

make docker-report-view          # http://localhost:8888 — styled HTML, all reports
make docker-report-browse        # same, auto-opens browser
REPORT_PORT=9999 make docker-report-view   # custom port

Tengu report viewer

Without Docker:

uv sync --extra agent
python autonomous_tengu.py 192.168.1.100 --scope 192.168.1.0/24 --type blackbox

# Cost-optimised run
python autonomous_tengu.py 192.168.1.100 --model claude-haiku-4-5 --max-tokens 1024 --timeout 30

Cost control — three env vars / CLI flags:

FlagEnv varDefault
--modelTENGU_AGENT_MODELclaude-sonnet-4-6
--max-tokensTENGU_AGENT_MAX_TOKENS2048
--timeoutTENGU_AGENT_TIMEOUT60 (minutes, 0=unlimited)

How It Works

Download Tool