CVE MCP Server
Related Servers
Alternatives to CVE MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityCmaintenanceProvides Claude with live access to multiple vulnerability databases (NVD, OSV, GitHub Advisories, Snyk) for querying CVEs, package vulnerabilities, and remediation guidance.-
- AlicenseAqualityCmaintenanceEnables Claude to fetch live package versions across npm, PyPI, crates.io, and Go modules, flag deprecations and known vulnerabilities, and audit dependency manifests with minimum safe upgrade versions.2MIT
- AlicenseAqualityBmaintenanceEnables any MCP client (Claude Code, Claude Desktop, Codex, or a custom agent) to fetch the latest CVEs at query time from live sources — NVD, CVE List V5, GitHub Advisory Database, CISA KEV and FIRST EPSS — without a separate API key. Exposes search, filtering (severity, RCE, PoC, KEV, keyword, CPE), per-CVE detail and risk-scored patch prioritization as JSON tools, so answers are grounded in live data rather than model memory.61MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to pull live NVD details, FIRST EPSS probabilities and CISA KEV status for CVEs, then rank a set of them into prioritized tiers with a transparent 0-100 risk score and a one-line rationale each. Also supports keyword searching and graceful degradation when a source is unavailable, so triage conversations can move from hundreds of scanner findings to a defensible patch order.MIT
- AlicenseNot gradedqualityBmaintenanceEnables Claude to query and correlate security intelligence from numerous vulnerability, network, and threat APIs for CVE triage, risk scoring, and exploit assessment. It fans out across sources to produce composite risk scores, patch recommendations, and prioritized remediation guidance through natural language.Apache 2.0
- AlicenseAqualityBmaintenanceEnables an AI agent to parse project lockfiles (npm, pnpm, Yarn, uv, Poetry, requirements.txt, Cargo, go.sum) and query OSV.dev to find known vulnerabilities in locked versions, transitive dependencies included, then produce minimal upgrade plans with breaking-change flags, cleanliness re-checks, and the parent dependency responsible. It also lists outdated packages and explains individual advisories, all read-only with no API key required.5MIT
TDQS
Scored across 4 tools
Each tool targets a distinct granularity and input: scan_lockfile handles whole lockfiles, check_package handles a single package/version, get_cve retrieves by CVE ID, and search_cves finds CVEs by keyword. The boundary between scan_lockfile and check_package is clearly explained by scope, preventing likely misselection.
All names follow a consistent snake_case verb_noun pattern: scan_lockfile, get_cve, search_cves, check_package. The singular/plural variation between get_cve and search_cves reflects the object semantics rather than a naming inconsistency.
Four tools are well-scoped for a focused CVE/vulnerability server, with each tool covering a distinct workflow: project scanning, individual package checking, CVE lookup, and keyword search. No tool feels redundant or trivial.
The surface covers the core lifecycle: scanning dependencies, checking a specific package, fetching a CVE, and searching recent CVEs. Minor gaps exist, such as no direct GHSA/advisory lookup by ID or bulk CVE listing, but agents can work around these using the provided tools.