Skip to main content
Glama
devinshawntripp

ScanRook MCP Server

by devinshawntripp
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Remote

Related Servers

Alternatives to ScanRook MCP Server

No user-submitted related servers found.

    Related Servers

    • Snyk MCP REST

      axelspringer
      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
    • 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
      13 PyPI
      9
      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.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 issues

    Resources