No user-submitted related servers found.
Scored across 130 tools
The module prefixes and detailed descriptions help distinguish scanners, but the set contains many overlapping scan_text/scan_file/scan_directory/list_patterns families plus multiple meta-orchestrators (owasp_scan_path, vulnerability_scanner, threat_rules). An agent must read descriptions carefully to choose between secret/prompt-leak/document scanners, OWASP meta-scans and individual auditors.
Names are consistently snake_case and mostly use a predictable module__verb_noun pattern. Minor deviations exist, such as gateway_status, scan_and_report, and baseline_server/check_server, but overall the convention is clear.
130 tools is far beyond a well-scoped set and creates a severe selection burden for an agent. Although many tools map to distinct security domains, the repeated action variants across dozens of modules make the surface extremely heavy.
Coverage is very broad, spanning OWASP MCP categories, secrets, dependencies, TLS/DNS, models, vector stores, compliance, red-teaming, and runtime gateway auditing. Some lifecycle gaps remain, such as baseline deletion/update and gateway policy mutation, but the core scanning and reporting surface is extensive.