Ext Ops Panel
Open dashboard
Comparison

io.github.mikusnuz/npm vs io.github.nimbus-agent/nimbus

io.github.mikusnuz/npm is an MCP server published by mikusnuz. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.nimbus-agent/nimbus is an MCP server published by nimbus-agent. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-30. 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
Marketplaceio.github.mikusnuz/npmio.github.nimbus-agent/nimbus
Official MCP Registry Listed
Version: 1.4.0
Downloads/month (npm): 215
Downloads/week (npm): 114
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 0.4.1
Downloads/month (npm): 362
Downloads/week (npm): 0
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

io.github.mikusnuz/npm vs io.github.nimbus-agent/nimbus
Factio.github.mikusnuz/npmio.github.nimbus-agent/nimbus
Marketplaces that list it11
Stars (GitHub) (differs)1 (better)0 (worse)
Forks (GitHub)00
Last release (differs)2026-10-19Not published
Where it runs (differs)On your machine (@mikusnuz/npm-mcp)On your machine (@nimbus-dev/mcp)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)1, secrets among them: 12, secrets among them: 0
LicenceNot statedNot stated
Repository (differs)github.com/mikusnuz/npm-mcpgithub.com/nimbus-agent/nimbus-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

io.github.mikusnuz/npm

In its own words, on Official MCP Registry:

MCP server for npm package management — publish, version, search, audit, and more

io.github.nimbus-agent/nimbus

In its own words, on Official MCP Registry:

Search your local Nimbus index and run its built-in agents from any MCP client.

How to run each

io.github.mikusnuz/npm As a local MCP server: npm package

Claude Code
claude mcp add --env "NPM_TOKEN=<YOUR_NPM_TOKEN>" --transport stdio npm -- npx -y @mikusnuz/npm-mcp

Requires: NPM_TOKEN (secret)

io.github.nimbus-agent/nimbus As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio nimbus -- npx -y @nimbus-dev/mcp

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Only io.github.mikusnuz/npm asks for

  • NPM_TOKEN (secret)

Only io.github.nimbus-agent/nimbus asks for

  • NIMBUS_BIN
  • NIMBUS_MCP_TIMEOUT_MS

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: io.github.mikusnuz/npm · What it can do: io.github.nimbus-agent/nimbus · 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.

Where the data comes from: how the catalog is built