Execute codevulnerability-mcp vs io.github.Nekzus/npm-sentinel-mcp
Execute codevulnerability-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.Nekzus/npm-sentinel-mcp is an MCP server published by Nekzus. Marketplaces we read that list it: 3 (Official MCP Registry, Docker MCP Catalog, npm registry (MCP servers)). As of our marketplace pass on 2026-10-28. 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.Nekzus/npm-sentinel-mcp | |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 No figure published Not marked · First seen |
Listed Version: 1.26.1 Downloads/month (npm): 1 487 Downloads/week (npm): 309 Forks (GitHub): 10 Stars (GitHub): 19 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:d8e4bbc7dd5c Forks (GitHub): 10 Pulls (Docker Hub): 61 271 Stars (Docker Hub): 1 Stars (GitHub): 19 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.26.1 Downloads/month (npm): 1 487 Downloads/week (npm): 309 Forks (GitHub): 10 Stars (GitHub): 19 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 | Execute codevulnerability-mcp | io.github.Nekzus/npm-sentinel-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | No figure on GitHub | 19 |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 61 271 |
| Forks (GitHub) (differs) | No figure on GitHub | 10 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.m2mcent.com/codevulnerability-mcp/sse) | Remote server or your machine |
| Transport (differs) | SSE | stdio, Streamable HTTP |
| Tools it declares (differs) | Not published | 19 |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | Not stated | github.com/nekzus/npm-sentinel-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Answered with HTTP 402 (30 h ago) | Responded 5 days ago, requires a key |
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
Execute codevulnerability-mcp
Premium agentic endpoint for codevulnerability-mcp.
io.github.Nekzus/npm-sentinel-mcp
Advanced NPM analysis: Recursive security scanning, ecosystem awareness, and deep insights.
How to run each
Execute codevulnerability-mcp As a remote MCP server
claude mcp add --transport sse codevulnerability-mcp https://api.m2mcent.com/codevulnerability-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
io.github.Nekzus/npm-sentinel-mcp As a local MCP server: npm package
claude mcp add --transport stdio npm-sentinel-mcp -- npx -y @nekzus/mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only the endpoint of io.github.Nekzus/npm-sentinel-mcp responded at the last daily check. How we check endpoints
Tools each declares
The marketplaces of Execute codevulnerability-mcp publish no list of tools, so we do not compare tools.
Settings each asks for
Neither one's marketplaces publish the settings it asks for.
What it can do: Execute codevulnerability-mcp · What it can do: io.github.Nekzus/npm-sentinel-mcp · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.