contextweave-mcp vs io.github.Nekzus/npm-sentinel-mcp
contextweave-mcp is an MCP server published by matthew-brough. Marketplaces we read that list it: 1 (PyPI (MCP servers)). 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-11-15. 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 |  contextweave-mcp |  io.github.Nekzus/npm-sentinel-mcp |
|---|---|---|
| PyPI (MCP servers) | Listed Version: 0.6.5 Downloads/month (PyPI): 0 Downloads/week (PyPI): 184 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.26.1 Downloads/month (npm): 1 875 Downloads/week (npm): 498 Forks (GitHub): 10 Stars (GitHub): 18 Not marked · First seen |
| Docker MCP Catalog | Not listed | Listed Version: sha256:d8e4bbc7dd5c Forks (GitHub): 10 Pulls (Docker Hub): 62 061 Stars (Docker Hub): 1 Stars (GitHub): 18 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.26.1 Downloads/month (npm): 1 875 Downloads/week (npm): 498 Forks (GitHub): 10 Stars (GitHub): 18 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 | contextweave-mcp | io.github.Nekzus/npm-sentinel-mcp |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 3 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 18 (better) |
| Pulls (Docker Hub) (differs) | No figure on Docker Hub | 62 061 |
| Forks (GitHub) (differs) | 0 (worse) | 10 (better) |
| Last release (differs) | 2026-11-05 | Not published |
| Where it runs (differs) | On your machine (contextweave-mcp) | Remote server or your machine |
| Transport (differs) | Not stated | stdio, Streamable HTTP |
| Tools it declares (differs) | Not published | 19 |
| Environment variables it asks for | Not published | Not published |
| Licence (differs) | MPL-2.0 | MIT |
| Repository (differs) | github.com/matthew-brough/contextweave | github.com/nekzus/npm-sentinel-mcp |
| Changes in the last 7 days (differs) | 1 | 0 |
| First seen (differs) | 2026-10-14 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 16 h ago, requires authentication |
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
contextweave-mcp
Unified code-context MCP server: structural, lexical and semantic retrieval
io.github.Nekzus/npm-sentinel-mcp
Advanced NPM analysis: Recursive security scanning, ecosystem awareness, and deep insights.
How to run each
contextweave-mcp
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
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 io.github.Nekzus/npm-sentinel-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of contextweave-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: contextweave-mcp · What it can do: io.github.Nekzus/npm-sentinel-mcp · Compare two other plugins
Package data comes from the Python Package Index (pypi.org). 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.