현대적인 전송/인증 지원과 확장된 정찰 도구를 갖춘 전문 침투 테스트 MCP 서버입니다.

0.9.0에서 바뀐 점

• MCP SDK를 [[T0]로 업그레이드했습니다.
• 최신 릴리스([@modelcontextprotocol/inspector@^0.20.0)와 번들 런처를 유지함
• 스트리밍 가능한 HTTP가 이제 주요 네트워크 전송 수단입니다 (MCP_TRANSPORT=http)
• SSE는 여전히 더 이상 지원되지 않는 호환성 모드로만 제공됩니다
• OIDC JWKS와 인트로스펙션 지원을 통한 베어러 토큰 인증 추가
• 일류 도구 추가: subfinderEnum, httpxProbe, ffufScan, nucleiScan, trafficCapture, hydraBruteforce, privEscAudit, extractionSweep
• 신고 관리 도구 추가: listEngagementRecords, getEngagementRecord
• 안전한 템플릿 폴백과 함께 MCP 추출(scopeMode=ask)을 사용하는 보고서를 위한 SoW 캡처 플로우 추가
• 웹 프로빙이 httpx-toolkit(선호) 또는 검증된 ProjectDiscovery httpx를 사용하여 Python httpx CLI 충돌을 피하도록 강화된 명령 해상도
• 통합 번들 MCP 검사기 발사기 (pentest-mcp inspector)
• 런타임 기준은 현재 22.7.5+Node.js

Pentest MCP

Pentest MCP is a TypeScript MCP server for authorized security assessments. It gives a human researcher or a tool-using assessment agent one scoped interface for discovery, validation, capture, credential checks, local audit, evidence retrieval, and report preparation. Each active tool call is tied to an engagement and a durable record. The server checks the declared targets and time window; the researcher verifies findings before publication.

October 2026 workflow

1. Create an engagement from signed authorization and rules of engagement, then save the assessment plan. The operator chooses a stable engagementId.
2. A researcher or fresh Codex process in the managed assessment container connects to the Pentest MCP server. It sees the complete catalog, while the plan’s exact allowedToolNames list permits only selected calls. Active tools also pass the engagement target and time gate.
3. Review recordId values and correlated scope decisions with listEngagementRecords and getEngagementRecord. Records persist across restarts. Import external research with recordResearchActivity; the import does not replace MCP tool use.
4. Draft a report from the complete evidence ledger, inspect candidate findings against source records, and publish only analyst-verified findings. Retrieve Markdown or JSON later with getClientReport.

The declared-target check is an operational guardrail, not a complete network boundary. DNS changes, redirects, Nmap scripts, Nuclei templates, and other third-party tool behavior can create secondary traffic. Review tool configuration and keep network controls aligned with the engagement’s rules.

Agentic assessment uses the MCP tools