Skip to main content
Glama
Sign In
deenesjakoruzh
cve-search_mcp

cve-search_mcp

by roadwy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

CVE-Search MCP Server

CVE-SEARCH_MCP

A Model Context Protocol (MCP) server for querying the CVE-Search API. This server provides comprehensive access to CVE-Search, browse vendor and product、get CVE per CVE-ID、get the last updated CVEs.

Related MCP server: CIRCL CVE SEARCH MCP Server

Requirements

  • python 3.10+

  • uv

  • Cline、Roo Code etc

Tools

  • To get a JSON with all the vendors

  • To get a JSON with all the products associated to a vendor

  • To get a JSON with all the vulnerabilities per vendor and a specific product

  • To get a JSON of a specific CVE ID

  • To get a JSON of the last 30 CVEs including CAPEC, CWE and CPE expansions

  • To get more information about the current databases in use and when it was updated

Quick Start

  1. Git clone this repository

git clone https://github.com/roadwy/cve-search_mcp.git

  1. Install the dependencies

cd cve-search_mcp
uv sync

3.Add to your mcp client(vscode with cline/roo code) configuration file, modify the "YOU_CVE_SEARCH_MCP_DIR_PATH" as you self dir.

    "cve-search_mcp": {
      "command": "uv",
      "args": [
        "--directory",
        "YOU_CVE_SEARCH_MCP_DIR_PATH",
        "run",
        "main.py"
      ],
      "disabled": false,
      "autoApprove": []
    }

Reference

https://github.com/cve-search/cve-search

Available Tools

6 tools
vul_cve_searchC

To get a JSON of a specific CVE ID

Inputs: cve_id (required).

vul_db_update_statusC

To get more information about the current databases in use and when it was updated

Inputs: no named parameters.

vul_last_cvesC
To get a JSON of the last <number> (5 by default) CVEs including CAPEC, CWE and CPE expansions

Inputs: number.

vul_vendor_product_cveC

To get a JSON with all the vulnerabilities per vendor and a specific product

Inputs: product (required), vendor (required).

vul_vendor_productsC

To get a JSON with all the products associated to a vendor

Inputs: vendor (required).

vul_vendorsC

To get a JSON with all the vendors

Inputs: no named parameters.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.3/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose targeting specific CVE-related queries: searching by ID, checking database status, retrieving recent CVEs, finding vulnerabilities by vendor/product, listing products per vendor, and listing all vendors. There is no overlap in functionality, making tool selection unambiguous.

    Naming Consistency5/5

    All tools follow a consistent 'vul_' prefix and snake_case naming pattern (e.g., vul_cve_search, vul_vendor_products), with clear and descriptive names that indicate the resource and action. This uniformity enhances readability and predictability.

    Tool Count5/5

    With 6 tools, the server is well-scoped for CVE search and vulnerability management, covering key operations like lookup, updates, recent entries, and vendor/product queries. Each tool serves a specific, non-redundant purpose, making the count appropriate for the domain.

    Completeness4/5

    The tool set provides comprehensive coverage for querying CVE data, including searches by ID, vendor, product, and recent entries, plus database status. A minor gap is the lack of tools for filtering or sorting beyond basic queries, but core workflows are fully supported without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessLimited data

    Resources

    Related MCP Connectors

    Related MCP Servers

    Appeared in Searches