eip-mcp
The official MCP server for the Exploit Intelligence Platform.
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/mcp
In 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 --version
Then 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-mcp
For 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.
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
- User guide and tool reference
- Self-hosting the HTTP transport
- Contributing
- Security policy
- EIP command-line client
License
1 maintainer
Metadata
1 maintainer
Release files for eip-mcp 3.0.3
For a detailed explanation of source distributions (sdists) and built distributions (wheels), please see the package formats documentation.
Source distribution (sdist)
| File | Size | Uploaded | |
|---|---|---|---|
| eip_mcp-3.0.3.tar.gz | 545.1 kB | Details |
Built distribution (wheel)
| File | Interpreter | ABI | Platform | Reset |
|---|---|---|---|---|
| eip_mcp-3.0.3-py3-none-any.whl | Python 3 | none | any | Details |
Total release size: 668.8 kB
Release files / eip_mcp-3.0.3.tar.gz
| Download URL | eip_mcp-3.0.3.tar.gz |
|---|---|
| Size | 545.1 kB |
| Tags | Source |
|
SHA-256 checksum How to use checksums |
2f5c8dd593da6825f04122567245492e94319babd55928de05f041145ba69049
|
|
BLAKE2b-256 checksum How to use checksums |
2edf79841cc6a8711ede8823fa81f6caa5f47c5a0b18d28fad469b405238c9ce
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency logRelease files / eip_mcp-3.0.3-py3-none-any.whl
| Download URL | eip_mcp-3.0.3-py3-none-any.whl |
|---|---|
| Size | 123.8 kB |
| Tags | Python 3 |
|
SHA-256 checksum How to use checksums |
2fb762023be4443151ba4c0f7ba81c2ba014d323fcd40b31ec277a23e2e98e07
|
|
BLAKE2b-256 checksum How to use checksums |
458fa4f99c9d3521ac60787907338a3dd0b1a150581d665bbb20541c7186eb1d
|
| Upload date | |
|
Uploaded using Trusted Publishing? What is trusted publishing? |
Yes |
| Uploaded via |
twine/6.1.0 CPython/3.13.13
|
Provenance
Provenance describes where a file came from. On PyPI, provenance is shared via attestations, which provide a verifiable record of the build or publishing details. View details, limitations and caveats.
PyPI Publish Attestation
PyPI verified that this artifact, at this checksum, originated from the publisher listed below.
Signed by GitHub Actions, verified by PyPI on Oct 6, 2026.
Transparency log
