No user-submitted related servers found.
Scored across 10 tools
Most tools have distinct purposes, but there is meaningful overlap between run_pentest_pipeline and run_wstg_test because the pipeline can target a single WSTG objective while run_wstg_test also runs individual tests. run_surface_recon also partially overlaps with the pipeline's recon scan profiles. Descriptions help clarify when to use each, but an agent could still hesitate between them.
All tool names use snake_case and generally follow a verb_noun pattern such as manage_pentest_program, run_wstg_test, get_pentest_dashboard, and export_bugbounty_report. The few compound names like inspect_finding_or_evidence remain readable and consistent with the set.
The set contains 10 tools, which is well within the appropriate range for a focused pentest workflow. Each tool corresponds to a meaningful stage or operation: lifecycle management, scope, scanning, catalog lookup, evidence inspection, triage, and reporting.
The surface covers the core pentest lifecycle from program and scope management through scanning, triage, inspection, and reporting. Minor gaps remain around explicitly listing or managing findings beyond inspecting by ID, such as listing all findings or updating finding status, but these are workable given the dashboard and report tools.