Skip to main content

vuln-intel-mcp

A local MCP server that gives any AI agent — Claude Desktop, Claude Code, Cline, Cursor, or your own — CVE remediation intelligence from public sources: NVD, CISA KEV, and FIRST EPSS.

Your model does the reasoning. This server does not.

That is the whole point: the server only does the token-free work — fetching public vulnerability data over HTTP and computing an objective priority. It never calls an LLM, needs no API key, and sends nothing anywhere except read-only requests to public vulnerability databases. The remediation write-up and the ServiceNow note are produced by your model, in your session, from the structured facts the tools return. No one's API tokens are consumed but your own.

Built by Rohan Raj. A hosted demo with AI synthesis and a live cost ledger runs at clawofrohan.com/vuln-intel.


Install & connect

You need Python 3.10+. The easiest runner is uv (uvx downloads and runs on demand — nothing to install permanently).

Claude Code

claude mcp add vuln-intel -- uvx vuln-intel-mcp

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "vuln-intel": {
      "command": "uvx",
      "args": ["vuln-intel-mcp"]
    }
  }
}

Cline / Cursor / any MCP client

Same shape — command uvx, args ["vuln-intel-mcp"]. Or if you installed it with pip install vuln-intel-mcp, use command vuln-intel-mcp with no args.

Restart the client, and ask it something like "Should I patch CVE-2024-3400?" or "What's the exploit status of Log4Shell?"


Tools

Tool What it returns (token-free) What your model does with it
cve_lookup NVD facts, CVSS, CWEs, affected products, fix versions from CPE data, EPSS probability, CISA KEV status, and a computed P1–P4 priority Writes fix versions, remediation steps, workarounds, and a ServiceNow VR note
cve_search Candidate CVEs for a free-form product/keyword query (NVD keyword search) Picks the right CVE, then calls cve_lookup
cve_exploit_intel Public exploit signals — KEV exploited/ransomware flags, EPSS score, and public GitHub repos referencing the CVE (often PoC/exploit code) Judges weaponization and urgency

Optional environment variables

All optional — the server works with none. These raise your own public-API rate limits:

  • NVD_API_KEY — a free NVD API key for higher NVD throughput.
  • GITHUB_TOKEN — a GitHub token for more GitHub repo searches in cve_exploit_intel.

Privacy

  • No telemetry. No account. No key required.
  • Outbound requests go only to services.nvd.nist.gov, api.first.org, cisa.gov, and (for exploit intel) api.github.com.
  • The CVE ids and search terms you look up are sent to those public services, exactly as if you visited them in a browser.

License

MIT © Rohan Raj

Metadata

Release files for vuln-intel-mcp 0.1.0

For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.

Source distribution (sdist)

Source distribution for vuln-intel-mcp 0.1.0
File Size Uploaded Provenance
vuln_intel_mcp-0.1.0.tar.gz 7.2 kB Without provenance Details

Built distribution (wheel)

Table of built distributions (wheels) for vuln-intel-mcp 0.1.0
File Interpreter ABI Platform
vuln_intel_mcp-0.1.0-py3-none-any.whl Python 3 none any Details

Total release size: 15.5 kB

Release files / vuln_intel_mcp-0.1.0.tar.gz

Download URL vuln_intel_mcp-0.1.0.tar.gz
Size 7.2 kB
Tags Source
SHA-256 checksum
How to use checksums
d70f2b4a649de18e437245ea2521ff7c717fc3b12a4c5f378bab89f3ae108870
BLAKE2b-256 checksum
How to use checksums
e44170d2d53c17dba0919033cb001603c077c09a9a1e9b15bfe7ed1380fe93c1
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.10.9 {"installer":{"name":"uv","version":"0.10.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Release files / vuln_intel_mcp-0.1.0-py3-none-any.whl

Download URL vuln_intel_mcp-0.1.0-py3-none-any.whl
Size 8.3 kB
Tags Python 3
SHA-256 checksum
How to use checksums
3b792c7e8f78ad36088788987c254792dc335a39f0a89cf8f9064b8751294f05
BLAKE2b-256 checksum
How to use checksums
9ffef8b4093bdc891f9a631eabe2f225f529a40294f73fc4702746a460722cfc
Upload date
Uploaded using Trusted Publishing?
What is trusted publishing?
No
Uploaded via uv/0.10.9 {"installer":{"name":"uv","version":"0.10.9","subcommand":["publish"]},"python":null,"implementation":{"name":null,"version":null},"distro":{"name":"macOS","version":null,"id":null,"libc":null},"system":{"name":null,"release":null},"cpu":null,"openssl_version":null,"setuptools_version":null,"rustc_version":null,"ci":null}

Security for vuln-intel-mcp 0.1.0

Provenance

Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.

No provenance found

None of the files in this release were uploaded with provenance metadata.

A note on package security

PyPI is a repository for distributing packages, not a service for auditing them. While third-party security researchers and our staff do their best to detect and remove malicious packages, PyPI cannot guarantee the quality, security or suitability of any given package.

To learn more about protecting yourself from malicious actors, visit our package security documentation.

Release history Release notifications | RSS feed

This release

0.1.0 This release

2 release files No provenance

Anthropic, PBC Visionary sponsor Bloomberg Visionary sponsor Hudson River Trading Visionary sponsor Meta Visionary sponsor NVIDIA Visionary sponsor Microsoft Sustainability sponsor Depot Continuous Integration AWS Cloud computing and Security Sponsor Datadog Monitoring Fastly CDN Google Download Analytics Sentry Error logging StatusPage Status page