Ext Ops Panel
Open dashboard
Comparison

io.github.mcp-protocol/node-runtime vs io.github.noahgift/pmcp

io.github.mcp-protocol/node-runtime is an MCP server published by mcp-protocol. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.noahgift/pmcp is an MCP server published by noahgift. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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.mcp-protocol/node-runtimeio.github.noahgift/pmcp
Official MCP Registry Listed
Version: 1.0.2
Downloads/month (npm): 139
Downloads/week (npm): 25
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
Listed
Version: 1.6.1
No figure published
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.mcp-protocol/node-runtime vs io.github.noahgift/pmcp
Factio.github.mcp-protocol/node-runtimeio.github.noahgift/pmcp
Marketplaces that list it11
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (@mcp-protocol/node-runtime)Not stated
Transport (differs)stdioNot stated
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/mcp-protocol/node-runtimegithub.com/noahgift/rust-mcp-sdk
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.mcp-protocol/node-runtime

In its own words, on Official MCP Registry:

This package is intended for demonstration only. Maintained by JFrog Security.

io.github.noahgift/pmcp

In its own words, on Official MCP Registry:

High-quality Rust SDK for Model Context Protocol (MCP) with full TypeScript SDK compatibility

How to run each

io.github.mcp-protocol/node-runtime As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio node-runtime -- npx -y @mcp-protocol/node-runtime

io.github.noahgift/pmcp

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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

Neither one's marketplaces publish the settings it asks for.

What it can do: io.github.mcp-protocol/node-runtime · What it can do: io.github.noahgift/pmcp · 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