Skip to main content
Glama
12211725-star

hospital-vuln-scanner-mcp

Related Servers

Alternatives to hospital-vuln-scanner-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for AI security analysis, enabling vulnerability scanning, sensitive information leak detection, and GitHub code leak monitoring via 48 tools.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for web application security scanning with Nikto, Nuclei, Wapiti, and shcheck integration.
      8
      BSD 3-Clause
    • A
      license
      A
      quality
      D
      maintenance
      Unified MCP server integrating NIST and OWASP security frameworks with live vulnerability data, enabling security searches, compliance mapping, threat modeling, and checklist generation.
      41
      14
      MIT
    • A
      license
      A
      quality
      F
      maintenance
      A comprehensive security testing MCP server providing 51 tools for penetration testing, network forensics, memory analysis, and vulnerability assessment. It enables automated security audits and technical investigations across web applications, cloud environments, and network captures.
      51
      36 npm
      23
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      Scans MCP servers and AI tools for security risks, providing 4-dimensional scoring and badges, with optional guardrail MCP for auto-protection.
      2
      MIT
    • A
      license
      Not graded
      quality
      A
      maintenance
      This MCP server enables security auditing for MCP configurations and AI agents, including prompt injection testing, data flow tracing, and security policy generation.
      30 npm
      MIT

    TDQS

    A3.7/5.0

    Scored across 14 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose (e.g., start_scan vs. get_scan_status, list_vulnerabilities vs. get_vulnerability). There is no ambiguity between tools.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun snake_case pattern (e.g., cancel_scan, discover_network, generate_report). No mixing of conventions.

    Tool Count5/5

    14 tools are well-scoped for a vulnerability scanner covering scanning, vulnerability management, network discovery, and reporting. No unnecessary tools.

    Completeness4/5

    Covers the core lifecycle (scan, report, vuln management) well. Minor gap: absence of a tool to retrieve report content (only list and generate). Overall, very thorough.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues