Skip to main content
Glama
ScanRook MCP Server

ScanRook MCP Server

Related Servers

Alternatives to ScanRook MCP Server

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to scan directories, container images, and SBOMs for vulnerabilities, look up individual CVEs, and refresh the local vulnerability database. Findings come back prioritized with concrete upgrade targets rather than raw scanner output.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      F
      maintenance
      Provides security scanning capabilities through Snyk CLI tools and REST API, enabling AI assistants to test projects for vulnerabilities, retrieve security issues, and manage Snyk projects with comprehensive SAST, container, and infrastructure as code scanning.
      2
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to vet open-source repositories and dependencies by running OpenSSF Scorecard, Trivy, and Syft checks for repository health, vulnerabilities, licenses, and SBOMs, with background jobs and status polling.
      4
      Apache 2.0
    • 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
      23 PyPI
      9
      Apache 2.0
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI coding assistants to run pre-publish security and code-quality scans across 17 categories, generate a 0–100 security score and Markdown report, quickly check critical vulnerabilities, and receive fix/refactor suggestions by finding ID.
      3
      MIT

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: scanning images, checking status, listing scans, retrieving findings, comparing scans, analyzing licenses, checking packages, and searching CVEs. No overlap exists.

    Naming Consistency3/5

    Most tools use verb_noun pattern (analyze_licenses, check_package, compare_scans, get_findings, list_scans, scan_image, search_cve), but scan_status differs (noun_verb) and is inconsistent with the rest.

    Tool Count5/5

    8 tools is appropriate for a vulnerability scanning server, covering the core lifecycle from scanning to results, comparisons, and CVE lookups. Each tool earns its place.

    Completeness4/5

    Covers scanning, results, comparison, license analysis, and CVE lookup. Minor gap: no tool to trigger a scan by non-OCI artifacts (e.g., filesystem) or manage scan configurations.

    Maintenance

    ActivityInactive
    ResponsivenessNo recent community issues