pentest-mcp
Related Servers
Alternatives to pentest-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceRecords your terminal sessions per command (PTY + OSC 133) into local SQLite, so AI agents can search, retrieve, and diff what commands actually printed. Secret redaction is applied by default to everything served over MCP.47MIT
- AlicenseNot gradedqualityAmaintenanceEnables professional penetration testers to run reconnaissance, exploitation, brute-force, traffic-capture, and reporting workflows through MCP tools over STDIO/HTTP/SSE transports with bearer/OIDC authentication and Dockerized host tooling.298 npmGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables authorized penetration testers to run reconnaissance, enumeration, vulnerability scanning, brute-force checks, traffic capture, and exploitation workflows via MCP tools, with STDIO/HTTP/SSE transport support. It also manages engagement records and generates client reports.298 npmGPL 3.0
- AlicenseNot gradedqualityAmaintenanceEnables professional penetration testers to run and coordinate reconnaissance, scanning, brute-force, exploitation, traffic capture, and reporting tools through MCP, with stdio/HTTP/SSE transports and bearer/OIDC authentication.298 npmGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables agents to query a dated, provenance-backed history distilled from any text stream, turning raw records into observations, bi-temporal facets, and narratives over MCP.10MIT
- AlicenseNot gradedqualityAmaintenanceEnables professional penetration testers to run reconnaissance, exploitation, brute-force, and credential-cracking tooling (nmap, gobuster, nikto, John the Ripper, hashcat, subfinder, httpx, ffuf, nuclei, hydra, sqlmap, tcpdump) through MCP clients over stdio or HTTP. It also captures engagement records and generates client reports with scope-of-work handling and bearer/OIDC authentication.298 npmGPL 3.0
TDQS
Scored across 15 tools
Each tool targets a distinct resource and action: listing vs getting vs updating findings/tasks/entities, searching, tracing provenance, recording observations. No two tools appear to do the same thing, and overlaps like list_findings vs get_finding are cleanly separated by collection vs singleton semantics.
All tool names follow a consistent lowercase_verb_noun pattern (get_, list_, search, record_, update_). Verbs are uniform and actions are clear from names alone, with no camelCase or mixed conventions.
15 tools is well within the ideal range for a specialized MCP server. Each tool serves a distinct purpose in the penetration-testing workflow (observation, analysis, status management, provenance), with no redundancy or bloat.
The surface covers the full investigation lifecycle: capture review, entity management, finding workflow (candidate/confirm/reject), task tracking, provenance tracing, and operator note-taking. Minor gaps exist (no explicit engagement creation/deletion or direct entity editing), but these are addressable via record_observation and do not create dead ends.