Scrapezy vs Browser Data Capture
Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). Browser Data Capture is a plugin bundle for AI coding tools published by danielrosehill. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-24. 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 |  Scrapezy |  Browser Data Capture |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:7a19e9b36500 Forks (GitHub): 8 Pulls (Docker Hub): 41 142 Stars (Docker Hub): 3 Stars (GitHub): 14 Not marked · First seen |
Not listed |
| Community marketplace danielrosehill/claude-code-plugins | Not listed | Listed Version: 1.0.1 Forks (GitHub): 0 Stars (GitHub): 1 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 | Scrapezy | Browser Data Capture |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 14 (better) | 1 (worse) |
| Pulls (Docker Hub) (differs) | 41 142 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 8 (better) | 0 (worse) |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | On your machine (mcp/scrapezy) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| Tools it declares (differs) | 1 | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 1 | Not published |
| Parts of the bundle (differs) | Not a bundle | 8 |
| Licence | MIT | MIT |
| Repository (differs) | github.com/scrapezy/mcp | github.com/danielrosehill/claude-browser-data-capture-plugin |
| Changes in the last 7 days (differs) | 0 | 1 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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
Scrapezy
A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.
Browser Data Capture
Streamline programmatic data ingestion against sites and apps that don't ship a documented API — capture network traffic (HAR, mitmproxy, or live tab via claude-in-chrome), map endpoints, infer schemas, and produce a draft OpenAPI spec you can build a stable client against. Ships skills for per-domain map documents, version-controlled storage in a private GitHub repo, and good-faith vulnerability disclosure if a finding turns up incidentally. White-hat use only.
How to run each
Scrapezy As a local MCP server: Docker image
claude mcp add --env "SCRAPEZY_API_KEY=<YOUR_SCRAPEZY_API_KEY>" --transport stdio scrapezy -- docker run -i --rm -e SCRAPEZY_API_KEY mcp/scrapezyRequires: SCRAPEZY_API_KEY (secret)
Browser Data Capture As a Claude Code plugin
/plugin marketplace add danielrosehill/claude-code-plugins
/plugin install browser-data-capture@danielrosehillCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of Browser Data Capture publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Browser Data Capture publish no settings it asks for, so we do not compare settings.
What it can do: Scrapezy · What it can do: Browser Data Capture · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.