Grype MCP Server
OfficialClick on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Grype MCP Server Scan my project directory for vulnerabilities"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Grype MCP Server
Anchore MCP server for Grype vulnerability scanner
Integrate Grype vulnerability scanning directly into AI-assisted development workflows through the Model Context Protocol (MCP).
🚀 Quick Start
Installation
Install using uvx (recommended):
uvx grype-mcpOr using pipx:
pipx install grype-mcpOr using pip:
pip install grype-mcpMCP Client Setup
Claude Desktop
Add to your Claude Desktop configuration:
{
"mcpServers": {
"grype": {
"command": "uvx",
"args": ["grype-mcp"]
}
}
}Other MCP Clients
For other MCP-compatible clients, add the server using:
Command:
uvxArgs:
["grype-mcp"]
Start using Grype's vulnerability scanning capabilities!
Related MCP server: Security Scanner MCP Server
🛠️ Available Tools
The Grype MCP server provides these tools for AI assistants:
System Management
find_grype- Check if Grype is installed and get version infoupdate_grype- Install or update Grype to the latest versionget_db_info- Get vulnerability database status and version infoupdate_db- Update the vulnerability database
Vulnerability Scanning
scan_dir- Scan project directories for vulnerabilitiesscan_purl- Scan specific packages using PURL format (e.g.,pkg:npm/lodash@4.17.20)scan_image- Scan container images for vulnerabilities
Vulnerability Research
search_vulns- Search the vulnerability database by CVE, package name, or CPEget_vuln_details- Get detailed information about specific CVEs
💡 Example Usage
Once configured, you can ask:
"Check if Grype is installed and up to date"
"Scan my project directory for vulnerabilities"
"Is pkg:npm/lodash@4.17.20 vulnerable?"
"Scan the nginx:latest Docker image"
"Search for Log4j vulnerabilities"
"Get details about CVE-2021-44228"
🔧 Requirements
Python 3.10+
Grype (can be installed via the
update_grypetool)Docker (optional, for container image scanning)
The MCP server can help install Grype if it's not already available using the update_grype tool.
📋 Supported Scanning Targets
Directories - Scan entire projects with all their dependencies
Container Images - Docker images from any registry
Package URLs - Individual packages in PURL format
npm:
pkg:npm/package@versionPython:
pkg:pypi/package@versionGo:
pkg:golang/package@versionJava:
pkg:maven/group/artifact@versionAnd many more ecosystems
🏗️ Architecture
The MCP server acts as a bridge between AI assistants and Grype:
AI Assistant ↔ MCP Server ↔ Grype CLI ↔ Vulnerability DatabaseZero modifications to Grype required
Structured JSON responses optimized for AI consumption
Comprehensive error handling with helpful messages
Automatic tool management for easy setup
🤝 Contributing
We welcome contributions! Please see:
CONTRIBUTING.md - Contribution guidelines
DEVELOPING.md - Development setup
CODE_OF_CONDUCT.md - Community standards
📄 License
Licensed under the Apache License, Version 2.0. See LICENSE for details.
🔗 Related Projects
Grype - Vulnerability scanner for container images and filesystems
Syft - SBOM generation tool
Model Context Protocol - Open protocol for AI assistant integrations
Anchore Enterprise - Commercial SBOM-powered security platform
📞 Support
GitHub Issues - Bug reports and feature requests
Anchore Community Discourse - Community support and discussions
Documentation - Full documentation
Made with ❤️ by the Anchore team for the AI-assisted development community
Available Tools
9 toolsfind_grypeB
Find the grype binary and check if it's installed.
Returns information about grype installation status.
Inputs: no named parameters. Returns: result
get_db_infoA
Get information about the Grype vulnerability database.
Inputs: no named parameters. Returns: result
get_vuln_detailsC
Get detailed information about a specific vulnerability.
Args: cve_id: CVE identifier (e.g., CVE-2021-44228)
Inputs: cve_id (required). Returns: result
scan_dirC
Scan a directory for vulnerabilities using Grype.
Args: path: Path to the directory to scan include_dev: Include development dependencies
Inputs: path (required), include_dev. Returns: result
scan_imageA
Scan a container image for vulnerabilities.
Args: image: Container image name/tag (e.g., nginx:latest, ubuntu:20.04)
Inputs: image (required). Returns: result
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)
Inputs: package_url (required). Returns: result
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
Inputs: query (required), search_type. Returns: result
update_dbB
Update the Grype vulnerability database.
Args: force: Force update even if database is recent
Inputs: force. Returns: result
update_grypeA
Install or update the grype binary to the latest version.
Downloads and installs grype using the official Anchore installer.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Related MCP Connectors
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Generate SBOMs, scan vulnerabilities, and analyze dependencies from local projects or Git repos.
Scan packages and lockfiles (npm, PyPI, Go, Maven, Cargo, NuGet) for vulnerabilities and malware.
Related MCP Servers
- FlicenseAqualityNot gradedmaintenancePerforms vulnerability scans using Trivy to generate Software Bill of Materials (SBOM) in CycloneDX format. It enables automated security auditing and dependency tracking through the Model Context Protocol.1-
- AlicenseAqualityFmaintenanceMulti-engine container and system vulnerability scanning for AI agents. Wraps Trivy and Grype with cross-engine validation, SBOM generation, and IaC misconfiguration scanning.1514 npmMIT

Aribot MCPofficial
AlicenseNot gradedqualityDmaintenanceEnables security work such as threat modeling, scanning, compliance checks, and remediation through AI assistants using the Model Context Protocol.MIT- AlicenseNot gradedqualityDmaintenanceEnables AI agents to drive OWASP ZAP vulnerability scanning via the Model Context Protocol.4MIT