Automation & Ops penetration-testingctfmcpvulnerability-scanningexploit-development

VulnClaw

AI-driven penetration testing CLI that turns natural language into a full pentest workflow: recon, discovery, exploitation, and reporting.

FollowAgents review · FARS-2.1
Not recommended
48/ 100 5-point scale 2.4 / 5
1 2 3 4 5 6
1Trust11 / 29 · 1.9/5

Evidence shows: README declares authorized use, security statement, and sandbox prompts, but no actual permission control details; user confirmation mechanisms exist (e.g., TUI scope confirmation), but not all operations require confirmation; data flow transparency is good with AgentState evidence recording and traffic storage; sensitive data handling (API key storage) not detailed; dependency security not mentioned vulnerability scanning or pinning; external effects (e.g., network scanning) have authorization statements but no technical restrictions; rollback has target state snapshots and rollback functionality; source attribution has author info but unverified. Deductions: least privilege, user confirmation, sensitive data handling, dependency security, external effects, rollback, and source attribution lack concrete implementation evidence.

2Reliability6 / 14 · 2.1/5

Evidence shows: README and test files are internally consistent, module division clear; dependencies declared in pyproject.toml, but availability not verified; failure messages mentioned (e.g., stall guard), but no specific error handling examples. Deductions: dependency availability unverified, failure message details insufficient.

3Adaptability12 / 18 · 3.3/5

Evidence shows: clearly targets authorized pentesting, CTF, teaching scenarios; capability boundaries have security statements and authorization requirements; trigger precision has natural language keyword triggers and explicit commands; environment fit has Docker, multi-platform CI, and multiple LLM providers. Deductions: capability boundaries not detailed to specific tool limits, trigger precision may be imprecise due to natural language.

4Convention9 / 18 · 2.5/5

Evidence shows: README structure clear with installation, usage, architecture, configuration sections; installation instructions detailed (pip, source, Docker); naming stable (vulnclaw command); examples and FAQ present (REPL examples); known limitations mentioned (e.g., python_execute not sandbox); license MIT; version in pyproject.toml, but no CHANGELOG content; maintenance responsibility has contribution guide but no clear maintainer. Deductions: naming stability not verified historically, known limitations not comprehensive, version changelog missing, maintenance responsibility unclear.

5Effectiveness7 / 13 · 2.7/5

Evidence shows: output usability has report and PoC generation; marginal value high with full-process automation; cost-benefit lacks actual performance data. Deductions: cost-benefit lacks data support.

6Verifiability3 / 8 · 1.9/5

Evidence shows: README feature claims have some test coverage (e.g., test files), but no specific evidence links; cross-source verification insufficient, relying only on single repository; fact-inference separation unclear. Deductions: claim traceability insufficient, cross-source verification missing, fact-inference not clearly separated.

Evidence confidence: Low Reviewed Aug 11, 2026 Reviewed revision 76b14c34f1d5
Before you use it
  • This is a penetration testing tool; must only be used on authorized targets, otherwise illegal.
  • python_execute and shell_command tools are not strong isolation sandboxes, posing code execution risks.
  • Dependencies are not pinned, posing supply chain risks.
  • API key storage method is not clear; handle with caution.
Review evidence [1][2][3][4][5][6][7]
See the full review method →

What does this agent do, and when should you use it?

VulnClaw is an AI-powered penetration testing CLI (Python 3.10+, MIT license) that combines an LLM Agent with the MCP toolchain and Skill references. It accepts natural language input and automatically executes the complete pentest flow—from information gathering to vulnerability exploitation—and generates structured Markdown reports and Python PoC scripts. The default model-driven 'solve' engine lets the model decide each step, backed by an AgentState evidence memory and an anti-hallucination gate that only accepts claims found verbatim in real tool outputs. It supports 14 LLM providers (OpenAI, Anthropic, MiniMax, DeepSeek, Zhipu, Moonshot, Qwen, SiliconFlow, Doubao, Baichuan, StepFun, SenseTime, Yi, and local Ollama) and optional MCP services (fetch, memory, chrome-devtools, burp). Delivery modes include CLI, REPL, TUI, a Web UI, and Docker. It bundles 50 specialized Skills covering CTF, web, intranet, and reverse engineering, plus built-in tools for encoding/decryption, batch HTTP probing, runtime differential analysis, and more. Intended only for authorized security testing.

