Skip to main content
Glama
cve-mcp-server

cve-mcp-server

cve-mcp-server

Realtime CVE intelligence over the Model Context Protocol. Gives an LLM one place to look up a vulnerability and get details, exploitation signals, and public proof-of-concepts aggregated from five authoritative sources:

Source

What it provides

NIST NVD (API v2.0)

Description, CVSS v2/v3.1/v4 scores + vectors, CWE weaknesses, affected-product CPEs, references

CISA KEV

Confirmed active-exploitation status, remediation due dates, ransomware-use flag

FIRST.org EPSS

Probability a CVE is exploited in the next 30 days (+ percentile)

GitHub Security Advisories

Package-level impact: ecosystem, vulnerable version ranges, first patched version

nomi-sec PoC-in-GitHub + Exploit-DB

Public proof-of-concept repos (ranked by stars) and exploit references, with optional repo-content retrieval

Metasploit + Nuclei

Packaged, ready-to-run tooling: Metasploit modules (Rapid7, with reliability rank) and Nuclei templates (ProjectDiscovery) referencing the CVE

Tools

Tool

Purpose

cve_triage

Prioritization verdict fusing CVSS + EPSS + KEV + PoC into ACT NOW → LOW.

cve_batch_triage

Triage up to 25 CVEs in one call, returned ranked by priority (turn a scan/findings list into a fix-first queue).

cve_watchlist

Vendor/product digest: recently published CVEs + that vendor's CISA KEV entries in one call.

cve_get_details

Full enriched detail for one CVE (NVD + KEV + EPSS, with triage banner).

cve_search

Search NVD by keyword, CPE, severity, KEV status, date range.

cve_recent

Recently published CVEs (realtime monitoring, up to 120-day look-back).

cve_get_pocs

Discover public PoC / exploit references for a CVE.

cve_fetch_poc_code

Fetch a PoC repo's file listing + README.

cve_get_exploit_tooling

Packaged Metasploit modules + Nuclei templates for a CVE (with run strings).

cve_get_kev

CISA KEV single lookup or catalog browse.

cve_get_epss

EPSS scores for one or many CVEs.

cve_get_advisories

GitHub Security Advisories for a CVE.

All tools are read-only and support response_format: "markdown" (default) or "json".

Related MCP server: Cybersecurity Threat Intelligence MCP

Setup

Requires Node.js 18+.

npm install
npm run build

Optional environment variables

All are optional but recommended — they raise rate limits and coverage:

  • NVD_API_KEY — request one here (NVD throttles hard without it).

  • GITHUB_TOKEN — any GitHub PAT; raises the GitHub API limit for advisories and PoC fetching.

  • TRANSPORT — stdio (default) or http.

  • PORT — HTTP port when TRANSPORT=http (default 3000, bound to 127.0.0.1).

Connecting a client

Claude Code

claude mcp add cve --env NVD_API_KEY=xxx --env GITHUB_TOKEN=ghp_xxx -- node /home/k4p/cve-mcp-server/dist/index.js

Claude Desktop (claude_desktop_config.json)

{
  "mcpServers": {
    "cve": {
      "command": "node",
      "args": ["/home/k4p/cve-mcp-server/dist/index.js"],
      "env": {
        "NVD_API_KEY": "your-nvd-key",
        "GITHUB_TOKEN": "ghp_your_token"
      }
    }
  }
}

Example prompts

  • "Tell me everything about Log4Shell, including whether it's actively exploited."

  • "What critical CVEs were published this week that are in the CISA KEV catalog?"

  • "Find public PoCs for CVE-2024-3400 and show me what's in the top repo."

  • "Is there a Metasploit module or Nuclei template for EternalBlue?"

  • "Rank CVE-2021-44228, CVE-2023-23397, and CVE-2024-3400 by EPSS exploitation likelihood."

  • "Here are 12 CVEs from last night's scan — triage them and tell me what to patch first."

  • "What's new for Fortinet this month, and which of theirs are actively exploited?"

  • "Which Maven packages does CVE-2021-44228 affect and in what version was it fixed?"

Safety note

