Grype MCP Server
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| find_grypeB | Find the grype binary and check if it's installed. Returns information about grype installation status. |
| update_grypeA | Install or update the grype binary to the latest version. Downloads and installs grype using the official Anchore installer. |
| scan_dirC | Scan a directory for vulnerabilities using Grype. Args: path: Path to the directory to scan include_dev: Include development dependencies |
| scan_purlA | Scan a specific package using PURL (Package URL) format. Args: package_url: Package URL in PURL format (e.g., pkg:npm/lodash@4.17.20) |
| scan_imageA | Scan a container image for vulnerabilities. Args: image: Container image name/tag (e.g., nginx:latest, ubuntu:20.04) |
| search_vulnsB | Search the Grype database for vulnerability information. Args: query: Search query (CVE ID, package name, etc.) search_type: Type of search: vuln, package, or cpe |
| get_vuln_detailsC | Get detailed information about a specific vulnerability. Args: cve_id: CVE identifier (e.g., CVE-2021-44228) |
| get_db_infoA | Get information about the Grype vulnerability database. |
| update_dbB | Update the Grype vulnerability database. Args: force: Force update even if database is recent |
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 9 tools
Each tool has a clearly distinct purpose: installation check, DB info, vulnerability details, three scan types (directory, image, PURL), search, and two update operations. No overlap.
All tool names follow a consistent verb_noun pattern in snake_case (e.g., find_grype, scan_dir, update_db), making them predictable and easy to use.
9 tools is well-scoped for a vulnerability scanning server: covering installation, scanning, searching, and updates without unnecessary bloat or missing essentials.
Covers core workflows: installation check, DB info, scanning (directory, image, PURL), vulnerability details, search, and updates. Minor gaps like returning raw scan results or listing installed packages, but not critical.