Skip to main content
Glama
Grype MCP Server

Grype MCP Server

Official
by anchore

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 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!

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 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.

📞 Support


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

Available Tools

9 tools
find_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

    A3.7/5.0

    Scored across 9 tools

    Disambiguation5/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    9 tools is well-scoped for a vulnerability scanning server: covering installation, scanning, searching, and updates without unnecessary bloat or missing essentials.

    Completeness4/5

    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

    Related MCP Servers