Ext Ops Panel
Open dashboard
Comparison

mcp-email-server vs io.github.Nekzus/npm-sentinel-mcp

mcp-email-server is an MCP server published by Wh1isper. 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-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

Where each is published
Marketplacemcp-email-serverio.github.Nekzus/npm-sentinel-mcp
PyPI (MCP servers) Listed
Version: 1.14.0
Downloads/month (PyPI): 14 158
Downloads/week (PyPI): 4 010
Forks (GitHub): 137
Stars (GitHub): 386
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.26.1
Downloads/month (npm): 1 487
Downloads/week (npm): 309
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): 61 785
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 487
Downloads/week (npm): 309
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

mcp-email-server vs io.github.Nekzus/npm-sentinel-mcp
Factmcp-email-serverio.github.Nekzus/npm-sentinel-mcp
Marketplaces that list it (differs)1 (worse)3 (better)
Stars (GitHub) (differs)386 (better)18 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub61 785
Forks (GitHub) (differs)137 (better)10 (worse)
Last release (differs)2026-11-03Not published
Where it runs (differs)On your machine (mcp-email-server)Remote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declares (differs)Not published19
Environment variables it asks forNot publishedNot published
Licence (differs)Not statedMIT
Repository (differs)github.com/wh1isper/mcp-email-servergithub.com/nekzus/npm-sentinel-mcp
Changes in the last 7 days (differs)10
First seen (differs)2026-10-122026-10-11
Endpoint at the last check (differs)no remote endpoint we checkStatus out of date: last check 37 h ago returned HTTP 401

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

mcp-email-server

In its own words, on PyPI (MCP servers):

Full-featured, multi-account MCP email server for Windows, macOS, and Linux—read, search, organize, and send email via IMAP and SMTP.

io.github.Nekzus/npm-sentinel-mcp

In its own words, on Official MCP Registry:

Advanced NPM analysis: Recursive security scanning, ecosystem awareness, and deep insights.

How to run each

mcp-email-server

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 Code
claude mcp add --transport stdio npm-sentinel-mcp -- npx -y @nekzus/mcp-server

Commands 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 mcp-email-server 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: mcp-email-server · 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.

Where the data comes from: how the catalog is built