Cybersecurity Vulnerability Intel
Let your coding agent pull CVE details, known-exploited flags, exploit likelihood, and ATT&CK context while you triage dependencies or prep a release.
Overview
Cybersecurity Vulnerability Intel is an MCP server for the Ship phase that enriches CVEs with NIST NVD, CISA KEV, EPSS, and MITRE ATT&CK data through seven agent tools.
What is this MCP server?
- Seven MCP tools spanning NIST NVD, CISA KEV, EPSS, and MITRE ATT&CK in one remote server
- Streamable HTTP endpoint on Apify—no local clone required to register the server
- Agent-callable CVE lookup instead of tab-hopping across government security sites
- Useful for answering “is this CVE actively exploited?” and “how bad is EPSS?” in one session
- Pairs with dependency scanners: agent enriches raw CVE IDs with authoritative intel
- 7 MCP tools
- Data sources: NIST NVD, CISA KEV, EPSS, MITRE ATT&CK
- Hosted streamable-http remote on Apify
What problem does it solve?
Dependency alerts give you CVE IDs without telling you whether attackers are already exploiting them or how ATT&CK techniques apply to your stack.
Who is it for?
Indie devs and small teams doing pre-release dependency review or incident triage who want NVD plus KEV plus EPSS in one MCP registration.
Skip if: Builders who need automated repo scanning, SAST/DAST, or secret detection without bringing their own CVE list.
What do I get? / Deliverables
After you add the remote, your agent can return prioritized, government-sourced vulnerability context in the same thread where you fix or waive each finding.
- Structured CVE and severity context from NIST NVD
- KEV and EPSS signals to prioritize patches
- ATT&CK-linked context for agent-written remediation notes
Recommended MCP Servers
Journey fit
Vulnerability intelligence belongs on the Ship shelf because solo builders use it right before launch and during dependency updates—not as early idea research. Security subphase is the canonical fit for NVD/KEV/EPSS/ATT&CK lookups tied to patching, SBOM review, and pre-ship hardening.
How it compares
Federal vulnerability intel MCP integration, not a replacement for Dependabot or a full penetration-test skill.
Common Questions / FAQ
Who is Cybersecurity Vulnerability Intel for?
Solo builders and agent users who ship software with third-party dependencies and want authoritative CVE, KEV, EPSS, and ATT&CK context inside the IDE.
When should I use Cybersecurity Vulnerability Intel?
Use it during Ship security work—before a production deploy, after a scanner surfaces CVEs, or when researching whether to patch or accept risk on a library.
How do I add Cybersecurity Vulnerability Intel to my agent?
Register the streamable-http remote URL from the server manifest (cybersecurity-vuln-mcp.apify.actor/mcp) in your MCP client, then invoke the seven tools from agent chat.