cve-reference-mcp
Related Servers
Alternatives to cve-reference-mcp
No user-submitted related servers found.
Related Servers
- 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
- FlicenseNot gradedqualityDmaintenanceEnables comprehensive cybersecurity vulnerability assessment by searching GitHub repositories for exploits, querying NIST NVD for CVE details, and accessing CISA's Known Exploited Vulnerabilities catalog. Supports complete vulnerability research workflows from threat intelligence gathering to proof-of-concept discovery.4-
- AlicenseNot gradedqualityDmaintenanceEnables AI assistants to look up CVE details, EPSS exploit probability, and CISA KEV status from free public APIs to prioritize vulnerabilities by real-world risk. Combines these sources into a single enriched, prioritized view using a KEV > EPSS > CVSS rule.MIT
- AlicenseAqualityBmaintenanceEnables LLMs to access realtime CVE intelligence aggregated from NVD, CISA KEV, EPSS, GitHub advisories, PoC discovery, and Metasploit/Nuclei tooling, providing vulnerability details, exploitation signals, and prioritized triage verdicts.1214 npm2MIT
- AlicenseNot gradedqualityDmaintenanceProvides multi-source vulnerability intelligence for AI-powered security operations, combining NVD CVSS, CISA KEV, and EPSS scores without requiring an API key.1MIT
- AlicenseNot gradedqualityFmaintenanceProvides CVE search enriched with EPSS exploit likelihood and CISA KEV status, plus live IP/domain reputation and a real-time threat feed for AI agents.MIT
TDQS
Scored across 2 tools
Both tools accept a CVE ID, but their purposes are clearly differentiated: one returns a list of references from multiple sources, and the other returns a concise summary of key information. While an agent must read the descriptions to choose correctly, there is no overlap in output type.
Both tool names follow a consistent get_cve_<noun> pattern, with 'references' and 'summary' clearly indicating their distinct functions. This is a uniform and predictable naming convention.
With only two tools, the set feels thin for a server dedicated to CVE references. However, it is narrowly scoped and may be adequate for the intended use case of gathering references and summaries for CVE guides.
The server covers two core operations: fetching references and providing summaries. Notable gaps exist, such as fetching detailed CVE metadata or searching by keyword, which an agent might expect from a CVE reference tool. Still, the provided tools cover the primary workflow without dead ends.