Ext Ops Panel
Open dashboard
Comparison

Scrapezy vs io.github.robertoyanguas-ops/agentdiet

Scrapezy is an MCP server published by Scrapezy. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.robertoyanguas-ops/agentdiet is an MCP server published by robertoyanguas-ops. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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
MarketplaceScrapezyio.github.robertoyanguas-ops/agentdiet
Docker MCP Catalog Listed
Version: sha256:7a19e9b36500
Forks (GitHub): 7
Pulls (Docker Hub): 40 884
Stars (Docker Hub): 3
Stars (GitHub): 14
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.1.1
No figure published
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 io.github.robertoyanguas-ops/agentdiet
FactScrapezyio.github.robertoyanguas-ops/agentdiet
Marketplaces that list it11
Stars (GitHub) (differs)14No figure on GitHub
Pulls (Docker Hub) (differs)40 884No figure on Docker Hub
Forks (GitHub) (differs)7No figure on GitHub
Last release (differs)Not published2026-10-13
Where it runs (differs)On your machine (mcp/scrapezy)Remote server (agentdiet-72343955726.us-central1.run.app/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declares (differs)1Not published
Environment variables it asks for (differs)1, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/scrapezy/mcpNot stated
Changes in the last 7 days (differs)04
First seen (differs)2026-10-112026-10-13
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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.

io.github.robertoyanguas-ops/agentdiet

In its own words, on Official MCP Registry:

Strips 85-97% of HTML bloat into clean Markdown, <200-token skeletons, or BM25 excerpts via MCP.

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)

io.github.robertoyanguas-ops/agentdiet As a remote MCP server

Claude Code
claude mcp add --transport http agentdiet https://agentdiet-72343955726.us-central1.run.app/mcp

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

Tools each declares

The marketplaces of io.github.robertoyanguas-ops/agentdiet publish no list of tools, so we do not compare tools.

Settings each asks for

The marketplaces of io.github.robertoyanguas-ops/agentdiet publish no settings it asks for, so we do not compare settings.

What it can do: Scrapezy · What it can do: io.github.robertoyanguas-ops/agentdiet · 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