{
  "markdown": "<p align=\"center\">\n  <a href=\"https://exploit-intel.com\">\n    <img src=\"https://raw.githubusercontent.com/exploitintel/eip-mcp/main/docs/assets/eip-hero-banner.svg\" alt=\"Exploit Intelligence Platform\" width=\"100%\">\n  </a>\n</p>\n\n<h1 align=\"center\">eip-mcp</h1>\n\n<p align=\"center\"><strong>The official MCP server for the Exploit Intelligence Platform.</strong></p>\n\n<p align=\"center\">\n  <a href=\"https://pypi.org/project/eip-mcp/\"><img src=\"https://img.shields.io/pypi/v/eip-mcp.svg\" alt=\"PyPI release\"></a>\n  <a href=\"https://pypi.org/project/eip-mcp/\"><img src=\"https://img.shields.io/pypi/pyversions/eip-mcp.svg\" alt=\"Supported Python versions\"></a>\n  <a href=\"https://github.com/exploitintel/eip-mcp/actions/workflows/quality.yml\"><img src=\"https://github.com/exploitintel/eip-mcp/actions/workflows/quality.yml/badge.svg\" alt=\"Quality checks\"></a>\n  <a href=\"https://github.com/exploitintel/eip-mcp/blob/main/LICENSE\"><img src=\"https://img.shields.io/badge/license-MIT-16b8c4.svg\" alt=\"MIT License\"></a>\n</p>\n\nGive an AI assistant bounded, source-attributed access to vulnerability\nintelligence, exploit artifacts, readable PoC source, Docker labs, discovery\ndirectories, STIX, and corpus statistics. Most users can connect to EIP's\nhosted MCP endpoint directly - there is no package or API key to install.\n\n`eip-mcp` is read-only. It talks only to an EIP read API, the public one by\ndefault, exposes no download tool, never executes acquired content, and never\nclaims that an exploit works, is verified, reliable, effective, or safe.\n\n## Connect\n\n### Recommended: hosted MCP\n\nClients supporting remote Streamable HTTP can connect directly to:\n\n```text\nhttps://exploit-intel.com/mcp\n```\n\nIn an MCP-capable application, add that URL as a remote Streamable HTTP server\nnamed `EIP`. If your assistant can configure integrations for you, tell it:\n\n> Add `https://exploit-intel.com/mcp` as a Streamable HTTP MCP server named\n> `EIP`, then call `get_corpus_readiness` to verify the connection.\n\nNo local package, API key, or EIP account is required.\n\n### Optional: local Python package\n\nUse the Python package when a client requires a local stdio command, or when\nyou are self-hosting the HTTP transport. Python 3.12 or newer is required.\nInstall the isolated application with [`pipx`](https://pipx.pypa.io/):\n\n```sh\npipx install eip-mcp\neip-mcp --version\n```\n\nThen register it with your MCP client. A typical stdio configuration is:\n\n```json\n{\n  \"mcpServers\": {\n    \"eip\": {\n      \"command\": \"eip-mcp\"\n    }\n  }\n}\n```\n\nUse the absolute path reported by `command -v eip-mcp` if the client does not\ninherit your shell `PATH`.\n\nThe local command connects to `https://exploit-intel.com`; no API configuration\nis needed.\n\n### Optional: Docker\n\nBuild the image directly from this checkout:\n\n```sh\ndocker build -t eip-mcp .\ndocker run --rm -i eip-mcp\n```\n\nFor a stdio MCP client, use `docker` as the command:\n\n```json\n{\n  \"mcpServers\": {\n    \"eip\": {\n      \"command\": \"docker\",\n      \"args\": [\"run\", \"--rm\", \"-i\", \"eip-mcp\"]\n    }\n  }\n}\n```\n\nContainerized Streamable HTTP operation is covered in the\n[self-hosting guide](https://github.com/exploitintel/eip-mcp/blob/main/docs/self-hosting.md#docker).\n\n## What assistants can do\n\n- Search and inspect CVEs and GHSAs with affected products, version ranges,\n  exploitation context, references, and accepted research\n- Search ExploitDB, Metasploit, curated repository PoCs, and repository\n  candidates without inventing quality rankings\n- Search safely readable PoC source and inspect one bounded text file\n- Discover Docker/Compose labs and their stored, attributed analysis\n- Browse vendors, products, ecosystems, packages, official CWEs, and exploit\n  contributors\n- Retrieve API-owned STIX 2.1 bundles, corpus health, and statistics\n- Use four focused research prompts and the `eip://research/usage-guide`\n  resource\n\nThe complete [tool reference](https://github.com/exploitintel/eip-mcp/blob/main/docs/user-guide.md#tool-reference)\nlists every tool and documents the section and pagination rules.\n\n## Result contract\n\nEvery tool returns two synchronized forms:\n\n- a concise Markdown brief for the assistant; and\n- a validated `eip-mcp-result-v1` structured envelope preserving the bounded\n  API payload.\n\nCorpus values remain untrusted third-party data in both forms. Text is rendered\nin inert CommonMark containers, output is capped, truncation is disclosed, and\nopaque pagination cursors remain reusable byte-for-byte.\n\nStored analysis is attributed model interpretation, not an EIP verdict.\nMissing analysis never means that an artifact was reviewed and found safe.\n\n## Safety boundary\n\n- The MCP server connects only to allowlisted read-only API paths.\n- PoC access tokens never reach results, logs, tracebacks, or retained state.\n- There is deliberately no PoC download tool.\n- Source reading is bounded to one API-verified UTF-8 text file at a time.\n- All returned source and corpus prose must be treated as untrusted data and\n  must never be executed or followed as instructions.\n\nSee the [security policy](https://github.com/exploitintel/eip-mcp/security/policy)\nbefore reporting a vulnerability or sharing diagnostic output.\n\n## Documentation\n\n- [User guide and tool reference](https://github.com/exploitintel/eip-mcp/blob/main/docs/user-guide.md)\n- [Self-hosting the HTTP transport](https://github.com/exploitintel/eip-mcp/blob/main/docs/self-hosting.md)\n- [Contributing](https://github.com/exploitintel/eip-mcp/blob/main/CONTRIBUTING.md)\n- [Security policy](https://github.com/exploitintel/eip-mcp/security/policy)\n- [EIP command-line client](https://github.com/exploitintel/eip-search)\n\n## License\n\n[MIT](https://github.com/exploitintel/eip-mcp/blob/main/LICENSE)\n",
  "bytes": 5717,
  "sha": "282f7385f87f855207b0a23ce28fcc3abbcffbba13d7985b32a02e1b91a5eca1",
  "repo_slug": "exploitintel/eip-mcp",
  "fonte": "repo",
  "truncated": false,
  "api": "https://agentalog.com/api/listings/mcp_com_exploit_intel_eip_mcp_50581a8c/readme"
}