raven-nest-mcp
MCP server for AI-driven penetration testing. Wraps 22 security tools (nmap, nuclei, sqlmap, Metasploit…) as 46 safety-hardened MCP tools for Claude and LLM agents. Written in Rust.
Install / Use
claude mcp add tidynest -- npx -y github:tidynest/raven-nest-mcpIf the server publishes to npm under a different name, use that package instead — check the repo README.
MCP Server
Model Context Protocol server
Quality Score
Category
SecuritySupported Platforms
Our assessment of raven-nest-mcp
raven-nest-mcp scores 74/100 on our quality scale, 1033rd of 1,105 Security skills we index.
Its MCP Server is 16 KB long, well organised into 35 sections with 7 code examples: a thorough specification that gives an agent plenty to work with.
It has 3 GitHub stars, so there is little community track record yet; judge it on its content.
Maintenance, license and trust
- The repository was last updated 13 days ago, so raven-nest-mcp is actively maintained.
- It is released under the Apache-2.0 license, a permissive license that allows use, modification and commercial use with attribution.
- Its trust signals score 92/100, with 1 caution from licensing, adoption, age or documentation. These come from repository metadata, not a code audit — read the skill file before letting an agent act on it.
raven-nest-mcp compared with similar skills
All 4 of these similar skills score higher than raven-nest-mcp; compare them before choosing.
| Skill | Score | Stars | Updated | Format |
|---|---|---|---|---|
| raven-nest-mcp (this skill)by tidynest | 74 | 3 | 13d ago | MCP Server |
| claude-memby thedotmack | 100 | 117.7k | today | CLAUDE.md |
| Agent-Reachby Panniantong | 100 | 112.4k | 9d ago | CLAUDE.md |
| rufloby ruvnet | 100 | 81.9k | today | CLAUDE.md |
| headroomby headroomlabs-ai | 100 | 79.9k | today | CLAUDE.md |
Frequently asked questions
- How do I install raven-nest-mcp?
- Run
claude mcp add tidynest -- npx -y github:tidynest/raven-nest-mcp. The install tabs above show the steps for each supported agent. - Which AI agents does raven-nest-mcp work with?
- It is written for Claude Code and Claude Desktop, as a MCP Server file. Other agents that read the same format can often use it too.
- Is raven-nest-mcp safe to use?
- It is Apache-2.0-licensed and scores 92/100 on trust signals. Skills are instructions an agent will follow, so read the file before installing it and do not approve commands you do not understand.
- Is raven-nest-mcp still maintained?
- The repository was last updated 13 days ago, so raven-nest-mcp is actively maintained.
Skill content
View source on GitHubRaven Nest MCP
A pentesting toolkit that runs as an MCP server, giving AI assistants structured access to industry-standard security tools through a safety-hardened interface.
Authorized use only. Raven Nest is an offensive-security tool intended solely for testing systems you own or have explicit written permission to assess. Unauthorized scanning, enumeration, or exploitation may be illegal. You are solely responsible for obtaining authorization and complying with all applicable laws. The software is provided "as is", without warranty of any kind - see LICENSE.
Demo
Real MCP traffic to the tools - no LLM in the loop, fully deterministic. Targets are the authorized public test hosts example.com / scanme.nmap.org.
Scan → structured finding → report

Recon flow - connectivity, ports, web stack

Metasploit module discovery - requires an MSF-enabled build; the default container image excludes Metasploit

