Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database
com.exploit-intelPublished by exploit-intel.comOfficial publisherv0.3.9Updated Oct 24, 2026
Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)
Overview
Gives an AI assistant real-time CVE, exploit and vulnerability intelligence from a database of 350K+ CVEs and 115K+ proof-of-concept exploits.
- What you can do
- Look up CVE and vulnerability intelligence in real time
- Find known exploits and proof-of-concept code tied to vulnerabilities
- Query a large vulnerability database covering 350K+ CVEs and 115K+ PoCs
- Use it from a remote endpoint or as a local stdio process
- When to use it
- Useful when an assistant needs to check whether a CVE is known, whether an exploit or PoC exists, or to add vulnerability context to security triage, dependency review or patch prioritization.
- Requirements
- Works as a remote streamable HTTP endpoint or as a local PyPI package (eip-mcp) over stdio, so a Python runtime is needed for local use. No authentication is required; an optional EIP_API_KEY can be supplied for higher rate limits. Network access to the service is needed.
Installation
In SourceWeft
- Open Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.
Use with an agent
Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.
Read https://sourceweft.com/mcp/com.exploit-intel%2Feip-mcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.Other MCP clients
Add this to your client's mcpServers config.
{
"mcpServers": {
"exploit-intelligence-platform-cve-vulner": {
"type": "http",
"url": "https://mcp.exploit-intel.com/mcp"
}
}
}Tools
0Version history
1- v0.3.9LatestSep 16, 2026
Score
25% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 daysRequired25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declaredRequired10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.
- License10 pts
Declare a license in the repository or the registry entry.