Cve Search MCP

What roadwy/cve-search_mcp MCP server does

The roadwy/cve-search_mcp MCP server exposes CVE-Search API data through Model Context Protocol tools. It is intended for MCP clients that need to inspect vulnerability information without building a separate CVE-Search API client. The server belongs in the 🔒 Security category and focuses on discovery, lookup, and database-status queries.

Available operations cover several levels of detail:

• List all vendors known to CVE-Search.
• List products associated with a selected vendor.
• Retrieve vulnerabilities for a vendor and a specific product.
• Fetch the record for one CVE identifier.
• Retrieve the latest 30 CVEs with CAPEC, CWE, and CPE expansions.
• Check which databases are in use and when they were last updated.

The returned data is described as JSON, making the server suitable for agents that need to inspect or pass structured vulnerability records into another workflow.

How it works

The roadwy/cve-search_mcp MCP server acts as an MCP-facing layer over the CVE-Search API. An MCP client starts the local Python entry point, and the exposed tools make API requests for vendor, product, vulnerability, CVE, recent-CVE, or database-status data. The repository identifies CVE-Search as the upstream reference API and links to the CVE-Search project for additional context.

A typical lookup can begin by listing vendors, narrowing the selection to products for one vendor, and then requesting vulnerabilities for that vendor-product pair. When the identifier is already known, the CVE-specific operation avoids that discovery sequence. The recent-CVE operation is intended for retrieving the latest 30 records and their listed CAPEC, CWE, and CPE expansions.

Setup and configuration

The roadwy/cve-search_mcp MCP server requires Python 3.10 or newer and uv. Installation uses the repository source:

1. Clone the GitHub repository.
2. Change into the repository directory.
3. Run uv sync to install dependencies.
4. Add an MCP client entry that runs uv with the repository directory and main.py.

The example configuration uses --directory, followed by the local checkout path, then run and main.py. Replace the placeholder path with the directory where the repository was cloned. The README demonstrates this setup with VS Code using Cline or Roo Code.

Tools and capabilities

The roadwy/cve-search_mcp MCP server provides read-oriented CVE-Search operations rather than database mutation features. Its capabilities include vendor enumeration, vendor-specific product enumeration, vendor-and-product vulnerability searches, direct CVE-ID retrieval, recent-CVE retrieval, and inspection of database coverage and update timing.

These capabilities support workflows such as identifying products maintained by a vendor, examining known vulnerabilities for a product, enriching an investigation with a specific CVE record, or checking whether the upstream data has been updated recently.

Limitations and notes

It also does not document write operations, remediation guidance, scanning, or automated severity assessment. The server should therefore be evaluated as a query interface for CVE-Search data, not as a complete vulnerability-management system.

Client support in the README explicitly mentions Cline and Roo Code, with VS Code shown as the host configuration context.