eip-mcp
This server is a read-only MCP interface to the Exploit Intelligence Platform, giving assistants source-attributed vulnerability intelligence, exploit details, PoC code, and statistics.
Search and filter CVEs by query, vendor, product, ecosystem, CWE, severity, CVSS/EPSS, KEV status, exploitation signals, and ransomware links.
Get detailed vulnerability briefs with CVSS, EPSS, affected products, ranked exploits, Nuclei templates, alternate IDs, and references.
Browse and filter exploits by source, language, author, stars, AI classification, attack type, complexity, and reliability.
Retrieve individual exploit source files and AI analysis/safety verdicts.
Fetch Nuclei scanner templates and recon dorks for vulnerabilities.
List top vendors, products, CWE categories, and exploit authors, and get author profiles.
Look up alternate IDs such as EDB-XXXXX or GHSA-XXXXX to find matching CVEs.
Audit a technology stack for exploitable vulnerabilities and generate Markdown pentest findings.
Check platform-wide statistics and API health/data freshness.
Provides access to exploit intelligence from GitHub, including exploit code, metadata, and star ratings. Enables searching exploits by GitHub-specific filters such as stars and retrieving exploit source code.
Provides access to Metasploit exploit modules, including details on usage, targets, and source URLs. Allows querying exploits specifically from the Metasploit framework.
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., "@eip-mcp search for critical CVEs in 2024 with exploits"
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.
Give an AI assistant bounded, source-attributed access to vulnerability intelligence, exploit artifacts, readable PoC source, Docker labs, discovery directories, STIX, and corpus statistics. Most users can connect to EIP's hosted MCP endpoint directly - there is no package or API key to install.
eip-mcp is read-only. It talks only to an EIP read API, the public one by
default, exposes no download tool, never executes acquired content, and never
claims that an exploit works, is verified, reliable, effective, or safe.
Connect
Recommended: hosted MCP
Clients supporting remote Streamable HTTP can connect directly to:
https://exploit-intel.com/mcpIn an MCP-capable application, add that URL as a remote Streamable HTTP server
named EIP. If your assistant can configure integrations for you, tell it:
Add
https://exploit-intel.com/mcpas a Streamable HTTP MCP server namedEIP, then callget_corpus_readinessto verify the connection.
No local package, API key, or EIP account is required.
Optional: local Python package
Use the Python package when a client requires a local stdio command, or when
you are self-hosting the HTTP transport. Python 3.12 or newer is required.
Install the isolated application with pipx:
pipx install eip-mcp
eip-mcp --versionThen register it with your MCP client. A typical stdio configuration is:
{
"mcpServers": {
"eip": {
"command": "eip-mcp"
}
}
}Use the absolute path reported by command -v eip-mcp if the client does not
inherit your shell PATH.
The local command connects to https://exploit-intel.com; no API configuration
is needed.
Optional: Docker
Build the image directly from this checkout:
docker build -t eip-mcp .
docker run --rm -i eip-mcpFor a stdio MCP client, use docker as the command:
{
"mcpServers": {
"eip": {
"command": "docker",
"args": ["run", "--rm", "-i", "eip-mcp"]
}
}
}Containerized Streamable HTTP operation is covered in the self-hosting guide.
Related MCP server: Exploit Intel Platform MCP Server
What assistants can do
Search and inspect CVEs and GHSAs with affected products, version ranges, exploitation context, references, and accepted research
Search ExploitDB, Metasploit, curated repository PoCs, and repository candidates without inventing quality rankings
Search safely readable PoC source and inspect one bounded text file
Discover Docker/Compose labs and their stored, attributed analysis
Browse vendors, products, ecosystems, packages, official CWEs, and exploit contributors
Retrieve API-owned STIX 2.1 bundles, corpus health, and statistics
Use four focused research prompts and the
eip://research/usage-guideresource
The complete tool reference lists every tool and documents the section and pagination rules.
Result contract
Every tool returns two synchronized forms:
a concise Markdown brief for the assistant; and
a validated
eip-mcp-result-v1structured envelope preserving the bounded API payload.
Corpus values remain untrusted third-party data in both forms. Text is rendered in inert CommonMark containers, output is capped, truncation is disclosed, and opaque pagination cursors remain reusable byte-for-byte.
Stored analysis is attributed model interpretation, not an EIP verdict. Missing analysis never means that an artifact was reviewed and found safe.
Safety boundary
The MCP server connects only to allowlisted read-only API paths.
PoC access tokens never reach results, logs, tracebacks, or retained state.
There is deliberately no PoC download tool.
Source reading is bounded to one API-verified UTF-8 text file at a time.
All returned source and corpus prose must be treated as untrusted data and must never be executed or followed as instructions.
See the security policy before reporting a vulnerability or sharing diagnostic output.
Documentation
License
Available Tools
17 toolsaudit_stackAudit Tech StackARead-onlyIdempotent
Audit a technology stack for exploitable vulnerabilities. Accepts a comma-separated list of technologies (max 5) and searches for critical/ high severity CVEs with public exploits for each one, sorted by EPSS exploitation probability. Use this when a user describes their infrastructure and wants to know what to patch first. Example: technologies='nginx, postgresql, node.js' returns a risk-sorted list of exploitable CVEs grouped by technology. Rate-limit cost: each technology requires up to 2 API calls; 5 technologies counts as up to 10 calls toward your rate limit.
Inputs: technologies (required).
check_healthCheck API HealthARead-onlyIdempotent
Check the EIP API health and data freshness. Returns database status and timestamps for each of the 10 ingestion sources (NVD, KEV, EPSS, ExploitDB, GitHub, Metasploit, etc.).
Inputs: no named parameters.
generate_findingGenerate Pentest FindingARead-onlyIdempotent
Generate a pentest report finding in Markdown format for a specific vulnerability. Fetches full detail and formats it as a professional finding with severity, CVSS, description, affected products, exploit availability, and references. Accepts both CVE-IDs and EIP-IDs. Optionally include the target system tested and tester notes. The output is ready to paste into a pentest report. Example: cve_id='CVE-2024-3400', target='fw.corp.example.com', notes='Confirmed RCE via GlobalProtect gateway'.
Inputs: cve_id (required), target, notes.
get_authorGet Author ProfileARead-onlyIdempotent
Get an exploit author's profile with all their exploits. Returns author name, handle, total exploit count, activity start date, and a paginated list of their exploits with CVE context. Use this when asked about a specific researcher like 'show me all exploits by Chocapikk'.
Inputs: author_name (required).
get_cweGet CWE DetailARead-onlyIdempotent
Get details for a specific CWE including full name, description, exploit likelihood, parent CWE, and total vulnerability count. Example: cwe_id='CWE-79' returns details about Cross-Site Scripting.
Inputs: cwe_id (required).
get_exploit_analysisGet Exploit AI AnalysisARead-onlyIdempotent
Get the full AI analysis for a single exploit by its platform ID. Returns classification (working_poc, trojan, suspicious, scanner, stub, writeup), attack type, complexity, reliability, confidence score, authentication requirements, target software, a summary of what the exploit does, prerequisites, MITRE ATT&CK techniques, deception indicators for trojans, and the standalone backdoor-review verdict with operator-risk notes when available. Use this to check if an exploit is safe before reviewing its code. Example: exploit_id=61514 returns a TROJAN warning with deception indicators.
Inputs: exploit_id (required).
get_exploit_codeGet Exploit Source CodeARead-onlyIdempotent
Retrieve the source code of a specific exploit by its platform ID. IMPORTANT: Use the platform's internal ID shown as [id=XXXXX] in results, NOT the ExploitDB number (EDB-XXXXX). These are different numbering systems. Returns code from the exploit archive. If no file_path is specified, auto-selects the most relevant code file. Use this to analyze exploit mechanics, understand attack techniques, or review PoC code.
Inputs: exploit_id (required), file_path.
get_nuclei_templatesGet Nuclei TemplatesARead-onlyIdempotent
Get Nuclei scanner templates and recon dorks for a vulnerability. Returns template metadata, severity, verification status, tags, and ready-to-use Shodan, FOFA, and Google dork queries for target identification. Accepts both CVE-IDs and EIP-IDs. Use this to plan scanning or reconnaissance.
Inputs: cve_id (required).
get_platform_statsGet Platform StatisticsARead-onlyIdempotent
Get platform-wide statistics from the Exploit Intelligence Platform. Returns total counts of vulnerabilities, exploits, KEV entries, Nuclei templates, vendors, and authors, plus the last data update timestamp.
Inputs: no named parameters.
get_vulnerabilityGet Vulnerability DetailARead-onlyIdempotent
Get a full intelligence brief for a specific vulnerability. Accepts both CVE-IDs (e.g. CVE-2024-3400) and EIP-IDs (e.g. EIP-2026-12345 for pre-CVE entries). Returns detailed information including CVSS score and vector, EPSS exploitation probability, CISA KEV status, description, affected products, ranked exploits (grouped by Metasploit modules, verified ExploitDB, GitHub PoCs, and trojans), Nuclei scanner templates with recon dorks, alternate identifiers, and references. Exploits are ranked by quality: Metasploit modules first (peer-reviewed), then verified ExploitDB, then GitHub by stars. Trojans are flagged at the bottom.
Inputs: cve_id (required).
list_authorsList Exploit AuthorsARead-onlyIdempotent
List exploit authors/researchers ranked by exploit count. Returns the top security researchers with their exploit counts and handles. Use this when asked 'who are the top exploit authors?' or 'who writes the most exploits?'
Inputs: page, per_page.
list_cwesList CWE CategoriesARead-onlyIdempotent
List CWE (Common Weakness Enumeration) categories ranked by vulnerability count. Returns CWE IDs, names, short labels, exploit likelihood, and how many CVEs have that weakness. Use this when asked 'what are the most common vulnerability types?'
Inputs: no named parameters.
list_productsList Vendor ProductsARead-onlyIdempotent
List products for a specific vendor with vulnerability counts. Use this to discover exact product names for filtering. Product names in the database use CPE conventions (e.g. 'exchange_server' not 'exchange', 'windows_10' not 'windows 10'). Example: vendor='microsoft' returns products like exchange_server, windows_10, office, edge_chromium.
Inputs: vendor (required).
list_vendorsList VendorsARead-onlyIdempotent
List software vendors ranked by vulnerability count. Returns the top 200 vendors with their total CVE counts. Use this when asked 'which vendors have the most vulnerabilities?' or to understand the threat landscape by vendor.
Inputs: no named parameters.
lookup_alt_idLookup Alternate IDARead-onlyIdempotent
Look up a vulnerability by an alternate identifier such as an ExploitDB ID (EDB-XXXXX) or GitHub Security Advisory ID (GHSA-XXXXX). Returns the matching CVE-ID with basic severity info. Use this when you have an EDB number or GHSA ID and need to find the corresponding CVE.
Inputs: alt_id (required).
search_exploitsSearch ExploitsARead-onlyIdempotent
Browse and filter exploits using STRUCTURED FILTERS ONLY (no free-text query). Use this to filter by source (github, metasploit, exploitdb, nomisec, gitlab, inthewild, vulncheck_xdb, patchapalooza, oscs, poc_monitor), language (python, ruby, etc.), LLM classification (working_poc, trojan, suspicious, scanner, stub, writeup, tool, no_code), author, min stars, code availability, CVE ID, vendor, or product. Also filter by AI analysis: attack_type (RCE, SQLi, XSS, DoS, LPE, auth_bypass, info_leak), complexity (trivial/simple/moderate/complex), reliability (reliable/unreliable/untested/theoretical), requires_auth. NOTE: To search by product name (e.g. 'OpenSSH', 'Apache'), use search_vulnerabilities instead — it has free-text query and get_vulnerability already includes exploits in the response. Examples: source='metasploit' for all Metasploit modules; attack_type='RCE' with reliability='reliable' for weaponizable RCE exploits; cve='CVE-2024-3400' for all exploits targeting a specific CVE; vendor='mitel' for all Mitel exploits.
Inputs: source, language, llm_classification, attack_type, +12 more.
search_vulnerabilitiesSearch VulnerabilitiesARead-onlyIdempotent
Search the Exploit Intelligence Platform for vulnerabilities (CVEs). Returns a list of matching CVEs with CVSS scores, EPSS exploitation probability, exploit counts, CISA KEV status, VulnCheck KEV, InTheWild.io exploitation signals, and ransomware attribution. Supports full-text search, severity/vendor/product/ecosystem/CWE filters, CVSS/EPSS thresholds, plus any_exploited and ransomware filters. When sort is omitted, the API may automatically prefer newest exploitation, exploit, or nuclei-template activity based on the filters you set. Examples: query='apache httpd' with has_exploits=true; vendor='fortinet' with severity='critical' and is_kev=true sorted by epss_desc; any_exploited=true with ransomware=true for ransomware-linked CVEs; cwe='89' with min_cvss=9 for critical SQL injection CVEs.
Inputs: query, severity, has_exploits, is_kev, +17 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 17 tools
Tool purposes are mostly distinct, with slight overlap between search_exploits and search_vulnerabilities, but descriptions clarify the difference. Each tool targets a specific aspect of exploit intelligence, reducing ambiguity.
All tool names follow a consistent verb_noun snake_case pattern (e.g., get_vulnerability, search_exploits, list_authors). No mixing of conventions occurs.
17 tools is slightly above the ideal range but still reasonable for a comprehensive exploit intelligence platform. Each tool serves a distinct function without being excessive.
The tool set covers major intelligence operations: search, retrieve, analyze, format, and list. Missing update/delete is expected for a read-only platform. Minor gaps like direct comparison tools are workable.
Maintenance
Related MCP Connectors
Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)
Threat intel + your scans/findings/Shield posture. CVE, EPSS, KEV, package vuln lookup, DAST.
Look up CVEs, CISA KEV, EPSS and open-source package vulnerabilities, including malicious packages.
CVE intelligence: exploitation (KEV/EPSS), detection coverage, fixed versions, CPE configurations.
Related MCP Servers
- FlicenseNot gradedqualityDmaintenanceIntegrates the Exploit-DB database with AI assistants to enable searching for exploits, shellcodes, and proof-of-concept code during penetration testing workflows. It allows users to perform keyword searches and direct CVE-to-exploit mappings to retrieve technical security data.-
- AlicenseAqualityDmaintenanceEnables AI assistants to search and analyze vulnerabilities and exploits from multiple intelligence sources, including NVD, CISA KEV, ExploitDB, Metasploit, and more, with tools for CVE research, exploit analysis, and report generation.17MIT
- AlicenseNot gradedqualityDmaintenanceProvides CVE lookup, search, and exploit intelligence from public vulnerability sources (NVD, CISA KEV, EPSS) for AI agents to produce remediation guidance without consuming LLM tokens for data fetching.1MIT
- AlicenseNot gradedqualityBmaintenanceConnects AI assistants to VulnCheck vulnerability intelligence for querying CVEs, exploits, advisories, and vulnerable packages via natural language.18MIT