CVE-info-mcp
Related Servers
Alternatives to CVE-info-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityDmaintenanceProvides conversational access to a local CVE (Common Vulnerabilities and Exposures) database, enabling natural language queries to search vulnerabilities, retrieve detailed CVE information, and view security statistics.3MIT
- AlicenseAqualityDmaintenanceEnables users to retrieve and display CVE vulnerability information from the National Vulnerability Database (NVD) with support for keyword search and detailed lookup.283 npm4MIT
- FlicenseNot gradedqualityDmaintenanceEnables CVE vulnerability lookup and search using the National Vulnerability Database (NVD), allowing users to retrieve detailed information about specific CVEs and search for vulnerabilities by keyword.-
- AlicenseNot gradedqualityBmaintenanceEnables querying CVE vulnerability data from the NIST National Vulnerability Database, including CVE lookup, product/version search via CPE filters, CVSS severity scores, and recent high-severity disclosures.394 npmMIT
- AlicenseNot gradedqualityDmaintenanceProvides CVE lookup, search, and exploit intelligence from public vulnerability sources (NVD, CISA KEV, EPSS) for AI agents to produce remediation guidance without consuming LLM tokens for data fetching.1MIT
- AlicenseAqualityBmaintenanceEnables AI agents to search, correlate, and monitor real-time vulnerability intelligence from NVD, CISA KEV, EPSS, and MITRE ATT&CK, including CVE details, critical CVE tracking, known exploited vulnerabilities, and exploitation probability scores.52MIT
TDQS
Scored across 5 tools
The set contains two overlapping search tools (`search` vs `search_cves`) and two overlapping detail tools (`fetch` vs `get_cve`). Descriptions hint at differences in pagination and section selection, but an agent could easily choose the wrong one for a simple CVE lookup.
Names mix bare verbs (`search`, `fetch`) with verb_noun patterns (`search_cves`, `get_cve`, `get_status`). The same action is labeled both `fetch` and `get_cve`, making the convention inconsistent rather than predictable.
Five tools is a reasonable count for a CVE lookup server, but the redundancy between the two search tools and the two retrieval tools means not every tool clearly earns its place. Consolidating the pairs would yield a cleaner three-tool surface.
The server covers the core read-only CVE lifecycle: search, filtered pagination, detailed retrieval by ID, section selection, and index status. Minor gaps exist around related metadata such as CWE or product browsing, but the main workflows are supported.