npm Registry MCP Server vs toolprint by JEStats
npm Registry MCP Server is an MCP server published by YawLabs. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). toolprint by JEStats is an MCP server published by jestatsio. 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
| Marketplace |  npm Registry MCP Server |  toolprint by JEStats |
|---|---|---|
| Official MCP Registry | Listed Version: 0.17.0 Downloads/month (npm): 933 Downloads/week (npm): 105 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Listed Version: 0.4.1 Downloads/month (npm): 220 Downloads/week (npm): 109 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 0.17.0 Downloads/month (npm): 933 Downloads/week (npm): 105 Forks (GitHub): 1 Stars (GitHub): 2 Not marked · First seen |
Not listed |
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 | toolprint by JEStats |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 2 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 1 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | On your machine (@yawlabs/npmjs-mcp) | On your machine (toolprint) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/yawlabs/npmjs-mcp | github.com/jestatsio/toolprint |
| Changes in the last 7 days | 0 | 0 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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
toolprint by JEStats
package-lock.json for MCP trust: catch MCP rug-pulls, tool poisoning, and leaked secrets.
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-mcptoolprint by JEStats As a local MCP server: npm package
claude mcp add --env "TOOLPRINT_BEARER=<YOUR_TOOLPRINT_BEARER>" --transport stdio toolprint -- npx -y toolprint serveRequires: TOOLPRINT_BEARER (secret)
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
The marketplaces of npm Registry MCP Server publish no settings it asks for, so we do not compare settings.
What it can do: npm Registry MCP Server · What it can do: toolprint by JEStats · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. 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.