pentest-ai (0xSteph/pentest-ai) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 52 tools. No publisher has claimed this listing.

C
Emerging
74/100
25 days ago

pentest-ai

Open-source AI pentester that proves every finding. Machine oracles re-run each exploit; verified bugs ship a proof capsule you can replay yourself.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

Code Verified⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

0xSteph

Source: PulseMCP · also listed on Glama, github_topic

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: GITHUB_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 7 credentials: PENTEST_AI_API_KEY, OPENAI_API_KEY, ANTHROPIC_API_KEY, PTAI_OAST_TOKEN, PENTEST_AI_API_TOKEN, GITHUB_TOKEN, VAULT_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configPENTEST_DB_PATH
configPENTEST_EVIDENCE_DIR
configPENTEST_AI_DB_PATH
configPENTEST_AI_RUNTIME_DIR
configPTAI_FORCE_EXIT_DISABLE
configPTAI_FORCE_EXIT_SECS
configPENTEST_AI_LLM_PROVIDERexport =ollama # Ollama (default localhost:11434)
🔐 secretPENTEST_AI_API_KEY
🔐 secretOPENAI_API_KEYexport =sk-... # OpenAI
🔐 secretANTHROPIC_API_KEYexport =sk-ant-... # Claude (best results)
configPTAI_UPSTREAM_PROXY
configPTAI_NO_OAST
configPTAI_OAST_SERVER
🔐 secretPTAI_OAST_TOKEN
configPTAI_AUTO_AUTH
🔐 secretPENTEST_AI_API_TOKEN
configPENTEST_AI_MCP_CONFIG
configPTAI_SKIP_TOOLS
configCLEANAPP_PORT
configPTAI_VERSION_OVERRIDE
configPTAI_SKIP_VERSION_CHECK
configPENTESTAI_API_BASE
configGITHUB_OUTPUT
configGITHUB_REPOSITORY
🔐 secretGITHUB_TOKEN
configGITHUB_REF
configNO_COLOR
configOPENAI_BASE_URL
configPENTEST_WEBHOOK_URL
configPENTEST_WEBHOOK_TYPE
configPTAI_NON_INTERACTIVEIn non-interactive contexts (=1 or no TTY) ptai uses what's on PATH and logs (rather than prompts) for anything missing.
configPENTEST_AI_CONFIG_DIR
configPENTEST_AI_AUP_ACCEPTEDFirst-run prompts you to confirm AUP acceptance and persists the choice to ~/.pentest-ai/aup-consent.txt. Set =1 in CI to bypass the prompt non-interactively.
configPENTEST_AI_CACHE
configPTAI_STRICT_EVIDENCE
configPTAI_DB_PATH
configXDG_DATA_HOME
configPTAI_INSTALL_PREFS
configPTAI_NO_OAST_SEVERITY_CALIBRATION
configPENTEST_AI_TELEMETRY
configPENTEST_AI_TELEMETRY_ENDPOINT
configPENTEST_AI_TRACING
configOTEL_SERVICE_NAME
configOTEL_TRACES_EXPORTER
configOTEL_EXPORTER_OTLP_ENDPOINT
configJUICE_SHOP_DIR
configZAP_DIR
🔐 secretVAULT_TOKEN
configVAULT_ADDR
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

52/52 tools missing one or more hints — start_engagement (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_engagement_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_findings (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +49 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 2 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Score](https://m8ven.ai/badge/mcp/0xsteph/pentest-ai)](https://m8ven.ai/mcp/0xsteph/pentest-ai)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 96c3bf7f3aa53b86431d4b89999e8ca8115fc3b0
code hash: c485f27ff91bbd71b8ce14e38dbf69a5d4e640bd805285ba74319b3bbea31dce
verified: 8/16/2026, 1:07:00 PM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client