PoC and exploit tools surface already-public security research artifacts and are intended for authorized defensive testing, detection engineering, and vulnerability triage. cve_fetch_poc_code retrieves repository contents (file listing + README, size-bounded) and cve_get_exploit_tooling links to public Metasploit/Nuclei source; use them only against targets you are authorized to test.

Triage scoring

cve_triage (and the banner on cve_get_details) turns four signals into one verdict:

Priority

Trigger

🔴 ACT NOW

In CISA KEV (confirmed exploited), or composite score ≥ 85

🟠 HIGH

Score ≥ 70

🟡 ELEVATED

Score ≥ 50

🔵 MODERATE

Score ≥ 30

⚪ LOW

Score < 30

Composite score (0-100): CVSS contributes up to 50, EPSS up to 40, and exploit availability up to 15. Availability is a gradient (strongest signal wins, not additive): a weaponized Metasploit exploit module → 15, other packaged tooling (auxiliary module / Nuclei template) → 12, a public PoC → 10, none → 0. KEV membership hard-pins to 100. Each verdict comes with a plain-English rationale — including an explicit "severe on paper but low real-world signal → deprioritize" note when CVSS is high but EPSS/KEV/PoC/tooling are all cold.

Resilience

  • Retries with backoff on 429/502/503/504 and network blips (honors Retry-After) — so NVD's strict unauthenticated rate limit doesn't fail a triage mid-run.

  • CVE-detail lookups cached 15 min in-process (the same CVE is queried repeatedly across cve_get_details / cve_triage / cve_get_pocs).

Evaluations

evals/ holds a 10-question suite (cve-mcp-evals.xml, mcp-builder format) plus a ground-truth checker that asserts each answer is still retrievable from the live sources:

npm run verify:evals

See evals/README.md for details. Answers are chosen to be stable over time (CVSS/CWE, KEV dates, GHSA patched versions, classic Metasploit paths).

Notes

  • The CISA KEV catalog is cached in-process for one hour to avoid re-downloading the full feed on every call.

  • The Metasploit metadata (~11 MB) and Nuclei CVE index (~2 MB) feeds are fetched once and cached in-process for six hours, then indexed by CVE for instant lookups.

  • NVD caps date-range queries at 120 days; cve_recent clamps to that.

  • Responses are truncated at 25,000 characters; use pagination or json format for more.

Available Tools

12 tools
cve_batch_triageBatch triage CVEs (ranked)A
Read-onlyIdempotent

Triage a list of CVEs in a single call and get them back ranked by priority — turn a scan or findings list into an ordered "fix this first" queue without one tool call per CVE.

Each CVE is scored exactly as cve_triage does (CVSS + EPSS + CISA KEV + optional PoC/tooling), then results are sorted highest-priority first. EPSS is fetched for the whole batch in one request; unknown IDs are reported separately rather than failing the call.

Args:

  • cve_ids (string[]): 1-25 CVE identifiers.

  • check_pocs (boolean, default false): Add public-PoC availability (one extra lookup per CVE).

  • check_tooling (boolean, default true): Add Metasploit/Nuclei tooling (cached feeds; cheap across a batch).

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { requested, triaged, not_found[], results[] } where each result is { cve_id, priority, score, signals, description } sorted by score descending.

Examples:

  • "Rank these scan findings by what to patch first" -> cve_ids=[...].

  • "Triage this list but skip the PoC lookups" -> check_pocs=false.

Errors:

  • Malformed IDs are rejected up front; unresolvable-but-valid IDs come back in not_found[].

Inputs: cve_ids (required), check_pocs, check_tooling, response_format.

cve_fetch_poc_codeFetch PoC repository contentsA
Read-onlyIdempotent

Fetch the actual proof-of-concept material from a GitHub repository: its top-level file listing plus the decoded README (bounded in size).

Use after cve_get_pocs to inspect a specific PoC. Intended for authorized security research and defensive validation. Set GITHUB_TOKEN to raise rate limits and access more repos.

Args:

  • repo (string): 'owner/repo' or a full github.com URL.

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { fullName, htmlUrl, files[], readme, readmeTruncated }.

Examples:

Errors:

  • "GitHub rate limit exceeded (429)" — set GITHUB_TOKEN.

  • "GitHub has no record for that identifier (404)" — repo not found or private.

