vuln_lookup_cveLABSCO SUMMARY
Severity alone does not tell you what to patch first.
A high CVSS score on something nobody is exploiting is a different problem from a mid score sitting in the KEV catalog with a remediation deadline attached. Because vuln_lookup_cve returns all four signals from one call, triage becomes a single question rather than four tabs. vuln_kev_due_soon is the one that matters if you are on a federal remediation clock.
What it is
A vulnerability intelligence server that joins four government and community sources into a single answer: NIST NVD 2.0 for CVE details and CVSS scores, the CISA Known Exploited Vulnerabilities catalog, FIRST.org EPSS for exploitation probability, and MITRE ATT&CK for adversary techniques.
What you get
vuln_lookup_cvetakes acveIdand returns NVD details, the CVSS score, KEV exploitation status, the EPSS probability and mapped ATT&CK techniques in one callvuln_searchsearches NVD bykeyword,severity(LOW, MEDIUM, HIGH, CRITICAL), publication date range andlimit(1-50, default 20), withhasKevto restrict to actively exploited entriesvuln_kev_latestlists what CISA added recently —daysdefaults to 7vuln_kev_due_soonlists KEV entries whose remediation deadline falls withindays, default 14vuln_epss_topreturns the CVEs most likely to be exploited next, above athresholdthat defaults to 0.7vuln_trendingreturns newly published high or critical CVEs from the lastdays, default 3vuln_by_vendorsearches byvendorand optionalproduct, cross-referencing KEV to flag what is actively exploited
Requirements
Node.js 18 or later; you clone the gov-mcp-servers repository and build this server yourself. No credentials are needed — NVD, CISA KEV, FIRST.org EPSS and MITRE ATT&CK are all public — though an optional NVD_API_KEY raises the NVD rate limit from 5 to 50 requests per 30 seconds. Note the update cadences, because they set how fresh an answer can be: NVD is continuous, KEV and EPSS are daily, ATT&CK is quarterly.
Setup effort
Build from source — git clone https://github.com/martc03/gov-mcp-servers.git
USE CASES
Deciding how urgent a CVE really is
One lookup returns severity, whether it is being exploited, how likely exploitation is, and which techniques map to it.
Ordering a patch queue
Pull the highest-probability CVEs and cross-check which are already in the exploited catalog.
Staying ahead of a remediation deadline
List KEV entries whose deadline lands inside the next fortnight.
Assessing a vendor you depend on
Search their products and see which of their vulnerabilities are actively exploited.
Watching for something newly weaponised
Check what CISA added this week and what critical CVEs were published in the last few days.
7 tools
Listed in project docs. Your client may show a different list.
vuln_searchvuln_kev_latestvuln_kev_due_soonvuln_epss_topvuln_trendingvuln_by_vendorBEFORE YOU INSTALL
What to know first
Tools you get
7 tools named in the project's documentation.
Requires
Node.js 18+
Where it runs
Both documented clients run the server on your machine.
INSTALLATION
Connect your client
Server setup
git clone https://github.com/martc03/gov-mcp-servers.git
cd gov-mcp-servers/servers/cybersecurity-vuln-mcp
npm install && npm run build
node dist/stdio.jsMCP Clients
Claude Desktop, Claude Code
{
"mcpServers": {
"cybersecurity": {
"command": "node",
"args": [
"<YOUR_PATH_TO_SERVERS>/cybersecurity-vuln-mcp/dist/stdio.js"
],
"env": {
"NVD_API_KEY": "<YOUR_NVD_API_KEY>"
}
}
}
}