Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database

REMOTE · MCP.EXPLOIT-INTEL.COM · 2 COMPONENTS · SCANNED SEP 20

Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)

−82 this week 0 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security11
Transport & Reachability0
Schema Quality & AI Usability0
  • Schema not yet verified: we couldn't read the endpoint's schema.Unverified
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Tool coverage not yet verified: we couldn't read the endpoint's tools.Unverified
Tool Safety

Not scored yet: our latest scan of this component recorded no findings here. It fills in the next time we score it.

Capabilities0
  • Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified

Unverified: 4 categories

Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

Install

How do I install the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server?

Exploit Intelligence Platform — CVE, Vulnerability and… is a hosted endpoint at https://mcp.exploit-intel.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.exploit-intel.com

# add to Claude Code
claude mcp add --transport http com-exploit-intel-eip-mcp 'https://mcp.exploit-intel.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-exploit-intel-eip-mcp": {
      "url": "https://mcp.exploit-intel.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-exploit-intel-eip-mcp": {
      "type": "http",
      "url": "https://mcp.exploit-intel.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-exploit-intel-eip-mcp]
url = "https://mcp.exploit-intel.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-exploit-intel-eip-mcp": {
      "type": "remote",
      "url": "https://mcp.exploit-intel.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-exploit-intel-eip-mcp --url 'https://mcp.exploit-intel.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-exploit-intel-eip-mcp:
    url: "https://mcp.exploit-intel.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-exploit-intel-eip-mcp": {
      "Transport": "http",
      "Url": "https://mcp.exploit-intel.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-exploit-intel-eip-mcp -t streamable-http -u 'https://mcp.exploit-intel.com/mcp'
// mcp.json
{
  "mcpServers": {
    "com-exploit-intel-eip-mcp": {
      "type": "http",
      "url": "https://mcp.exploit-intel.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Aug 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 20 Aug 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 19 Aug 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 18 Aug 26 −17

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 17 Aug 26 −16

    The score moved with no change recorded against any check. We would rather say so than guess.

  • 15 Aug 26 0
    • Endpoint reachability: reachable → unreachable security
    • HSTS header: pass → unverified security
    • Authorization: partial → unverified security
    • TLS certificate: pass → unverified security
    • DNSSEC: fail → unverified security
    • Stability: 0.63 → unverified security
    • Transport: pass → fail security
    • Tool coverage: 100 → unverified functional
    • Capabilities: pass → unverified functional
    • Schema quality: 100 → unverified functional
  • 13 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Aug 2026 · Probed https://mcp.exploit-intel.com/mcp

TLS unreached
DNSSEC inconclusive

Validation of mcp.exploit-intel.com. Inconclusive

Zone DS Keys Algorithms Outcome
mcp.exploit-intel.com. Error no A/AAAA/CNAME RRset answered for the name
Authentication Inconclusive

We could not reach the endpoint well enough to judge its authorisation posture.

Result Inconclusive

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.exploit-intel.com/mcp Unreachable
http (plaintext) http://mcp.exploit-intel.com/mcp HTTPS enforced
MCP tools · 17 exposed · ~2,792 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
audit_stack ~157

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.

NameTypeReqDescription
technologiesstringyesComma-separated list of technologies (e.g. 'nginx, postgresql, node.js'). Max 5.

No output schema declared.

No examples provided.

check_health ~54

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

generate_finding ~186

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

NameTypeReqDescription
cve_idstringyesCVE or EIP identifier (e.g. 'CVE-2024-3400')
notesstringTester notes to include in the finding. Optional.
targetstringTarget system tested (e.g. 'fw.corp.example.com'). Optional.

No output schema declared.

No examples provided.

get_author ~84

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

NameTypeReqDescription
author_namestringyesAuthor name (e.g. 'Chocapikk')

No output schema declared.

No examples provided.

get_cwe ~76

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.

NameTypeReqDescription
cwe_idstringyesCWE identifier (e.g. 'CWE-79' or '79')

No output schema declared.

No examples provided.

get_exploit_analysis ~153

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.

NameTypeReqDescription
exploit_idintegeryesPlatform exploit ID (the [id=XXXXX] number from results — NOT the EDB number)

No output schema declared.

No examples provided.

get_exploit_code ~156

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.

NameTypeReqDescription
exploit_idintegeryesPlatform exploit ID (the [id=XXXXX] number from results — NOT the EDB number)
file_pathstringRelative path inside the exploit archive (optional — auto-selects if omitted). Absolute paths and traversal patterns are rejected.

No output schema declared.

No examples provided.

get_nuclei_templates ~104

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.

NameTypeReqDescription
cve_idstringyesCVE or EIP identifier (e.g. 'CVE-2024-27198')

No output schema declared.

No examples provided.

get_platform_stats ~49

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_vulnerability ~205

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.

NameTypeReqDescription
cve_idstringyesCVE or EIP identifier (e.g. 'CVE-2024-3400' or 'EIP-2026-12345')

No output schema declared.

No examples provided.

list_authors ~87

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?'

NameTypeReqDescription
pageintegerPage number (default: 1)
per_pageintegerResults per page (1-50, default: 25)

No output schema declared.

No examples provided.

list_cwes ~58

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?'

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

list_products ~107

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.

NameTypeReqDescription
vendorstringyesVendor name (e.g. 'microsoft', 'apache', 'fortinet')

No output schema declared.

No examples provided.

list_vendors ~51

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.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

lookup_alt_id ~110

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.

NameTypeReqDescription
alt_idstringyesAlternate ID (e.g. 'EDB-48537', 'GHSA-jfh8-c2jp-5v3q')

No output schema declared.

No examples provided.

search_exploits ~561

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.

NameTypeReqDescription
attack_typestringFilter by attack type from AI analysis (case-insensitive on input; canonical casing returned)
authorstringFilter by author name
complexitystringFilter by exploit complexity
cvestringFilter by CVE ID (e.g. 'CVE-2024-3400') — returns all exploits for that CVE
has_codebooleanOnly exploits with downloadable code
languagestringFilter by language: python, ruby, go, c, etc.
llm_classificationstringFilter by LLM classification
min_starsintegerMinimum GitHub stars
pageintegerPage number (default: 1)
per_pageintegerResults per page (1-25, default: 10)
productstringFilter by product name (e.g. 'micollab', 'pan-os')
reliabilitystringFilter by exploit reliability
requires_authbooleanFilter by whether exploit requires authentication
sortstringSort order
sourcestringFilter by source
vendorstringFilter by vendor name (e.g. 'mitel', 'fortinet') — returns exploits for all CVEs affecting that vendor

No output schema declared.

No examples provided.

search_vulnerabilities ~594

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.

NameTypeReqDescription
any_exploitedbooleanOnly return CVEs exploited in the wild (CISA KEV + VulnCheck KEV + InTheWild.io)
cwestringFilter by CWE ID (e.g. '79' or 'CWE-79')
date_fromstringStart date for CVE publication (YYYY-MM-DD)
date_tostringEnd date for CVE publication (YYYY-MM-DD)
ecosystemstringFilter by package ecosystem
has_exploitsbooleanOnly return CVEs with public exploit code
has_nucleibooleanOnly return CVEs with Nuclei scanner templates
is_kevbooleanOnly return CISA Known Exploited Vulnerabilities
min_cvssnumberMinimum CVSS v3 score (0-10)
min_epssnumberMinimum EPSS score (0-1)
min_scorenumberMinimum score for the selected score_version (0-10)
pageintegerPage number (default: 1)
per_pageintegerResults per page (1-25, default: 10)
productstringFilter by product name (e.g. 'exchange', 'pan-os')
querystringSearch keywords (e.g. 'apache httpd', 'log4j'). Optional if filters are provided.
ransomwarebooleanOnly return CVEs with confirmed ransomware campaign use
score_versionstringScore family for min_score / score_desc
severitystringFilter by severity level
sortstringSort order. Aliases are normalized to the current server schema.
vendorstringFilter by vendor name (e.g. 'microsoft', 'fortinet')
yearintegerFilter by CVE year (e.g. 2024)

No output schema declared.

No examples provided.

Common questions

What is the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server?

Exploit Intelligence Platform — CVE, Vulnerability and… is an MCP server listed in the public MCP registry as com.exploit-intel/eip-mcp. Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs). This page covers its hosted endpoint (https://mcp.exploit-intel.com/mcp).

Is the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server safe to use?

Exploit Intelligence Platform — CVE, Vulnerability and… scores 0 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server expose?

Exploit Intelligence Platform — CVE, Vulnerability and… exposes 17 tools: search_vulnerabilities, get_vulnerability, get_exploit_code, get_exploit_analysis, get_nuclei_templates, and 12 more. Their descriptions and schemas cost roughly 2,792 tokens of context every time the server is loaded.

Does the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server require authentication?

Its publisher declares no required credentials for Exploit Intelligence Platform — CVE, Vulnerability and…. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.

Is the Exploit Intelligence Platform — CVE, Vulnerability and… MCP server still maintained?

Exploit Intelligence Platform — CVE, Vulnerability and… has been unreachable for long enough that we treat it as dead, and its score is pinned to zero. We last reached this channel on 14 August 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.