Eip MCP Server

An MCP (Model Context Protocol) server that gives AI assistants access to the [Exploit Intelligence Platform](https://exploit-intel.com) —

Remote serverstreamable-httpPython

What is the Eip MCP MCP server?

An MCP (Model Context Protocol) server that gives AI assistants access to the Exploit Intelligence Platform — vulnerability and exploit intelligence from NVD, CISA KEV, VulnCheck KEV, InTheWild.io, ENISA EUVD. That is what the eip mcp mcp server brings to an AI assistant: the same capability, reachable through the Model Context Protocol rather than a separate app or dashboard.

The short version

  • Give AI assistants real-time vulnerability and exploit intelligence
  • Query CVEs with rich filters and ranked exploit context
  • Include AI exploit analysis, MITRE ATT&CK mapping, and trojan indicators
  • Generate pentest findings directly from CVE data
  • Every exploit includes a clickable source URL (GitHub, ExploitDB, Metasploit)
  • Nuclei templates include description, impact, and remediation text

The tools it exposes

The server publishes 14 tools. What each one is for:

  • search_vulnerabilities — Search CVEs with full-text query and filters: severity, vendor, product, ecosystem, CWE, CVSS/EPSS thresholds, KEV, Nuclei, year, date range
  • get_vulnerability — Full intelligence brief for a CVE or EIP-ID. Includes ranked exploits (AI analysis, MITRE techniques, source URLs), products, Nuclei templates
  • search_exploits — Browse exploits with structured filters only (no free-text query): source, language, LLM classification, author, stars, CVE, vendor, product
  • get_exploit_code — Retrieve exploit source code by platform ID (auto-selects main file)
  • get_exploit_analysis — Full AI analysis for a single exploit: classification, attack type, complexity, reliability, MITRE ATT&CK, summary, and trojan/deception indicators
  • get_nuclei_templates — Nuclei scanner templates with description, impact, remediation, and Shodan/FOFA/Google dork queries
  • list_authors — Top exploit researchers ranked by exploit count
  • get_author — Author profile with all their exploits and CVE context
  • list_cwes — CWE categories ranked by vulnerability count
  • get_cwe — CWE detail with description, exploit likelihood, parent hierarchy
  • list_vendors — Software vendors ranked by vulnerability count
  • list_products — Discover exact product names for a vendor (CPE name lookup with vuln counts)

What it needs from you

Configuration is passed through the environment: EIP_MCP_HOST, EIP_API_KEY. Treat anything key-shaped as a real credential — scope it to the minimum the server needs, and rotate it if it ever lands in a shared config.

  • Python 3.10 or newer (check with python3 --version or python --version) - pip (comes with Python on most systems) - An MCP-compatible AI client (Cursor IDE, Claude Desktop, etc.) Base installation is enough for stdio clients. If you want to run the standalone Streamable HTTP server, install the optional HTTP extra: ```bash pip install "eip-mcp[http]"

Getting it running

Because this one is hosted, setup is mostly authentication — you point your client at the endpoint and approve access. Nothing runs on your machine, so there is no runtime to keep patched.

How it compares

Among the developer tooling options, the useful question is rarely "what can it do" but "what does it cost you to run" — permissions, credentials, and how much of your context its toolset consumes. Eip MCP's toolset — search_vulnerabilities, get_vulnerability, search_exploits and 11 more — is a fair guide to whether it matches your workflow. It is maintained by exploitintel; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against Eip MCP's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.

Things to watch

  • Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
  • With 14 tools registered it takes up a noticeable share of the context window; turn it off in projects that never touch Eip MCP.
  • Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
  • Keep per-call confirmation enabled while you learn its behaviour; it is the cheapest safeguard you have.

Available tools

ToolWhat it does
search_vulnerabilitiesSearch CVEs with full-text query and filters: severity, vendor, product, ecosystem, CWE, CVSS/EPSS thresholds, KEV, Nuclei, year, date range. Supports explicit score mode via score_version + min_score + sort=score_desc.
get_vulnerabilityFull intelligence brief for a CVE or EIP-ID. **Includes ranked exploits** (AI analysis, MITRE techniques, source URLs), products, Nuclei templates (with description/impact/remediation), references.
search_exploitsBrowse exploits with **structured filters only** (no free-text query): source, language, LLM classification, author, stars, CVE, vendor, product, attack_type, complexity, reliability, requires_auth.
get_exploit_codeRetrieve exploit source code by platform ID (auto-selects main file)
get_exploit_analysisFull AI analysis for a single exploit: classification, attack type, complexity, reliability, MITRE ATT&CK, summary, and trojan/deception indicators
get_nuclei_templatesNuclei scanner templates with description, impact, remediation, and Shodan/FOFA/Google dork queries
list_authorsTop exploit researchers ranked by exploit count
get_authorAuthor profile with all their exploits and CVE context
list_cwesCWE categories ranked by vulnerability count
get_cweCWE detail with description, exploit likelihood, parent hierarchy
list_vendorsSoftware vendors ranked by vulnerability count
list_productsDiscover exact product names for a vendor (CPE name lookup with vuln counts)
lookup_alt_idResolve alternate IDs (EDB-XXXXX, GHSA-XXXXX) to their CVE
audit_stackAudit a tech stack for critical/high severity CVEs with exploits, sorted by EPSS risk

How to install the Eip MCP MCP server

{
  "mcpServers": {
    "eip": {
      "command": "uvx",
      "args": ["eip-mcp"],
      "env": {
        "EIP_MCP_HOST": "your-value",
        "EIP_API_KEY": "your-value"
      }
    }
  }
}

Add to claude_desktop_config.json, then restart Claude Desktop.

Configuration

  • Python 3.10 or newer (check with python3 --version or python --version) - pip (comes with Python on most systems) - An MCP-compatible AI client (Cursor IDE, Claude Desktop, etc.) Base installation is enough for stdio clients. If you want to run the standalone Streamable HTTP server, install the optional HTTP extra: ```bash pip install "eip-mcp[http]"
VariableDescriptionRequired
EIP_MCP_HOSTEndpoint or connection string the server talks to.Optional
EIP_API_KEYCredential the server authenticates with.Yes

Example prompts to try

  • Use Eip MCP to search vulnerabilities.
  • Use Eip MCP to get vulnerability.
  • Use Eip MCP to search exploits.

Frequently asked questions

It connects Eip MCP to MCP-compatible AI assistants such as Claude and Cursor, exposing 14 tools (search_vulnerabilities, get_vulnerability, search_exploits, and more) that the assistant can call on your behalf. Instead of copying data back and forth by hand, the assistant works with Eip MCP directly.