Skip to main content
Glama
friendlygeorge

Security Scanner MCP Server

by friendlygeorge
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to Security Scanner MCP Server

No user-submitted related servers found.

    Related Servers

    • SAST MCP Server

      Skyrxin
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to scan code for security vulnerabilities using multiple static analysis tools, with support for filtering, deduplication, and CI/CD integration.
      27
      2
      MIT
    • Grype MCP Server by anchore

      Grype MCP Serverofficial

      anchore
      A
      license
      A
      quality
      F
      maintenance
      Enables AI assistants to perform vulnerability scanning using Grype, supporting scans of directories, container images, and packages via the Model Context Protocol.
      9
      9
      Apache 2.0

    • Zfuzz

      Zfuzz-dev
      A
      license
      Not graded
      quality
      A
      maintenance
      Real security scanners for AI coding agents — SAST (441 rules), secret detection (419+ patterns), dependency CVEs (OSV.dev), MCP/skill vetting, MITRE ATT&CK. Open-source, Rust, free
      18 npm
      Apache 2.0

    • Security Intel MCP

      datakoot
      A
      license
      Not graded
      quality
      B
      maintenance
      Vulnerability intelligence for AI agents that enables CVE lookup, package vulnerability checks, and dependency auditing without API keys.
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A3.8/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes: scanning different targets (image, filesystem, repository, SBOM, PURL) and using different engines (Trivy, Grype, cross-validation). However, `scan_image` and `vulnerability_report` both scan Docker images with overlapping vulnerability output, and `db_status`/`update_db` are closely related, causing minor ambiguity.

    Naming Consistency4/5

    The majority of tools follow a `verb_noun` pattern (e.g., `scan_image`, `generate_sbom`), with consistent use of the `scan_` prefix for scanning tools. However, `vulnerability_report` is a noun phrase, `cross_validate` is a verb without an object, and `db_status` is noun_noun, breaking the pattern slightly.

    Tool Count5/5

    15 tools is well within the ideal 3-15 range, covering scanning, SBOM generation, database management, and reporting. Each tool serves a distinct purpose without being too numerous or too sparse for a security scanner server.

    Completeness4/5

    The tool set covers core security scanning operations for Docker images, filesystems, repositories, IaC configs, and SBOMs, with multi-engine support and cross-validation. Minor gaps include lack of running container scanning or direct CVE lookups beyond PURL, but the surface is largely complete for the domain.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources