Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database vs io.github.mrfentmen/epss-mcp
Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database is an MCP server published by exploit-intel.com. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). io.github.mrfentmen/epss-mcp is an MCP server published by mrfentmen. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-09. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.
Where each is published
| Marketplace |  Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database |  io.github.mrfentmen/epss-mcp |
|---|---|---|
| Official MCP Registry | Listed Version: 0.3.9 Downloads/month (PyPI): 489 Downloads/week (PyPI): 71 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 697 Downloads/week (npm): 133 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 3.0.4 Downloads/month (PyPI): 489 Downloads/week (PyPI): 71 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database | io.github.mrfentmen/epss-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release (differs) | 2026-10-29 (worse) | 2026-11-08 (better) |
| Where it runs (differs) | Remote server or your machine | On your machine (@mrfentmen/epss-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/exploitintel/eip-mcp | github.com/mrfentmen/awesome-servers |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-27 |
| Endpoint at the last check (differs) | Status out of date: no HTTP response at the last check 47 h ago | no remote endpoint we check |
Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.
What each says it does
Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database
Real-time CVE, exploit, and vulnerability intelligence for AI assistants (350K+ CVEs, 115K+ PoCs)
io.github.mrfentmen/epss-mcp
Exploit Prediction Scoring System scores: how likely a CVE will be exploited in the next 30 days.
How to run each
Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database As a remote MCP server
claude mcp add --transport http eip-mcp https://mcp.exploit-intel.com/mcpRequires: EIP_API_KEY (secret)
io.github.mrfentmen/epss-mcp As a local MCP server: npm package
claude mcp add --transport stdio epss-mcp -- npx -y @mrfentmen/epss-mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of io.github.mrfentmen/epss-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Exploit Intelligence Platform — CVE, Vulnerability and Exploit Database · What it can do: io.github.mrfentmen/epss-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.