ScanRook MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SCANROOK_API_KEY | Yes | Your ScanRook API key | |
| SCANROOK_API_URL | No | ScanRook API base URL | https://scanrook.io |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_imageA | Scan a Docker/OCI container image for vulnerabilities. Returns a job ID to track progress. |
| scan_statusA | Check the status and results of a vulnerability scan. |
| get_findingsB | Get detailed vulnerability findings for a completed scan. Returns CVE IDs, severity, affected packages, and descriptions. |
| search_cveB | Look up details about a specific CVE vulnerability. |
| list_scansA | List recent vulnerability scans for your organization. |
| analyze_licensesB | Analyze open source license compliance for a completed scan. Identifies copyleft, restrictive, and unknown licenses. |
| compare_scansB | Compare vulnerability findings between two scans to see what was added, removed, or unchanged. |
| check_packageA | Check if a specific package version has known vulnerabilities using the OSV database. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.