app.vercel.exploitwatch-kappa/exploitwatch vs io.github.mrfentmen/epss-mcp
app.vercel.exploitwatch-kappa/exploitwatch is an MCP server published by exploitwatch-kappa.vercel.app. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  io.github.mrfentmen/epss-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 No figure published 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 |
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 | app.vercel.exploitwatch-kappa/exploitwatch | io.github.mrfentmen/epss-mcp |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release (differs) | Not published | 2026-11-08 |
| Where it runs (differs) | Remote server (exploitwatch-kappa.vercel.app/api/mcp) | On your machine (@mrfentmen/epss-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | 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) | Responded 29 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
app.vercel.exploitwatch-kappa/exploitwatch
Check dependencies against CISA's real Known Exploited Vulnerabilities feed.
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
app.vercel.exploitwatch-kappa/exploitwatch As a remote MCP server
claude mcp add --transport http exploitwatch https://exploitwatch-kappa.vercel.app/api/mcpio.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 app.vercel.exploitwatch-kappa/exploitwatch 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
Neither one's marketplaces publish the settings it asks for.
What it can do: app.vercel.exploitwatch-kappa/exploitwatch · 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. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.