FSV
Related Servers
Alternatives to FSV
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to perform authorized security testing and penetration testing operations including SSL/TLS analysis, port scanning, vulnerability scanning, and HTTP security header audits through natural language interactions.1MIT
- FlicenseAqualityDmaintenanceEnables AI assistants to perform defensive security tasks such as vulnerability detection, CVE lookup, phishing/link safety checks, and security report generation via MCP tools.23-
- FlicenseNot gradedqualityDmaintenanceEnables natural-language-driven security testing by orchestrating multiple pen-testing tools through MCP, with automated scan execution and AI-assisted vulnerability summarization.-
- AlicenseNot gradedqualityAmaintenanceEnables AI assistants to drive OWASP ZAP for authorized penetration testing and bug-bounty workflows, including authenticated scans and vulnerability triage through 67 curated safety-gated tools.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to conduct penetration testing and offensive security workflows, including reconnaissance, exploitation, post-exploitation, threat intelligence, malware analysis, forensics, and reporting through MCP tools. It supports session management, C2, evasion, credential attacks, and many specialized security testing capabilities.1MIT
- AlicenseNot gradedqualityDmaintenanceIntegrates OWASP ZAP security testing with AI assistants through MCP, enabling automated vulnerability scanning and AI-powered security analysis during development. Supports multiple scan types including active, passive, and AJAX spider scans with real-time status updates.5MIT
TDQS
Scored across 12 tools
fsv_scan, fsv_quick_check, and fsv_waf_check overlap because quick_check and waf_check are essentially subsets of scan's passive profile. fsv_fixes also overlaps with fsv_get_report's fix-* formats. Descriptions clarify the intended distinctions, but an agent still has to judge which nested tool to use.
All tools use a consistent fsv_ prefix and snake_case, which is predictable. Most follow action_object, but fsv_quick_check, fsv_waf_check, fsv_target_trend, fsv_fixes, fsv_triage, and fsv_scan_stats deviate from a strict verb_noun pattern.
Twelve tools is well within a reasonable range for a vulnerability scanner and covers distinct lifecycle stages: scanning, reporting, scan history, comparison, trend analysis, triage, remediation, stats, module listing, and ownership verification. The set is scoped without obvious bloat.
The surface covers the core scan lifecycle from ownership verification through scanning, reporting, triage, remediation, and historical comparison. Minor gaps exist around scan cancellation/deletion, scheduled scans, and direct finding retrieval outside reports, but agents can work around these.