mcpField
S

Security Intel MCP

Remote
github.com/selflabbsSecurity0Updated 4d ago
Repository

About Security Intel MCP

Security Intel MCP gives AI agents vulnerability data from NVD, CISA KEV, FIRST EPSS and OSV.dev. It supports individual CVE checks and dependency audits without API keys.

Key features

  1. 01Combine CVE details with exploitation signals
  2. 02Check CISA known-exploited listings
  3. 03Get EPSS probability and percentile
  4. 04Look up package and version vulnerabilities
  5. 05Audit package.json or dependency lists

Use cases

  1. 01Assess a CVE’s severity and exploitation status
  2. 02Prioritize CVEs by exploit probability
  3. 03Audit dependencies before deployment

MCP support

It exposes vulnerability lookup and dependency audit tools to MCP clients. The tools require no API keys.

Configuration

Remote servers need no local install. Pick your client, then copy the config or install in one click.

Endpointhttps://security.selflabbs.com/mcp
Copy install command
Claude CodeTerminal
Cursor.cursor/mcp.json
VS Code.vscode/mcp.json
Claude Desktopclaude_desktop_config.json
Windsurf~/.codeium/windsurf/mcp_config.json

Run commands in a terminal; paste JSON into the client’s MCP config and restart. Servers that need sign-in will prompt on first connect.

Tools

Details

From the project README

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

ToolWhat it doesSource
cve_lookupCVE 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
known_exploitedIs a CVE on CISA's Known Exploited Vulnerabilities catalog? Or list the newest exploited CVEs (filter by vendor, product or ransomware use)CISA KEV
epss_scoreExploit probability (0–1) and percentile for one or many CVEs: the chance each is exploited in the next 30 daysFIRST EPSS
package_vulnerabilitiesKnown vulnerabilities for a package/versionOSV.dev
audit_dependenciesAudit a whole package.json (or dependency list) in one callOSV.dev

No API keys required for any tool.

Quick start

claude mcp add --transport http security-intel https://security.datakoot.com/mcp

Or 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.

Comments

Markdown supported

New to MCP?

From what the protocol is to installing your first server, these answers cover most first questions.

An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.