VulnClaw takes a natural language command such as 'pentest http://target.example.com' and executes an autonomous multi-round loop. It uses the built-in fetch tool (based on httpx) to send HTTP/HTTPS requests with configurable methods, headers, params, cookies, and bodies; http_probe_batch to compare multiple URL/parameter/header variants in one pass; nmap_scan for port scanning; crypto_decode for encoding/decryption (29 operations); python_execute to run Python code; shell_command for local commands (e.g., php -r, curl, rg); source_extract to pull clean source code from HTML; runtime_diff_probe to test filter/parser inconsistencies; brute_force_login for login brute-forcing; and load_skill_reference to fetch Skill documents on demand. Every tool result is written into AgentState.evidence, which the model can query via evidence_search/evidence_view. Finally, the solve engine deterministically generates a Markdown retrospective report including the reasoning path, key evidence, reproducing request packets, curl commands, response snippets, and an evidence index—plus a runnable Python PoC script.

  1. Authorized penetration testing: Security testers assess targets they own or have explicit permission to test, describing the objective in natural language and letting the agent handle recon and exploitation.
  2. CTF competitions: Competitors use VulnClaw to automate web challenge probing, leveraging the ctf-web, ctf-crypto, and ctf-misc knowledge bases, while the anti-hallucination gate prevents false flag claims.
  3. Security training: Instructors demonstrate pentest methodology in lab environments, and students observe model decisions and tool calls to learn attack chains.
  4. Red team exercises: Red teamers run long-duration persistent mode (vulnclaw persistent) for deep assessments, with auto-generated reports each cycle and support for incremental discoveries.
  5. Rapid vulnerability validation: Researchers use single-command modes like vulnclaw scan --ports 80,443 for quick port scans or vulnclaw exploit --cve CVE-2024-1234 to verify specific vulnerabilities.

What are this agent's strengths and limitations?

Pros
  • Model-driven solve engine: the model decides each step, adapting to unknown targets rather than following a fixed script.
  • Evidence-level anti-hallucination gate: conclusions are only accepted if they match real tool output verbatim or cite an evidence ID, preventing fabricated flags.
  • 14 LLM providers including local Ollama, reducing vendor lock-in.
  • Rich built-in toolchain: fetch, http_probe_batch, crypto_decode, python_execute, shell_command, and more work out of the box.
  • Comprehensive Skill library: 50 skills covering CTF, web, intranet, reverse engineering, etc., loaded on demand to avoid context bloat.
Limitations
  • Public Alpha stage: not yet stable for production security use.
  • Relies on external LLM APIs: requires API keys and may incur significant costs in long sessions.
  • High-risk experimental features: python_execute and shell_command can run arbitrary code; sandboxing is the user's responsibility.
  • MCP services (chrome-devtools, burp) require extra deployment and configuration.
  • Documentation is primarily in Chinese; English support is limited.

How do you install or deploy this agent?

Install from PyPI (recommended):

pip install vulnclaw

Or from source:

git clone https://github.com/Netw0rkNoob/VulnClaw.git
cd VulnClaw
pip install -e .

Optional Docker deployment:

cp .env.example .env  # fill in VULNCLAW_LLM_API_KEY etc.
docker compose up --build
# open http://127.0.0.1:7788

Requires Python 3.10+. You must configure an LLM API key before use.

How do you use this agent?

  1. Choose a provider: vulnclaw config provider minimax (or openai/anthropic/deepseek, etc.)
  2. Set the API key: vulnclaw config set llm.api_key sk-your-key-here
  3. Launch the REPL: vulnclaw
  4. Type a natural-language instruction like "pentest 192.168.1.100"

Common commands:
- vulnclaw solve target.com --goal "find the flag" — goal-driven solve
- vulnclaw run 192.168.1.100 — one-shot full pentest
- vulnclaw recon target.com — recon only
- vulnclaw scan target.com --ports 80,443 — vulnerability scan
- vulnclaw exploit target.com --cve CVE-2024-1234 --cmd id — exploit step
- vulnclaw report session.json — generate report
- vulnclaw web — start the Web UI (default 127.0.0.1:7788)
- vulnclaw tui — start the TUI workbench

Run vulnclaw doctor to verify the environment. Optionally configure MCP servers (e.g., chrome-devtools and burp) for browser automation and HTTP interception.

How does this agent compare with similar options?

Unlike traditional frameworks such as Metasploit, VulnClaw's core is an LLM agent that makes autonomous decisions rather than composing predefined modules. Compared to general coding agents like Codex or Claude Code, VulnClaw is specialized for security testing, with built-in evidence gates, WAF bypass libraries, and a CTF-oriented skill set.

FAQ

What are the prerequisites for using VulnClaw?
Python 3.10+ and an LLM API key (any of the 14 supported providers). Optionally Node.js and Chrome for chrome-devtools MCP, and Burp Suite for the burp MCP.
Does VulnClaw automatically exploit vulnerabilities?
Yes, it includes an exploit stage with PoC verification and privilege escalation, but you must have authorization for the target.
What report formats are supported?
It generates Markdown reports and Python PoC scripts by default, and can be configured to output HTML.
How does VulnClaw handle LLM failures or timeouts?
It has failure fallback and timeout controls; you can adjust settings like session.max_rounds.
Can VulnClaw run offline?
Yes, using a local Ollama as the LLM provider allows offline operation, though network may still be needed for some tools like nmap.

Compare agents like this one

The same FARS review applied across the shortlist this agent qualifies for.

Related agents