Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs walkerOS Source Browser

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). walkerOS Source Browser is an MCP server published by walkeros.io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplacePuppeteer (Archived)walkerOS Source Browser
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 790
Pulls (Docker Hub): 284 530
Stars (Docker Hub): 33
Stars (GitHub): 91 268
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 4.5.0
Downloads/month (npm): 2 541
Downloads/week (npm): 862
Forks (GitHub): 23
Stars (GitHub): 347
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

Puppeteer (Archived) vs walkerOS Source Browser
FactPuppeteer (Archived)walkerOS Source Browser
Marketplaces that list it11
Stars (GitHub) (differs)91 268 (better)347 (worse)
Pulls (Docker Hub) (differs)284 530No figure on Docker Hub
Forks (GitHub) (differs)11 790 (better)23 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/puppeteer)On your machine (@walkeros/mcp-source-browser)
Transportstdiostdio
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 0Not published
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/elbwalker/walkeros
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

Puppeteer (Archived)

In its own words, on Docker MCP Catalog:

Browser automation and web scraping using Puppeteer.

walkerOS Source Browser

In its own words, on Official MCP Registry:

Generate, parse, and validate walkerOS data-elb HTML tagging attributes

How to run each

Puppeteer (Archived) As a local MCP server: Docker image

Claude Code
claude mcp add --transport stdio puppeteer -- docker run -i --rm mcp/puppeteer

walkerOS Source Browser As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio source-browser -- npx -y @walkeros/mcp-source-browser

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

Tools each declares

The marketplaces of walkerOS Source Browser publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of walkerOS Source Browser publish no settings it asks for, so we do not compare settings.

What it can do: Puppeteer (Archived) · What it can do: walkerOS Source Browser · 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