cybersecurity-vuln-mcp
Related Servers
Alternatives to cybersecurity-vuln-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceUnifies NVD, EPSS, CISA KEV, GitHub Advisory, and OSV into a single MCP server, enabling AI agents to query vulnerability intelligence conversationally with 23 tools for incident response, prioritization, dependency audits, and threat monitoring.41292 npm30MIT
- AlicenseAqualityCmaintenanceConnects AI agents to structured vulnerability intelligence from NVD, EPSS, KEV, and OSV, enabling deterministic, policy-scored incident triage, CVE lookup, vulnerability search, and package scanning through auditable MCP tools.61MIT
- 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.21GPL 3.0
- AlicenseAqualityCmaintenanceEnables AI agents to search, correlate, and monitor real-time vulnerability intelligence from NVD, CISA KEV, EPSS, and MITRE ATT&CK, including CVE details, critical CVE tracking, known exploited vulnerabilities, and exploitation probability scores.52MIT
- 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
- FlicenseNot gradedqualityDmaintenanceUnified 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-
TDQS
Scored across 7 tools
Tools are mostly distinct, with slight overlap between vuln_kev_due_soon and vuln_kev_latest (both KEV-focused but different filters) and between vuln_trending and vuln_epss_top (different criteria for prioritizing CVEs). Descriptions clarify differences.
All tool names follow the pattern vuln_<descriptive_name>, using underscores and consistent noun/verb structure. No mixing of conventions.
7 tools cover the core vulnerability intelligence domain without being excessive. Each tool serves a clear purpose, and the count is well-scoped.
The surface covers search, lookup, trending, exploitation probability, and KEV monitoring comprehensively. Minor gaps exist, such as no tool for patch or fix version information, but overall the set is complete for its informational purpose.