What It Does
Raven Nest wraps 22 security tools plus Metasploit Framework behind an MCP interface with input validation, output quality assessment, session-aware context budgeting, and configurable safety limits. It handles tool execution, restart-safe background scans (completed results survive a server restart; interrupted ones surface as failed), vulnerability finding persistence, target discovery tracking, scan diffing, and multi-format report generation (Markdown, JSON, SARIF, HTML). Findings, reports, and scans are also exposed as MCP resources for browsing. 46 MCP endpoints total.
Supported Tools
| Category | Tools | |----------|-------| | Recon | nmap, masscan, whatweb, httpx, subfinder, dnsx, dnsrecon | | Crawling | katana | | SMB/AD | enum4linux-ng | | Credentialed enum (gated) | netexec | | Vulnerability | nuclei, nikto, wpscan, dalfox (XSS) | | Web fuzzing | feroxbuster, ffuf | | Exploitation | sqlmap, hydra | | Password cracking | john | | Secret scanning | gitleaks, trufflehog | | TLS/SSL | testssl.sh | | Metasploit | msf_search, msf_module_info, msf_exploit, msf_auxiliary, msf_sessions, msf_post | | Utility | ping_target, http_request | | Scan management | launch_scan, get_scan_status, get_scan_results, list_scans, cancel_scan | | Findings | save_finding, get_finding, list_findings, list_findings_by_scan, delete_finding, generate_report | | Engagement | set_engagement, list_engagements | | Discovery tracking | get_target_info, list_targets, diff_scans |
How It Fits Together
Raven Nest is an MCP server - it doesn't do anything on its own. An MCP host launches it over stdio and drives the tools. Pick whichever host suits you:
- Any MCP host (recommended) - point Claude Desktop, Cursor, or any MCP client at the Docker image below; the host spawns the server for you.
- Companion REPL -
raven-nest-clientis a TypeScript terminal client (tab-completion, scan/finding/report commands, engagement scoping) for driving Raven Nest by hand. It can launch either a localraven-serverbuild or the Docker image.
The server is the same stdio binary in both cases.
Quick Start
Run with Docker (recommended)
The published image bundles raven-server and all 22 wrapped tools on a Kali
base, so you don't have to install them yourself. Point your MCP client at it
(stdio):
{
"mcpServers": {
"raven-nest": {
"command": "docker",
"args": ["run", "--rm", "-i", "ghcr.io/tidynest/raven-nest-mcp:latest"]
}
}
}
masscan and nmap -O need raw sockets - append --cap-add=NET_RAW and
--cap-add=NET_ADMIN to args if you use them (the container runs as a
dedicated non-root user; the runtime grants those capabilities to the container
process directly, so they keep working without root). The server is also listed
on the MCP Registry as
io.github.tidynest/raven-nest-mcp.
Prerequisites
- Rust 1.93+ (2024 edition)
- One or more external tools installed (nmap, nuclei, nikto, etc.)
Build
cargo build --release
Configure your MCP client
Create .mcp.json in your project root (or configure your MCP client directly):
{
"mcpServers": {
"raven-nest": {
"command": "/path/to/raven-server",
"args": []
}
}
}
The server communicates over stdio and requires no network ports.
Configuration
Raven Nest loads configuration from TOML, resolved in order:
RAVEN_CONFIGenvironment variable (path to file)config/default.tomlnext to the binaryconfig/default.tomlin the working directory- Built-in defaults
Key configuration sections:
[safety]
allowed_tools = ["nmap", "nuclei", "nikto", "whatweb", "masscan", ". . ."]
context_budget = 65536 # Model context window in chars (0 = disabled)
expected_tool_calls = 10 # Anticipated calls per session
sudo_tools = ["masscan", "nmap"] # Tools invoked via passwordless sudo
# auto_save_findings = false # opt-in: auto-extract findings from scanners
[execution]
default_timeout_secs = 600
max_concurrent_scans = 3
output_dir = "/tmp/raven-nest"
# [scope] # engagement authorization allowlist (deny-wins)
# enabled = true
# allowed_domains = ["example.com"]
# [network]
# http_proxy = "http://127.0.0.1:8080"
# [metasploit]
# enabled = true
# host = "127.0.0.1"
# port = 55553
# password = "changeme"
# [netexec] # gated, read-only credentialed enumeration
# enabled = true
See docs/USAGE.md for the full parameter reference and per-tool configuration options.
Safety Architecture
Every tool call passes through six layers:
- Allowlist -- only explicitly permitted tools can execute
- Input validation -- targets must be valid IPs, hostnames, CIDRs, or URLs; shell metacharacters are rejected
- Preset arguments -- users pick scan types, never raw CLI flags
- Execution containment -- configurable timeouts with
kill_on_drop - Output sanitisation -- ANSI stripping, truncation at configurable limits (UTF-8 safe)
- Quality assessment -- detects empty results, rate-limiting, and WAF blocks
Additional hardening:
- Config validation at startup -- safety limits (sqlmap level/risk, hydra tasks, masscan rate) are range-checked; the server refuses to start with out-of-range values or default MSF credentials
- Wordlist path validation -- hydra, john, feroxbuster, and ffuf only accept wordlists under
/usr/share/,/usr/lib/, or the configuredoutput_dir; path traversal (..) is rejected - Positional-argument guards -- free-text values passed to tools as positional arguments are charset-checked so they can't be re-parsed as flags: hydra
service(lowercase/digits/hyphens) andform_params(no leading-, no control chars), sqlmaptechnique(subset ofBEUSTQ), ffuffilter_size(digits/commas). Targets get the same treatment (-oN/tmp/evilis rejected as flag-like) - Port spec validation -- nmap and masscan port parameters accept only digits, commas, and hyphens
- File permissions -- cookie files and scan spill files are created with
0o600(owner-only) - Markdown escaping -- report generation escapes user-supplied finding fields to prevent markdown injection
- Finding ID validation -- finding get/delete operations require valid UUID format, preventing path traversal
- Engagement scope -- an optional authorization allowlist (
[scope]): when enabled, every target must match an allowed CIDR/domain and must not match a denied one (deny wins); loopback is allowed unless disabled.http_requestre-validates each redirect hop against the scope, so a redirect cannot escape it. Off by default - Audit logging -- every tool execution is appended to
{output_dir}/audit.logwith the tool, target, and redacted arguments - Proactive cooldown -- an optional
min_exec_gap_msspaces out consecutive tool launches so back-to-back aggressive tools don't trip a target's WAF or rate-limiter, andper_target_min_gap_msdoes the same per host while independent targets proceed in parallel; complements the reactive WAF/rate-limit detection. Both off by default
Metasploit integration adds a 5-layer safety model: disabled by default, per-tool allowlisting, path-boundary module blocklist, exploit confirmation gate (double-call to execute), and session command filtering. Passwords are redacted from error messages, and TLS certificate bypass is restricted to localhost connections. See docs/METASPLOIT.md.
Tools requiring root (masscan, nmap OS detection) can be run via passwordless sudo without elevating the entire server. See sudo_tools in the configuration docs.
Context Budget
A session-aware context budget tracker dynamically adjusts per-tool output caps based on remaining context window space. This prevents context overflow on local AI models with limited context windows (49-64K tokens).
- Full mode -- all findings, all details, up to 8K chars per tool call
- Compact mode -- top-N results, critical/high findings only (triggers at 40% consumed)
- Minimal mode -- one-line summaries (triggers at 70% consumed)
Parser result caps scale dynamically via scale_cap() -- each tool's output parser adjusts its result limit based on the active budget mode. All tool output passes through centralised ANSI stripping and budget-aware truncation in wrap_result().
When the budget is exhausted, the server returns a message directing the AI to save findings and generate a report rather than running additional scans.
Target Discovery Tracking and Scan Diffing
Every nmap result (run_nmap and background nmap scans) accumulates into a
per-host discovery record: ports, states, services, versions, and OS guesses,
with first/last-seen timestamps. Re-scanning merges rather than overwrites, so
the record shows how the target evolved.
list_targets/get_target_inforecall the tracked hosts and full per-host service tables without re-scanning.diff_scanscompares two completed nmap scans: added/removed hosts and ports, plus per-port state/service/version changes (open (ssh OpenSSH 8.9) → open (ssh OpenSSH 9.0)).- Discovery data is engagement-scoped like findings (
{engagement}/targets/) and persists across restarts.
run_nmap and run_nuclei also attach machine-readable structured_content
to their responses (hosts/ports/CVEs; findings list), uncapped by the context
budget, so clients can process results without parsing prose.
Report Generation
The generate_report endpoint produces a structured report -- Markdown by default, or JSON, SARIF, or HTML via the format parameter -- containing:
- Table of Contents with linked findings
- **Execut
Truncated for display — read the full file on GitHub.
Related Skills
claude-mem
117.7kPersistent Context Across Sessions for Every Agent – Captures everything your agent does during sessions, compresses it with AI, and injects relevant context back into future sessions. Works with Claude Code, OpenClaw, Codex, Gemini, Hermes, Copilot, OpenCode + More
Agent-Reach
112.4kGive your AI agent eyes to see the entire internet. Read & search Twitter, Reddit, YouTube, GitHub, Bilibili, XiaoHongShu — one CLI, zero API fees.
ruflo
81.9k🌊 The original agent harness. Deploy intelligent multi-player swarms, coordinate autonomous workflows, and build conversational AI systems. Features adaptive memory, self-learning intelligence, federation, vector RAG integration, and native Claude Code / Codex / Hermes and many more Integrated
headroom
79.9kCompress tool outputs, logs, files, and RAG chunks before they reach the LLM. 20% fewer tokens for coding agents, 60-95% fewer tokens for JSON, same answers. Library, proxy, MCP server.
Languages
Trust signals
From repository metadata: license, adoption, age and documentation. Not a code audit — see the Safety scan above for what the skill file itself contains.
