Ext Ops Panel
Open dashboard
Comparison

Puppeteer (Archived) vs io.github.AceDataCloud/mcp-webextrator

Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.AceDataCloud/mcp-webextrator is an MCP server published by AceDataCloud. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-23. 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)io.github.AceDataCloud/mcp-webextrator
Docker MCP Catalog Listed
Version: sha256:c1e2bda6d92d
Forks (GitHub): 11 846
Pulls (Docker Hub): 291 119
Stars (Docker Hub): 33
Stars (GitHub): 91 505
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 2026.10.18.0
Downloads/month (PyPI): 862
Downloads/week (PyPI): 783
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 io.github.AceDataCloud/mcp-webextrator
FactPuppeteer (Archived)io.github.AceDataCloud/mcp-webextrator
Marketplaces that list it11
Stars (GitHub) (differs)91 505No figure on GitHub
Pulls (Docker Hub) (differs)291 119No figure on Docker Hub
Forks (GitHub) (differs)11 846No figure on GitHub
Last release (differs)Not published2026-10-18
Where it runs (differs)On your machine (mcp/puppeteer)Remote server (webextrator.mcp.acedata.cloud/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)7Not published
Environment variables it asks for (differs)1, secrets among them: 01, secrets among them: 1
Licence (differs)NOASSERTIONNot stated
Repository (differs)github.com/modelcontextprotocol/serversgithub.com/acedatacloud/webextratermcp
Changes in the last 7 days (differs)01
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 4 days ago, requires a key

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.

io.github.AceDataCloud/mcp-webextrator

In its own words, on Official MCP Registry:

MCP server for web extraction and rendering via AceDataCloud WebExtrator

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

io.github.AceDataCloud/mcp-webextrator As a remote MCP server

Claude Code
claude mcp add --transport http mcp-webextrator https://webextrator.mcp.acedata.cloud/mcp

Requires: ACEDATACLOUD_API_TOKEN (secret)

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

Only io.github.AceDataCloud/mcp-webextrator has a remote endpoint we check. How we check endpoints

Tools each declares

The marketplaces of io.github.AceDataCloud/mcp-webextrator publish no list of tools, so we do not compare tools.

Settings each asks for

Only Puppeteer (Archived) asks for

  • DOCKER_CONTAINER

Only io.github.AceDataCloud/mcp-webextrator asks for

  • ACEDATACLOUD_API_TOKEN (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Puppeteer (Archived) · What it can do: io.github.AceDataCloud/mcp-webextrator · 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