Inputs: repo (required), response_format.

cve_get_advisoriesGet GitHub Security AdvisoriesA
Read-onlyIdempotent

Retrieve GitHub Security Advisories (GHSA) that reference a CVE — the best source for package-level impact (ecosystem, affected version ranges, first patched version).

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): array of { ghsaId, summary, severity, cveId, htmlUrl, publishedAt, vulnerabilities: [ { ecosystem, packageName, vulnerableVersionRange, firstPatchedVersion } ] }.

Examples:

  • "Which npm/Maven packages does CVE-2021-44228 affect and when was it fixed?" -> cve_id="CVE-2021-44228".

Notes:

  • Returns an empty list when no advisory references the CVE. Set GITHUB_TOKEN to raise rate limits.

Inputs: cve_id (required), response_format.

cve_get_detailsGet CVE detailsA
Read-onlyIdempotent

Retrieve complete, authoritative details for a single CVE from the NIST NVD, enriched with real-time exploitation signals.

Combines: NVD description, CVSS v2/v3.1/v4 base scores + vectors, CWE weakness types, affected-product CPE strings, and reference URLs — plus (by default) CISA KEV actively-exploited status and the EPSS exploitation-probability score.

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • include_kev (boolean): Add CISA KEV status (default: true).

  • include_epss (boolean): Add EPSS score (default: true).

  • response_format ('markdown' | 'json'): Output format (default: 'markdown').

Returns (json): { id, published, lastModified, vulnStatus, descriptions, cvss[], cwes[], references[], cpe[], kev, epss }.

Examples:

  • "Tell me everything about Log4Shell" -> cve_id="CVE-2021-44228".

  • "Is CVE-2023-23397 being exploited?" -> include_kev=true, include_epss=true.

Errors:

  • "Invalid CVE ID ..." if the ID is malformed.

  • "No NVD record found for " if the CVE does not exist in NVD.

Inputs: cve_id (required), include_kev, include_epss, response_format.

cve_get_epssGet EPSS exploitation scoresA
Read-onlyIdempotent

Retrieve EPSS (Exploit Prediction Scoring System, by FIRST.org) scores for one or more CVEs.

EPSS estimates the probability (0-100%) that a CVE will be exploited in the wild within the next 30 days, plus a percentile ranking across all scored CVEs. Useful for prioritizing patching beyond raw CVSS severity.

Args:

  • cve_ids (string[]): 1-100 CVE identifiers.

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { count, scores: [ { cve, epss, percentile, date } ] } (epss/percentile as fractions 0-1).

Examples:

  • "EPSS for CVE-2021-44228" -> cve_ids=["CVE-2021-44228"].

  • "Rank these three by exploitation likelihood" -> cve_ids=[...].

Inputs: cve_ids (required), response_format.

cve_get_exploit_toolingGet exploit tooling (Metasploit + Nuclei)A
Read-onlyIdempotent

Find packaged, ready-to-run exploit and scan tooling for a CVE: Metasploit Framework modules (Rapid7) and Nuclei templates (ProjectDiscovery).

This is distinct from cve_get_pocs (raw proof-of-concept repos). For an operator, packaged tooling is usually more actionable: a Metasploit exploit module is point-and-shoot (use <module>), and a Nuclei template gives repeatable, at-scale detection (nuclei -id <cve> -u <target>). Each module/template comes with its reliability/severity, disclosure date, msfconsole/nuclei run string, and GitHub source link.

Intended for authorized penetration testing, detection engineering, and vulnerability triage.

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { cveId, metasploit: [ { fullname, name, type, rank, rankLabel, disclosureDate, hasCheck, sourceUrl } ], nuclei: [ { id, name, severity, cvssScore, filePath, sourceUrl } ] }.

Metasploit rank: 0 Manual, 100 Low, 200 Average, 300 Normal, 400 Good, 500 Great, 600 Excellent. Type "exploit" is weaponized; "auxiliary" is typically a scanner/check.

Examples:

  • "Is there a Metasploit module for Log4Shell?" -> cve_id="CVE-2021-44228".

  • "Can I scan for CVE-2024-3400 with Nuclei?" -> cve_id="CVE-2024-3400".

