Skip to main content

Grype MCP Server

PyPI version Python Support License

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 install grype-mcp

Or using pipx:

pipx install grype-mcp

Or using pip:

pip install grype-mcp

MCP 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: uvx
  • Args: ["grype-mcp"]

Start using Grype's vulnerability scanning capabilities!

🛠️ Available Tools

The Grype MCP server provides these tools for AI assistants:

System Management

  • find_grype - Check if Grype is installed and get version info
  • update_grype - Install or update Grype to the latest version
  • get_db_info - Get vulnerability database status and version info
  • update_db - Update the vulnerability database

Vulnerability Scanning

  • scan_dir - Scan project directories for vulnerabilities
  • scan_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 CPE
  • get_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_grype tool)
  • 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@version
    • Python: pkg:pypi/package@version
    • Go: pkg:golang/package@version
    • Java: pkg:maven/group/artifact@version
    • And many more ecosystems

🏗️ Architecture

The MCP server acts as a bridge between AI assistants and Grype:

AI Assistant ↔ MCP Server ↔ Grype CLI ↔ Vulnerability Database
  • Zero 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:

📄 License

Licensed under the Apache License, Version 2.0. See LICENSE for details.

🔗 Related Projects

📞 Support


Made with ❤️ by the Anchore team for the AI-assisted development community

Release files for grype-mcp 0.4.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for grype-mcp 0.4.0
File Size Uploaded
grype_mcp-0.4.0.tar.gz 15.2 kB Details

Built distribution (wheel)

Table of built distributions (wheels) for grype-mcp 0.4.0
File Interpreter ABI Platform
grype_mcp-0.4.0-py3-none-any.whl Python 3 none any Details

Total release size: 31.0 kB

Release files / grype_mcp-0.4.0.tar.gz

Download URL grype_mcp-0.4.0.tar.gz
Size 15.2 kB
Tags Source
SHA-256 checksum
How to use checksums
796bd68f579c7e3471930025c47e0d37d02885faafa042d9ed5894e0ab652da4
BLAKE2b-256 checksum
How to use checksums
ba08feb07f012c4c12776b795ec9f47d1fda83c697bedad9c8bcbbf6a95754ec
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 29, 2025.

Transparency log

Release files / grype_mcp-0.4.0-py3-none-any.whl

Download URL grype_mcp-0.4.0-py3-none-any.whl
Size 15.8 kB
Tags Python 3
SHA-256 checksum
How to use checksums
45bc16ac2a006ac090381f3326256dcd6c860c6173fffc4749e1200ce5525e6c
BLAKE2b-256 checksum
How to use checksums
6fd9dfcb45c1820b660c13a40bb722d3b6ef27ac0f66626d9728f08bb32e8b77
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
Yes
Uploaded via twine/6.1.0 CPython/3.12.9

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

PyPI Publish Attestation

PyPI verified that this artifact, at this checksum, originated from the publisher listed below.

Signed by GitHub Actions, verified by PyPI on Aug 29, 2025.

Transparency log

Release history Release notifications | RSS feed

This release

0.4.0 This release

2 release files

0.2.0

2 release files

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page