Puppeteer (Archived) vs io.github.DataLeadsPRO/web-scraper
Puppeteer (Archived) is an MCP server published by modelcontextprotocol. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.DataLeadsPRO/web-scraper is an MCP server published by DataLeadsPRO. 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
| Marketplace |   Puppeteer (Archived) |  io.github.DataLeadsPRO/web-scraper |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:c1e2bda6d92d Forks (GitHub): 11 787 Pulls (Docker Hub): 283 710 Stars (Docker Hub): 33 Stars (GitHub): 91 222 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.1 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
| Fact | Puppeteer (Archived) | io.github.DataLeadsPRO/web-scraper |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 91 222 (better) | 0 (worse) |
| Pulls (Docker Hub) (differs) | 283 710 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 11 787 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/puppeteer) | Remote server (data.dataleads.pro/mcp/web-scraper) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 7 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | Not published |
| Licence (differs) | NOASSERTION | Not stated |
| Repository (differs) | github.com/modelcontextprotocol/servers | github.com/dataleadspro/web-scraper |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Not 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
Puppeteer (Archived)
Browser automation and web scraping using Puppeteer.
io.github.DataLeadsPRO/web-scraper
Fetch, crawl, and browse protected pages with anti-bot handling - renders in a real browser and
How to run each
Puppeteer (Archived) As a local MCP server: Docker image
claude mcp add --transport stdio puppeteer -- docker run -i --rm mcp/puppeteerio.github.DataLeadsPRO/web-scraper As a remote MCP server
claude mcp add --transport http web-scraper https://data.dataleads.pro/mcp/web-scraperCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.DataLeadsPRO/web-scraper has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.DataLeadsPRO/web-scraper publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.DataLeadsPRO/web-scraper publish no settings it asks for, so we do not compare settings.
What it can do: Puppeteer (Archived) · What it can do: io.github.DataLeadsPRO/web-scraper · 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.