Security Intel MCP
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Security Intel MCP look up CVE-2024-3094"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Security Intel MCP — by Datakoot
Vulnerability intelligence for AI agents — as MCP tools your agent can call mid-task. One keyless call fuses NVD, CISA KEV and FIRST EPSS. No API keys.
Tools
Tool | What it does | Source |
| CVE summary: description, CVSS score & severity, CWE, references, plus whether it is actively exploited (CISA KEV) and its exploit probability (EPSS) | NVD (NIST), CISA KEV, FIRST EPSS |
| Is a CVE on CISA's Known Exploited Vulnerabilities catalog? Or list the newest exploited CVEs (filter by vendor, product or ransomware use) | CISA KEV |
| Exploit probability (0–1) and percentile for one or many CVEs: the chance each is exploited in the next 30 days | FIRST EPSS |
| Known vulnerabilities for a package/version | OSV.dev |
| Audit a whole package.json (or dependency list) in one call | OSV.dev |
No API keys required for any tool.
Related MCP server: DepHealth MCP
Quick start
claude mcp add --transport http security-intel https://security.datakoot.com/mcpOr point any MCP client at https://security.datakoot.com/mcp.
Try it in 10 seconds — no key, no signup
Paste this into a terminal:
curl -s https://security.datakoot.com/mcp \
-H 'content-type: application/json' \
-H 'accept: application/json, text/event-stream' \
-d '{"jsonrpc": "2.0", "id": 1, "method": "tools/call", "params": {"name": "cve_lookup", "arguments": {"cve_id": "CVE-2021-44228"}}}'You get Log4Shell (CVE-2021-44228) in one answer: the NVD record (severity, CVSS vector, references), its CISA KEV entry (exploited in the wild, used in ransomware) and its EPSS exploit probability. No API key, nothing to sign up for.
Or point any MCP client at the URL and just ask your agent, in plain language:
"Is CVE-2021-44228 something I need to worry about?"
"Which of these CVEs is actually being exploited right now?"
"Audit my package.json for known vulnerabilities before I deploy."
Data & attribution
Vulnerability data comes from the National Vulnerability Database (NIST — US public domain), CISA's Known Exploited Vulnerabilities catalog (US public domain), FIRST EPSS and OSV.dev (CC-BY 4.0), the same open sources used by scanners like Trivy and Grype.
Part of Datakoot — keyless intelligence APIs for AI agents.
Available Tools
5 toolsaudit_dependenciesAudit DependenciesARead-onlyIdempotentInspect
Audit a whole dependency manifest for known vulnerabilities in one call. Paste a package.json (as 'manifest'), or pass a 'dependencies' array of {name, version} objects. Returns per-package findings and a summary. Ecosystem defaults to npm.
Inputs: manifest, ecosystem, dependencies. Returns: source, verdict, findings, ecosystem, +6 more
cve_lookupCVE LookupARead-onlyIdempotentInspect
Look up a CVE by ID and get a compact summary: description, CVSS score & severity, vector, CWE weakness, publish date, references — plus whether it is on the CISA Known-Exploited list (actively exploited in the wild) and its EPSS exploit-probability. Sources: NVD (NIST), CISA KEV, FIRST EPSS.
Inputs: cve_id (required). Returns: id, cwe, cvss, status, +8 more
epss_scoreEPSS ScoreARead-onlyIdempotentInspect
Get the EPSS exploit-probability score (0-1) and percentile for one or more CVEs — the likelihood each is exploited in the next 30 days. Use it to prioritize patching. Pass cve_id for one, or cve_ids (array or comma-separated) for many. Source: FIRST.org EPSS.
Inputs: cve_id, cve_ids. Returns: note, as_of, model, scored, +3 more
known_exploitedKnown ExploitedARead-onlyIdempotentInspect
Check whether a CVE is on the CISA Known Exploited Vulnerabilities (KEV) catalog — confirmed exploited in the wild — or list the most recently added exploited vulnerabilities. Pass cve_id to check one; omit it to list recent (optionally filter by vendor/product, or ransomware_only). Source: CISA KEV, updated ~daily.
Inputs: limit, cve_id, vendor, ransomware_only. Returns: name, cve_id, filter, listed, +13 more
package_vulnerabilitiesPackage VulnerabilitiesARead-onlyIdempotentInspect
List known vulnerabilities for a software package (optionally a specific version) via OSV. Ecosystems: npm, pypi, cargo, go, maven, rubygems, nuget, composer, pub, hex.
Inputs: name (required), ecosystem (required), version. Returns: name, source, version, ecosystem, +3 more
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 5 tools
The five tools mostly target distinct resources: individual CVE lookup, KEV catalog queries, EPSS scoring, per-package OSV lookup, and manifest-wide auditing. However, cve_lookup already bundles KEV and EPSS results inline, so an agent may be unsure when to call the dedicated known_exploited or epss_score tools versus the composite lookup. The package_vulnerabilities vs audit_dependencies split is clear (single package vs whole manifest).
Names are readable but follow mixed conventions: cve_lookup, known_exploited, epss_score, package_vulnerabilities, and audit_dependencies blend noun_noun, adjective-style, and verb_noun forms. Two tools (audit_dependencies, package_vulnerabilities) use verb-based action naming while others are noun phrases. Not chaotic, but no single predictable pattern.
Five tools is a tight, well-scoped surface for a security-intelligence server covering CVE data, exploit likelihood, and dependency auditing. Each tool earns its place without redundancy or thinness. No unused or filler tools.
The surface covers the core workflows: CVE detail, known-exploited status, EPSS prioritization, package lookup, and full manifest auditing. Minor gaps exist, such as keyword/vendor-based CVE search or advisory text search, but agents can work around these via CVE IDs and OSV queries.
Maintenance
Related MCP Connectors
Pay-per-call cybersecurity for AI agents: vuln scans, threat intel, compliance, code security.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Package intelligence for AI agents across npm, PyPI, crates.io and deps.dev. No API keys.
Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)
Related MCP Servers
- FlicenseAqualityAmaintenanceDependency intelligence for AI agents. CVE scanning, health checks, upgrade planning.92-
- AlicenseAqualityDmaintenanceDependency security & health auditing for AI agents with no account or API key required.22MIT
- AlicenseNot gradedqualityCmaintenanceProvides security checks for AI agents, including secret scanning, CVE lookup, and dependency vulnerability scanning, all running locally except for CVE lookups.MIT

Fetter MCPofficial
FlicenseNot gradedqualityBmaintenanceProvides real-time Python package vulnerability data, enabling AI agents to check CVEs, CVSS scores, and safe versions for informed dependency decisions.1-