Vulnerability Registry MCP Server
Related Servers
Alternatives to Vulnerability Registry 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.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, fetch the latest updated CVEs with CAPEC/CWE/CPE expansions, and check current database information. It provides these capabilities through MCP tools for use in compatible clients.-
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors and products, retrieve vulnerabilities by vendor/product or CVE ID, fetch the latest CVEs with CAPEC/CWE/CPE details, and check database update status via MCP tools.-
- AlicenseAqualityBmaintenanceEnables users to search and retrieve CVE records, CVE history, CPE Dictionary entries, and CPE match criteria through MCP tools, with local caching, pagination, and upstream rate-limit handling.10MIT
- FlicenseNot gradedqualityAmaintenanceEnables querying the CVE-Search API to browse vendors, list products for a vendor, retrieve vulnerabilities for a vendor and product, fetch individual CVE records, get the latest CVEs with CAPEC/CWE/CPE expansions, and inspect current database version information. This gives MCP clients direct, structured access to public vulnerability data.-
- AlicenseAqualityCmaintenanceMCP server that provides tools to search, filter, and retrieve CVE data from the NVD API, including by ID, keyword, severity, and recency.4MIT
TDQS
Scored across 5 tools
Each tool targets a distinct operation: get_vulnerability for a specific CVE, search_vulnerabilities for filtered lists, search_vendors for vendor lookup, get_vendor_overview for aggregate vendor data, and get_vulnerability_statistics for counts. There is no meaningful overlap between any pair of tools.
All tool names follow a consistent verb_noun pattern using lowercase and underscores, with verbs limited to 'get' and 'search'. The naming clearly indicates whether a tool returns a single entity, a list, or statistics.
With 5 tools, the server is well-scoped for a vulnerability registry query interface. Each tool covers a distinct need without redundancy or bloat, fitting comfortably in the ideal 3-15 range.
The tool set provides complete read-only coverage for a vulnerability registry: individual CVE lookup, flexible searching, vendor discovery, vendor-specific aggregation, and vulnerability statistics. No obvious gaps exist for the apparent domain.