No user-submitted related servers found.
Scored across 8 tools
Each tool has a clear primary purpose: scanning project/snippet/live, listing/getting findings, verifying fixes, checking dependencies, and generating reports. Minor overlap exists between scan_project and check_dependencies (and verify_fixes re-scans), but descriptions are specific enough to avoid serious misselection.
All tool names follow a consistent verb_noun pattern in lowercase snake_case: scan_project, list_findings, get_finding, verify_fixes, scan_snippet, check_dependencies, probe_live, generate_report. There are no mixed conventions or vague verbs.
Eight tools is well-scoped for a security scanning server. Each tool covers a distinct stage of the workflow: scanning, inspecting findings, verifying fixes, live probing, dependency checks, and reporting, with no redundant or unnecessary additions.
Core coverage is solid: scanning (project, snippet, live, dependencies), finding inspection (list, get), verification, and reporting. Minor gaps include the inability to dismiss/mark findings as false positives or view scan history, but these are not critical to the primary launch-readiness workflow.
