Offensive-security MCP server from pentest-ai that lets Claude list and run wrapped security tools, plan and install missing tools, launch authorized engagements, run web, recon, API, cloud, AD, credential, vulnerability, mobile, wireless, and LLM-red-team assessments, and retrieve findings, attack chains, reports.
by 0xSteph · submitted by oktofeesh1·added 2026-06-06·1,391 source repo stars·
Pentest AI is offensive security tooling that performs real network and host operations and can run wrapped scanners, fuzzers, password tools, exploit-adjacent probes, and custom HTTP requests., Use only on targets where you have written permission, and keep rules of engagement, exclusions, rate limits, credentials, and scope boundaries in the prompt and engagement record., Prefer intensity=safe, strict_scope=true, and respect_rate_limits=true for real targets; the upstream README notes these safety flags are not all default behavior., Do not call ensure_tools_installed with auto_install=true until the exact tool list and install impact have been reviewed by a human., Authenticated scans should use credential references or approved secret resolvers, not raw passwords, tokens, or session cookies pasted into model context., External tools may create traffic, files, subprocesses, reports, findings databases, caches, and evidence artifacts that require cleanup and retention controls.
Privacy notes
Targets, URLs, IPs, domains, credentials references, findings, proofs of concept, screenshots, payloads, request/response data, reports, detection rules, process lists, and tool output can be sent to the MCP client and model., Findings databases, generated reports, SARIF/JUnit/HTML/PDF exports, logs, subprocess output, tool caches, auth profiles, and cloud-sync settings can contain sensitive vulnerabilities and customer data., Prompts and transcripts can disclose live vulnerabilities, exploitable paths, credentials handling, customer infrastructure, or engagement scope., Keep cloud workspace sync, API tokens, LLM provider keys, and generated reports disabled or controlled unless the engagement explicitly allows them.
Author
0xSteph
Submitted by
oktofeesh1
Claim status
unclaimed
Last verified
2026-06-06
Decision playbook
Review trust signals before you adopt
Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.
Compare context
Selected
0
Current score
63
Baseline
—
Delta
No baseline selected
No major trust-signal divergence detected in the current selection.
Source and provenance checks
Needs review
Confirm ownership and provenance before trusting install instructions.
Source link availableRequired
Open the canonical repository and verify ownership.
Done
Source provenance statusRequired
Marked as source-backed.
Done
Metadata reviewed
No reviewed flag detected in metadata.
Pending
Safety and privacy checks
Complete
Validate risk disclosures before installation or API wiring.
Safety notes presentRequired
Review the listed safety guidance before running commands.
Done
Privacy notes presentRequired
Review data handling notes before connecting accounts or secrets.
Done
Trust level risk gateRequired
Trust level does not block evaluation.
Done
Package and install checks
Needs review
Check package metadata and artifact integrity signals.
Install payload available
Install or copy payload is available for review.
Done
Package verification flag
No package verification flag provided.
Pending
Checksum metadata
No checksum provided for downloaded artifact.
Pending
Compare-driven decision checks
Needs review
Use compare context to validate trade-offs before adoption.
Compare tray has multiple entries
Add at least one more entry to compare trust differences.
6 safety and 4 privacy notes across 4 risk areas. Review closely: credentials & tokens, permissions & scopes.
4 areas
SafetyCredentials & tokensPentest AI is offensive security tooling that performs real network and host operations and can run wrapped scanners, fuzzers, password tools, exploit-adjacent probes, and custom HTTP requests.
SafetyCredentials & tokensUse only on targets where you have written permission, and keep rules of engagement, exclusions, rate limits, credentials, and scope boundaries in the prompt and engagement record.
SafetyPermissions & scopesPrefer intensity=safe, strict_scope=true, and respect_rate_limits=true for real targets; the upstream README notes these safety flags are not all default behavior.
SafetyExecution & processesDo not call ensure_tools_installed with auto_install=true until the exact tool list and install impact have been reviewed by a human.
SafetyCredentials & tokensAuthenticated scans should use credential references or approved secret resolvers, not raw passwords, tokens, or session cookies pasted into model context.
SafetyLocal filesExternal tools may create traffic, files, subprocesses, reports, findings databases, caches, and evidence artifacts that require cleanup and retention controls.
PrivacyCredentials & tokensTargets, URLs, IPs, domains, credentials references, findings, proofs of concept, screenshots, payloads, request/response data, reports, detection rules, process lists, and tool output can be sent to the MCP client and model.
PrivacyLocal filesFindings databases, generated reports, SARIF/JUnit/HTML/PDF exports, logs, subprocess output, tool caches, auth profiles, and cloud-sync settings can contain sensitive vulnerabilities and customer data.
PrivacyCredentials & tokensPrompts and transcripts can disclose live vulnerabilities, exploitable paths, credentials handling, customer infrastructure, or engagement scope.
PrivacyCredentials & tokensKeep cloud workspace sync, API tokens, LLM provider keys, and generated reports disabled or controlled unless the engagement explicitly allows them.
Safety notes
Pentest AI is offensive security tooling that performs real network and host operations and can run wrapped scanners, fuzzers, password tools, exploit-adjacent probes, and custom HTTP requests.
Use only on targets where you have written permission, and keep rules of engagement, exclusions, rate limits, credentials, and scope boundaries in the prompt and engagement record.
Prefer intensity=safe, strict_scope=true, and respect_rate_limits=true for real targets; the upstream README notes these safety flags are not all default behavior.
Do not call ensure_tools_installed with auto_install=true until the exact tool list and install impact have been reviewed by a human.
Authenticated scans should use credential references or approved secret resolvers, not raw passwords, tokens, or session cookies pasted into model context.
External tools may create traffic, files, subprocesses, reports, findings databases, caches, and evidence artifacts that require cleanup and retention controls.
Privacy notes
Targets, URLs, IPs, domains, credentials references, findings, proofs of concept, screenshots, payloads, request/response data, reports, detection rules, process lists, and tool output can be sent to the MCP client and model.
Findings databases, generated reports, SARIF/JUnit/HTML/PDF exports, logs, subprocess output, tool caches, auth profiles, and cloud-sync settings can contain sensitive vulnerabilities and customer data.
Prompts and transcripts can disclose live vulnerabilities, exploitable paths, credentials handling, customer infrastructure, or engagement scope.
Keep cloud workspace sync, API tokens, LLM provider keys, and generated reports disabled or controlled unless the engagement explicitly allows them.
Prerequisites
Python 3.10 or newer and pip, uv, or another supported Python package installer.
Written authorization and explicit scope for every target, host, account, user, API, network, or application being tested.
A dedicated test environment or engagement workspace for findings, tool output, reports, and installed security tools.
Human approval before auto-installing external tools, running active probes, credential tests, authenticated scans, or exploit-chain validation.
Legal, compliance, customer, and rate-limit review before running against production, bug-bounty, third-party, or internet-facing targets.
Pentest AI MCP Server exposes pentest-ai's offensive-security workflows to
Claude and other MCP clients through the ptai mcp command. It can start and
track engagements, list findings, retrieve attack chains, list and run wrapped
security tools, plan and install missing tools, run probes, launch specialist
assessments, inspect running subprocesses, and generate engagement outputs.
The project is intended for authorized security testing. Its MCP path lets an
existing MCP client subscription drive pentest-ai without a separate LLM API key,
while the standalone CLI can use configured LLM providers for non-MCP operation.
These sources were reviewed on 2026-06-06. Prefer the live repository,
README, PyPI metadata, Python package metadata, MCP server implementation,
MCP-side tool install helpers, security-tool registry, security policy, and
license file for current install commands, MCP tools, target guardrails, external
tool behavior, auth handling, and licensing.
Features
Python package ptai with ptai and pentest-ai console commands.
MCP server launched with ptai mcp.
Engagement tools for starting authorized assessments, checking status,
retrieving findings, and inspecting attack chains.
Tool catalog workflows for listing wrapped tools, running individual tools,
planning expected tools, and installing missing tools after approval.
Probe and assessment workflows for web apps, recon, API security, cloud,
Active Directory, credentials, vulnerabilities, privilege escalation, mobile,
wireless, social engineering, LLM red-team, and multi-target campaigns.
Findings database and report-oriented output workflows.
Start with an intentionally vulnerable local target or written-authorized test
environment. For real targets, pass safe engagement options such as
intensity=safe, strict_scope=true, and respect_rate_limits=true when
starting an engagement.
Use Cases
Run a scoped assessment against a deliberately vulnerable lab app.
Ask Claude to list available security tools and identify which are installed.
Plan missing tools for a web, recon, API, cloud, or AD engagement before a
human approves installation.
Launch an authorized web assessment and poll engagement status.
Retrieve findings, attack chains, reports, and process status for review.
Use strict scope and rate-limit settings to keep a bug-bounty or staging test
inside written rules of engagement.
Safety and Privacy
Pentest AI MCP Server is high-risk offensive security tooling. Do not use it
without written authorization, explicit target scope, and clear rules of
engagement. Its tools can generate traffic, run scanners, install external
security tools, authenticate to applications, test credentials, discover
vulnerabilities, validate proofs of concept, and create detailed exploitability
evidence.
Use safe intensity, strict scope, and rate-limit-respecting options for real
targets. Review every auto-install, active probe, credential test, authenticated
scan, and exploit-chain validation step before running it. Keep third-party
tools, subprocesses, findings databases, reports, and evidence artifacts in an
approved workspace with retention and cleanup controls.
Findings, payloads, screenshots, HTTP data, credentials references, report
exports, detection rules, logs, and transcripts can expose serious
vulnerabilities or customer data. Protect LLM provider keys, cloud workspace API
keys, auth profiles, reports, and generated evidence. Disable cloud sync unless
the engagement explicitly allows it.
Duplicate Check
Existing content includes other offensive or security-intelligence MCP entries
such as HexStrike AI and CVE MCP Server. Pentest AI MCP Server is distinct
because it covers 0xSteph/pentest-ai and the ptai MCP interface for
authorized engagements, wrapped external tool execution, tool install planning,
security probes, findings databases, attack chains, process controls, and
reporting workflows. No dedicated Pentest AI, ptai, or 0xSteph/pentest-ai
MCP entry was found in content/mcp.
Show that Pentest AI MCP Server is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/pentest-ai-mcp-server)
How it compares
Pentest AI MCP Server side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
3 trust signals differ across this comparison (Package trust, Source provenance, Submitter).
Offensive-security MCP server from pentest-ai that lets Claude list and run wrapped security tools, plan and install missing tools, launch authorized engagements, run web, recon, API, cloud, AD, credential, vulnerability, mobile, wireless, and LLM-red-team assessments, and retrieve findings, attack chains, reports.
PortSwigger's Burp Suite MCP Server extension connects Burp Suite to MCP clients through an SSE server or packaged stdio proxy for request, Repeater, Intruder, history, scanner, Collaborator, and configuration workflows.
Offensive security MCP framework that connects AI agents to a large toolkit for authorized penetration testing, vulnerability discovery, CTF, OSINT, and security research workflows.
✓Pentest AI is offensive security tooling that performs real network and host operations and can run wrapped scanners, fuzzers, password tools, exploit-adjacent probes, and custom HTTP requests.
Use only on targets where you have written permission, and keep rules of engagement, exclusions, rate limits, credentials, and scope boundaries in the prompt and engagement record.
Prefer intensity=safe, strict_scope=true, and respect_rate_limits=true for real targets; the upstream README notes these safety flags are not all default behavior.
Do not call ensure_tools_installed with auto_install=true until the exact tool list and install impact have been reviewed by a human.
Authenticated scans should use credential references or approved secret resolvers, not raw passwords, tokens, or session cookies pasted into model context.
External tools may create traffic, files, subprocesses, reports, findings databases, caches, and evidence artifacts that require cleanup and retention controls.
✓Treat dependency risk findings as triage input and verify impact before blocking releases or changing package policy.
✓Burp Suite MCP Server can send HTTP/1.1 and HTTP/2 requests, create Repeater tabs, send requests to Intruder, toggle Proxy Intercept, pause or resume Burp's task execution engine, and update the active message editor.
In Burp Suite Professional it can also expose scanner issues and generate or poll Collaborator payloads for out-of-band testing.
The extension includes approval flows for outbound HTTP requests and sensitive data access, but users can configure always-allow targets and disable some approval requirements.
Configuration editing tools can import project-level or user-level Burp options when enabled in the extension, which can change proxy, scanner, target, and other Burp behavior.
Use only on systems and applications where testing is authorized; active requests, Intruder traffic, scanner workflows, and Collaborator payloads can affect third-party services.
Keep the MCP server bound to trusted local interfaces and avoid exposing the SSE server to untrusted networks.
✓HexStrike AI orchestrates offensive security tools and can perform scanning, enumeration, exploitation support, password attacks, OSINT, and vulnerability research.
Use only on systems, domains, networks, binaries, accounts, and datasets where you have explicit authorization.
Agent-driven scans can create high traffic, trigger alarms, lock accounts, alter evidence, or disrupt services if scope and rate limits are not enforced.
Do not allow autonomous exploit generation, credential attacks, or destructive actions against third-party systems without human review and written permission.
Run in an isolated environment with controlled credentials, logging, allowlists, and clear stop conditions.
Privacy notes
✓Targets, URLs, IPs, domains, credentials references, findings, proofs of concept, screenshots, payloads, request/response data, reports, detection rules, process lists, and tool output can be sent to the MCP client and model.
Findings databases, generated reports, SARIF/JUnit/HTML/PDF exports, logs, subprocess output, tool caches, auth profiles, and cloud-sync settings can contain sensitive vulnerabilities and customer data.
Prompts and transcripts can disclose live vulnerabilities, exploitable paths, credentials handling, customer infrastructure, or engagement scope.
Keep cloud workspace sync, API tokens, LLM provider keys, and generated reports disabled or controlled unless the engagement explicitly allows them.
✓Package names, manifests, dependency graphs, repository context, and security findings may be sent through tool calls.
✓Proxy HTTP history, WebSocket history, Organizer items, scanner issues, request and response bodies, headers, cookies, tokens, session identifiers, and Collaborator interaction data may be returned to the MCP client.
The extension can read project-level and user-level Burp configuration; upstream code filters some configuration credentials when configured, but users should still treat exported options as sensitive.
MCP prompts, responses, Burp logs, and client transcripts can retain target URLs, credentials, payloads, vulnerability details, and proprietary application behavior.
The stdio proxy and SSE server bridge Burp traffic into the MCP client process; keep client configs, proxy paths, and Burp project files protected.
✓Targets, scan results, credentials, tokens, exploit notes, screenshots, OSINT findings, and vulnerability reports may be sent to the MCP client and model.
Tool logs can contain customer data, secrets, infrastructure details, private IP ranges, bug bounty findings, and regulated incident information.
Review retention, telemetry, and sharing settings for every AI client and security tool connected to the workflow.
Prerequisites
Python 3.10 or newer and pip, uv, or another supported Python package installer.
Written authorization and explicit scope for every target, host, account, user, API, network, or application being tested.
A dedicated test environment or engagement workspace for findings, tool output, reports, and installed security tools.
Human approval before auto-installing external tools, running active probes, credential tests, authenticated scans, or exploit-chain validation.