Ext Ops Panel
Open dashboard
Comparison

Node.js Sandbox vs Npm Package Info Mcp

Node.js Sandbox is an MCP server published by alfonsograziano. Marketplaces we read that list it: 1 (Docker MCP Catalog). Npm Package Info Mcp is an MCP server published by varvararatta. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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
MarketplaceNode.js SandboxNpm Package Info Mcp
Docker MCP Catalog Listed
Version: sha256:e8cbb5c3ae86
Forks (GitHub): 34
Pulls (Docker Hub): 156 732
Stars (Docker Hub): 6
Stars (GitHub): 158
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.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

Node.js Sandbox vs Npm Package Info Mcp
FactNode.js SandboxNpm Package Info Mcp
Marketplaces that list it11
Stars (GitHub) (differs)158 (better)0 (worse)
Pulls (Docker Hub) (differs)156 732No figure on Docker Hub
Forks (GitHub) (differs)34 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/node-code-sandbox)Remote server (npm-package-info-mcp.mcpize.run/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/alfonsograziano/node-code-sandbox-mcpgithub.com/varvararatta/botfactory-mcp
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkNot responding since 2026-10-13

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

Node.js Sandbox

In its own words, on Docker MCP Catalog:

A Node.js–based Model Context Protocol server that spins up disposable Docker containers to execute arbitrary JavaScript.

Npm Package Info Mcp

In its own words, on Official MCP Registry:

Dive into the world of npm with our NPM Package Info MCP. Access crucial metadata about any npm

How to run each

Node.js Sandbox As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio node-code-sandbox -- docker run -i --rm mcp/node-code-sandbox

Npm Package Info Mcp As a remote MCP server

Claude Code
claude mcp add --transport http npm-package-info-mcp https://npm-package-info-mcp.mcpize.run/mcp

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

Only Npm Package Info Mcp has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of Npm Package Info Mcp 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: Node.js Sandbox · What it can do: Npm Package Info Mcp · Compare two other plugins

Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. 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