Notes:

  • Returns empty lists (not an error) when no packaged tooling references the CVE.

Inputs: cve_id (required), response_format.

cve_get_kevCISA KEV lookup / catalogA
Read-onlyIdempotent

Query the CISA Known Exploited Vulnerabilities (KEV) catalog — the authoritative list of CVEs confirmed to be actively exploited in the wild.

Two modes:

  • Single lookup: pass cve_id to check whether a specific CVE is KEV-listed (with remediation due date and ransomware-use flag).

  • Catalog list: omit cve_id to browse the catalog, newest additions first, with optional vendor / ransomware filters.

Args:

  • cve_id (string, optional): Single-CVE lookup.

  • vendor (string, optional): Vendor/product substring filter (list mode).

  • ransomware_only (boolean, default false): Only known-ransomware entries (list mode).

  • limit (1-100, default 25), offset (default 0): Pagination (list mode).

  • response_format ('markdown'|'json', default 'markdown').

Returns (single): a KEV entry object, or a "not listed" message. Returns (list, json): { catalogVersion, dateReleased, total, count, startIndex, entries[] }.

Examples:

  • "Is CVE-2024-3400 known-exploited?" -> cve_id="CVE-2024-3400".

  • "Recent ransomware-linked KEV entries" -> ransomware_only=true.

Inputs: limit, cve_id, offset, vendor, +2 more.

cve_get_pocsDiscover CVE proof-of-conceptsA
Read-onlyIdempotent

Discover public proof-of-concept (PoC) and exploit references for a CVE.

Aggregates the nomi-sec "PoC-in-GitHub" index (public GitHub repos tagged to the CVE, ranked by stars) and, by default, Exploit-DB / exploit-tagged references from the NVD record. Returns links and metadata only — use cve_fetch_poc_code to retrieve a specific repo's contents.

Intended for authorized defensive testing, detection engineering, and vulnerability triage.

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • include_nvd_exploits (boolean): Include NVD exploit references (default: true).

  • max_results (1-100, default 30): Cap on references returned.

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { cve_id, count, pocs: [ { source, name, url, description, stars, createdAt, updatedAt } ] }.

Examples:

  • "Find PoCs for Log4Shell" -> cve_id="CVE-2021-44228".

  • "Any exploits for CVE-2024-3400?" -> include_nvd_exploits=true.

Notes:

  • Returns an empty list (not an error) when no public PoCs are indexed.

Inputs: cve_id (required), max_results, response_format, include_nvd_exploits.

cve_recentList recent CVEsA
Read-onlyIdempotent

List CVEs published within a recent look-back window — for real-time monitoring of newly disclosed vulnerabilities.

Args:

  • days (1-120, default 7): How far back to look (NVD caps ranges at 120 days).

  • severity ('LOW'|'MEDIUM'|'HIGH'|'CRITICAL'): Optional severity filter.

  • kev_only (boolean, default false): Only CVEs in the CISA KEV catalog.

  • limit (1-50, default 20), offset (default 0): Pagination.

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { total, count, offset, has_more, next_offset, results[] }, newest first by publish date.

Examples:

  • "What critical CVEs dropped this week?" -> days=7, severity="CRITICAL".

  • "New known-exploited vulns in the last month" -> days=30, kev_only=true.

Inputs: days, limit, offset, kev_only, +2 more.

cve_triageTriage a CVE (prioritization verdict)A
Read-onlyIdempotent

Produce a single prioritization verdict for a CVE by fusing every exploitation signal: CVSS severity, EPSS 30-day exploitation probability, CISA KEV (confirmed in-the-wild use / ransomware), and public proof-of-concept availability.

Answers "should I drop everything for this, or can it wait?" — the judgment call an analyst otherwise makes by hand across four tools.

Priority levels: ACT NOW (KEV / score ≥85) > HIGH (≥70) > ELEVATED (≥50) > MODERATE (≥30) > LOW. KEV membership always pins to ACT NOW. Score (0-100): CVSS up to 50, EPSS up to 40, and exploit availability up to 15 (weaponized Metasploit exploit module 15 > other packaged tooling 12 > public PoC 10).

