Ext Ops Panel
Open dashboard
Comparison

Scrapezy vs universal-scraping-architect

Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). universal-scraping-architect is a plugin bundle for AI coding tools published by Mehansh Barthwal. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-26. 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
MarketplaceScrapezyuniversal-scraping-architect
Docker MCP Catalog Listed
Version: sha256:7a19e9b36500
Forks (GitHub): 8
Pulls (Docker Hub): 41 212
Stars (Docker Hub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Community marketplace alirezarezvani/claude-skills Not listed Listed
Version: 2.14.1
Forks (GitHub): 3 978
Stars (GitHub): 28 652
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

Scrapezy vs universal-scraping-architect
FactScrapezyuniversal-scraping-architect
Marketplaces that list it11
Stars (GitHub) (differs)14 (worse)28 652 (better)
Pulls (Docker Hub) (differs)41 212No figure on Docker Hub
Forks (GitHub) (differs)8 (worse)3 978 (better)
Last release (differs)Not published2026-10-23
Where it runs (differs)On your machine (mcp/scrapezy)Installs as a plugin bundle
Transport (differs)stdioNot stated
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Parts of the bundle (differs)Not a bundle3
LicenceMITMIT
Repository (differs)github.com/scrapezy/mcpgithub.com/alirezarezvani/claude-skills
Changes in the last 7 days (differs)01
First seen (differs)2026-10-112026-10-14

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

In its own words, on Docker MCP Catalog:

A Model Context Protocol server for Scrapezy that enables AI models to extract structured data from websites.

universal-scraping-architect

In its own words, on Community GitHub marketplaces:

A universal scraping skill with intelligent routing, token budget tracking, and quota awareness. Supports Firecrawl (BYOK, free-tier compatible) and local Python extraction via requests/BeautifulSoup/pandas.

How to run each

Scrapezy As a local MCP server: Docker image

Claude Code
claude mcp add --env "SCRAPEZY_API_KEY=<YOUR_SCRAPEZY_API_KEY>" --transport stdio scrapezy -- docker run -i --rm -e SCRAPEZY_API_KEY mcp/scrapezy

Requires: SCRAPEZY_API_KEY (secret)

universal-scraping-architect As a Claude Code plugin

Claude Code
/plugin marketplace add alirezarezvani/claude-skills
/plugin install universal-scraping-architect@claude-code-skills

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

Tools each declares

The marketplaces of universal-scraping-architect publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of universal-scraping-architect publish no settings it asks for, so we do not compare settings.

What it can do: Scrapezy · What it can do: universal-scraping-architect · 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.

Where the data comes from: how the catalog is built