Ext Ops Panel
Open dashboard
Comparison

proxy-scraper vs Scrapingant

proxy-scraper is an MCP server published by maximilianfeix. Marketplaces we read that list it: 1 (Official MCP Registry). Scrapingant is an MCP server published by pipeworx-io. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-27. 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
Marketplaceproxy-scraperScrapingant
Official MCP Registry Listed
Version: 1.31.0
Downloads/month (PyPI): 2 491
Downloads/week (PyPI): 504
Forks (GitHub): 14
Stars (GitHub): 74
Not marked · First seen
Listed
Version: 0.1.2
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

proxy-scraper vs Scrapingant
Factproxy-scraperScrapingant
Marketplaces that list it11
Stars (GitHub) (differs)74 (better)0 (worse)
Forks (GitHub) (differs)14 (better)0 (worse)
Last release (differs)2026-10-23Not published
Where it runs (differs)On your machine (proxy-scraper-cli)Remote server (gateway.pipeworx.io/scrapingant/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
LicenceNot statedNot stated
Repository (differs)github.com/maximilianfeix/proxy-scrapergithub.com/pipeworx-io/mcp-scrapingant
Changes in the last 7 days (differs)10
First seen2026-10-112026-10-11
Endpoint at the last check (differs)no remote endpoint we checkResponded 26 h ago

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

proxy-scraper

In its own words, on Official MCP Registry:

Free proxies that actually work: checked HTTP/SOCKS proxies, and pages fetched through them

Scrapingant

In its own words, on Official MCP Registry:

ScrapingAnt MCP — wraps the ScrapingAnt web scraping API (scrapingant.com)

How to run each

proxy-scraper As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio proxy-scraper -- uvx --python ">=3.10" --with "mcp>=2.2,<3" proxy-scraper-cli

Scrapingant As a remote MCP server

Claude Code
claude mcp add --transport http scrapingant https://gateway.pipeworx.io/scrapingant/mcp

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

Only Scrapingant has a remote endpoint we check. How we check endpoints

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: proxy-scraper · What it can do: Scrapingant · Compare two other plugins

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