ScanRook MCP Server
Related Servers
Alternatives to ScanRook MCP Server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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.1Apache 2.0
- AlicenseNot gradedqualityFmaintenanceProvides 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.2MIT
- AlicenseAqualityBmaintenanceEnables 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.4Apache 2.0

Grype MCP Serverofficial
AlicenseAqualityFmaintenanceEnables AI assistants to perform vulnerability scanning using Grype, supporting scans of directories, container images, and packages via the Model Context Protocol.923 PyPI9Apache 2.0- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to VulnCheck vulnerability intelligence for querying CVEs, exploits, advisories, and vulnerable packages via natural language.14MIT
- AlicenseAqualityCmaintenanceEnables 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.3MIT
TDQS
Scored across 8 tools
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.
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.
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.
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.