cve-mcp
Related Servers
Alternatives to cve-mcp
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityBmaintenanceUnified vulnerability search MCP server for penetration testing agents, integrating 5 data sources (NVD, OSV, EPSS, CISA KEV, Exploit-DB+GitHub) and 10 MCP tools for CVE query, keyword search, batch query, EPSS scoring, KEV checking, exploit search, and comprehensive assessment with Chinese output.2-
- AlicenseAqualityCmaintenanceMCP server for the NIST National Vulnerability Database — lets AI assistants search CVEs by keyword, severity, CPE, CWE, KEV status, and date range via natural language.2GPL 3.0
- AlicenseBqualityCmaintenanceThis MCP server transforms Claude into a comprehensive security analyst by providing access to 27 security tools across 21 APIs for vulnerability intelligence. It enables users to query multiple sources like NVD, EPSS, CISA KEV, and threat intelligence platforms in parallel to get correlated security insights and risk assessments for CVEs.281,579Apache 2.0
- AlicenseAqualityAmaintenanceAn MCP server for vulnerability management that provides tools for automated severity and CWE classification using NLP models. It enables AI agents to query the Vulnerability Lookup API for detailed CVE information and search for security vulnerabilities across various sources.1642AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceMCP server for querying live CISA KEV, EPSS, and enriched vulnerability feeds with full provenance. Enables natural-language access to auditable security-intelligence data from Claude Desktop and other MCP clients.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to search, retrieve, and analyze vulnerability data from the NIST National Vulnerability Database through a comprehensive Model Context Protocol server.88MIT
TDQS
Scored across 41 tools
Each tool targets a distinct data source or specific operation (e.g., cve_enrich vs. nvd_get, cve_compare vs. cve_prioritize). Descriptions clearly differentiate purposes, even for similar-looking tools.
Most tools follow a consistent 'source_action' pattern with underscores (e.g., nvd_get, epss_score). Minor deviations like 'cve_by_product' and 'cve_to_attack' break the pattern but are still readable.
41 tools is high but justified by the breadth of data sources (NVD, EPSS, KEV, etc.) and operations (get, search, compare, prioritize). Slightly over the typical sweet spot but still well-scoped.
Covers nearly every aspect of CVE handling: retrieval from multiple sources, enrichment, comparison, prioritization, reporting, exploit checks, CWE mapping, and trending. No obvious gaps for a vulnerability intelligence server.