CVE MCP Server
Related Servers
Alternatives to CVE MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables security analysts and risk managers to query a legacy CVE registry via natural language, providing tools for searching vulnerabilities, retrieving details, and obtaining statistics.-
- AlicenseBqualityBmaintenanceEnables local, read-only search and retrieval of publicly available CVE vulnerability information, returning official advisories, AI explanations, research notes, and source URLs.5MIT
- 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.371 npmMIT
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to retrieve vendors, products, product-specific vulnerabilities, specific CVE IDs, recently updated CVEs with CAPEC/CWE/CPE expansions, and database update information. It supports natural-language access to CVE data through MCP clients.-
- AlicenseAqualityDmaintenanceEnables users to retrieve and display CVE vulnerability information from the National Vulnerability Database (NVD) with support for keyword search and detailed lookup.299 npm4MIT
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors and their products, retrieve vulnerabilities per vendor/product, look up specific CVE IDs, fetch the latest 30 CVEs with CAPEC, CWE and CPE expansions, and check database metadata. This gives MCP clients conversational access to public vulnerability data.-
TDQS
Scored across 3 tools
Each tool has a clearly distinct purpose: get_cve_details retrieves specific CVE data, get_statistics provides database metrics, and search_cves finds CVEs by keyword. There is no overlap in functionality, making tool selection straightforward for an agent.
All tool names follow a consistent verb_noun pattern with snake_case: get_cve_details, get_statistics, and search_cves. The naming is predictable and readable, with no deviations in style.
With only 3 tools, the server feels thin for a CVE database server, as it lacks operations like filtering by severity, date, or CVSS score, or updating/listing capabilities. However, the core functions are present, making it borderline appropriate.
The server covers basic retrieval (get details, search) and statistics, but there are notable gaps: no create, update, or delete operations for managing CVEs, and no advanced querying options. This limits functionality but allows for core lookup tasks.