Args:

  • cve_id (string): CVE identifier, e.g. "CVE-2021-44228".

  • check_pocs (boolean): Include PoC availability (default: true; one extra lookup).

  • check_tooling (boolean): Include Metasploit/Nuclei tooling (default: true; one extra lookup).

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { cve_id, priority, score, rationale[], signals{ cvssScore, cvssSeverity, epss, epssPercentile, kevListed, kevRansomware, kevDueDate, pocCount, msfModuleCount, nucleiTemplateCount, weaponized }, tooling{ metasploit, nuclei }, description }.

Examples:

  • "Should we patch CVE-2024-3400 this weekend?" -> cve_id="CVE-2024-3400".

  • "Triage this from the scan, skip the PoC check" -> check_pocs=false.

Errors:

  • "No NVD record found for " if the CVE is unknown/unpublished.

Inputs: cve_id (required), check_pocs, check_tooling, response_format.

cve_watchlistVendor/product CVE watchlistA
Read-onlyIdempotent

Monitor a vendor or product for new and known-exploited vulnerabilities in one call — a digest that fuses NVD recent-publications with the CISA KEV catalog.

Answers "what's new and what's on fire for right now?" without running cve_recent, cve_search, and cve_get_kev separately and cross-referencing by hand.

Args:

  • vendor (string): Vendor/product to watch, e.g. "fortinet", "apache struts". Matched against NVD descriptions and KEV vendor/product fields.

  • days (1-120, default 30): Look-back window for newly published CVEs.

  • severity ('LOW'|'MEDIUM'|'HIGH'|'CRITICAL'): Optional minimum severity for the recent list.

  • include_kev (boolean, default true): Also list this vendor's KEV entries (newest first; items added within the window are flagged 🆕).

  • limit (1-50, default 25): Max recently-published CVEs.

  • response_format ('markdown'|'json', default 'markdown').

Returns (json): { vendor, window_days, since, recent: { total, count, results[] }, kev: { total, entries[] }, kev_in_window }. Each recent result carries a kev_listed flag.

Examples:

  • "What's new for Fortinet this month, and what's actively exploited?" -> vendor="fortinet".

  • "Critical Ivanti CVEs in the last two weeks" -> vendor="ivanti", days=14, severity="CRITICAL".

Errors:

  • "NVD rejected the request (400)" if filters are invalid.

Inputs: vendor (required), days, limit, severity, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    TDQS

    A4.4/5.0

    Scored across 12 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: details, search, recent, PoCs, exploit tooling, KEV, EPSS, advisories, triage, batch triage, and vendor watchlist are all separated by explicit intent. Even potentially overlapping tools like cve_get_pocs vs cve_get_exploit_tooling are carefully delineated.

    Naming Consistency4/5

    All tools share the cve_ prefix and mostly follow a verb_noun pattern. Minor deviations exist: cve_recent and cve_watchlist are noun/adjective-style rather than verb-led, and cve_batch_triage modifies cve_triage rather than using a uniform verb. Overall still highly predictable.

    Tool Count5/5

    12 tools is well-scoped for a CVE intelligence server. Each tool covers a distinct aspect of vulnerability lookup, enrichment, and prioritization without redundancy, and the count feels appropriate for the domain.

    Completeness5/5

    The surface covers the full CVE workflow: discovery (search, recent, watchlist), detail retrieval (get_details, advisories), enrichment (KEV, EPSS, PoCs, tooling), and action (triage, batch triage). No significant gap in the stated purpose of providing comprehensive CVE intelligence and prioritization.

    Maintenance

    ActivitySlowing
    ResponsivenessNo recent community issues

    Related MCP Connectors

    Related MCP Servers

    • A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to search and analyze vulnerabilities and exploits from multiple intelligence sources, including NVD, CISA KEV, ExploitDB, Metasploit, and more, with tools for CVE research, exploit analysis, and report generation.
      17
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides 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.
      1
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Provides real-time vulnerability intelligence including CVE lookup, EPSS exploit probability, and CISA KEV status from free APIs, enabling AI assistants to prioritize CVEs by real-world risk.
      MIT