Skip to main content
Glama

Related Servers

Alternatives to FSV

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables 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.
      1
      MIT
    • F
      license
      A
      quality
      D
      maintenance
      Enables 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
      -
    • A
      license
      C
      quality
      B
      maintenance
      Enables MCP-capable AI agents to run authorization-gated reconnaissance, vulnerability scanning, web application testing, exploitation, CTF tasks, reporting, and integrations with tools such as Burp, ZAP, and DefectDojo.
      83
      185 PyPI
      2
      MIT
    • F
      license
      Not graded
      quality
      D
      maintenance
      Enables natural-language-driven security testing by orchestrating multiple pen-testing tools through MCP, with automated scan execution and AI-assisted vulnerability summarization.
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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.
      MIT

    TDQS

    A3.9/5.0

    Scored across 12 tools

    Disambiguation4/5

    Most tools have clearly distinct roles: scanning, listing, comparing, triage, reporting, verification, and trend analysis are well separated. There is some overlap between fsv_quick_check and a passive fsv_scan, between fsv_waf_check and WAF detection included elsewhere, and between fsv_fixes and fsv_get_report's fix-* formats, but the descriptions clarify intended usage.

    Naming Consistency4/5

    All tools use a consistent fsv_ prefix and snake_case, with mostly verb_noun patterns such as fsv_list_scans, fsv_compare_scans, and fsv_get_report. A few are noun-only or less action-oriented (fsv_triage, fsv_fixes, fsv_target_trend), but the overall convention remains predictable.

    Tool Count5/5

    At 12 tools, the set is well-scoped for a vulnerability scanner: core scanning, reporting, history, triage, remediation, and verification each have a clear place. No tool appears redundant enough to inflate the count.

    Completeness5/5

    The surface covers the full scanning lifecycle: quick and full scans, scan listing and comparison, trend reporting, triage persistence, remediation snippets, stats, module discovery, WAF detection, ownership verification, and multiple report formats. No obvious operational gap stands out for the stated domain.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues