Ext Ops Panel
Open dashboard
Comparison

token-optimizer vs io.github.Nekzus/npm-sentinel-mcp

token-optimizer is a plugin bundle for AI coding tools published by ooples. Marketplaces we read that list it: 1 (Community GitHub marketplaces). io.github.Nekzus/npm-sentinel-mcp is an MCP server published by Nekzus. Marketplaces we read that list it: 2 (Official MCP Registry, Docker MCP Catalog). As of our marketplace pass on 2026-10-17. 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
Marketplacetoken-optimizerio.github.Nekzus/npm-sentinel-mcp
Community marketplace ooples/token-optimizer-mcp Listed
Version: 7.5.1
Forks (GitHub): 69
Stars (GitHub): 550
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.26.1
Downloads/month (npm): 2 733
Downloads/week (npm): 869
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): 60 791
Stars (Docker Hub): 1
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

token-optimizer vs io.github.Nekzus/npm-sentinel-mcp
Facttoken-optimizerio.github.Nekzus/npm-sentinel-mcp
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)550 (better)18 (worse)
Pulls (Docker Hub) (differs)No figure on Docker Hub60 791
Forks (GitHub) (differs)69 (better)10 (worse)
Last release (differs)2026-10-15Not published
Where it runs (differs)Installs as a plugin bundleRemote server or your machine
Transport (differs)Not statedstdio, Streamable HTTP
Tools it declares (differs)Not published19
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)6Not published
Parts of the bundle (differs)7Not a bundle
LicenceMITMIT
Repository (differs)github.com/ooples/token-optimizer-mcpgithub.com/nekzus/npm-sentinel-mcp
Changes in the last 7 days (differs)30
First seen (differs)2026-10-142026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 18 h 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

token-optimizer

In its own words, on Community GitHub marketplaces:

Context-window optimization (caching, compression, smart file tooling) as an MCP server + usage skill + auto-optimization hooks.

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

token-optimizer As a Claude Code plugin

Claude Code
/plugin marketplace add ooples/token-optimizer-mcp
/plugin install token-optimizer@token-optimizer

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 token-optimizer 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: token-optimizer · What it can do: io.github.Nekzus/npm-sentinel-mcp · Compare two other plugins

Data comes from public marketplace files in GitHub repositories of their authors. 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. 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