Overview
What is grype mcp server?
Grype mcp server is a wrapper that exposes Anchore Grype’s vulnerability scanning capabilities through the Model Context Protocol (MCP). It allows developers to scan container images and file systems for known vulnerabilities directly from MCP‑compatible IDEs such as Cursor or Claude Desktop.
How to use grype mcp server?
Install the Grype CLI as a prerequisite. Then add the MCP server configuration to your MCP client (e.g., in claude_desktop_config.json or Cursor’s MCP settings) with command: "node" and args: ["${GRYPE_MCP_SERVER_PATH}/index.ts"]. Launch the IDE and invoke the scanner through its MCP interface.
Key features of grype mcp server
- Integrates Grype’s vulnerability scanner into MCP‑compatible IDEs
- Scans container images and file systems for known vulnerabilities
- No need to leave the IDE to use Grype
- Shows vulnerable packages and their locations
- Uses the full Grype vulnerability database
Use cases of grype mcp server
- Scan a Docker image for vulnerabilities during development
- Check a project’s file system dependencies for known CVEs
- Quickly locate vulnerable packages in a container or directory
FAQ from grype mcp server
What does grype mcp server do?
It provides an MCP interface to Anchore Grype, so developers can scan container images and file systems for vulnerabilities without leaving their IDE.
Does grype mcp server require Grype to be installed?
Yes. Grype must be installed separately as a dependency.
Which IDEs are supported?
The server works with any MCP‑compatible IDE, such as Cursor or Claude Desktop.
How do I configure the server?
Use the standard MCP server configuration with command: "node" and args: ["${GRYPE_MCP_SERVER_PATH}/index.ts"] in the mcpServers section of your client settings.
What kind of scans does it support?
It supports the same scan types as Grype: container images and file systems.
