npm Registry MCP Server vs io.github.ofershap/npm-plus
npm Registry MCP Server is an MCP server published by YawLabs. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ofershap/npm-plus is an MCP server published by ofershap. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  npm Registry MCP Server |  io.github.ofershap/npm-plus |
|---|---|---|
| Official MCP Registry | Listed Version: 0.17.0 Downloads/month (npm): 1 077 Downloads/week (npm): 192 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 1.0.1 Downloads/month (npm): 180 Downloads/week (npm): 20 Forks (GitHub): 1 Stars (GitHub): 1 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 | npm Registry MCP Server | io.github.ofershap/npm-plus |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 2 (better) | 1 (worse) |
| Forks (GitHub) | 1 | 1 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (@yawlabs/npmjs-mcp) | On your machine (mcp-server-npm-plus) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/yawlabs/npmjs-mcp | github.com/ofershap/mcp-server-npm-plus |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-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
npm Registry MCP Server
npm registry MCP server — package intelligence, security audits, dependency analysis
io.github.ofershap/npm-plus
npm MCP — search packages, bundle sizes, vulnerabilities, compare downloads.
How to run each
npm Registry MCP Server As a local MCP server: npm package
claude mcp add --transport stdio npmjs-mcp -- npx -y @yawlabs/npmjs-mcpio.github.ofershap/npm-plus As a local MCP server: npm package
claude mcp add --transport stdio npm-plus -- npx -y mcp-server-npm-plusCommands 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
Neither one's marketplaces publish the settings it asks for.
What it can do: npm Registry MCP Server · What it can do: io.github.ofershap/npm-plus · 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.