Ext Ops Panel
Open dashboard
Comparison

zyte-web-data vs dev.fetchgate/fetchgate

zyte-web-data is a plugin bundle for AI coding tools published by zytedata. Marketplaces we read that list it: 2 (Claude Code: claude-plugins-official, Claude Code: claude-plugins-community). dev.fetchgate/fetchgate is an MCP server published by fetchgate.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-13. 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
Marketplacezyte-web-datadev.fetchgate/fetchgate
Claude Code: claude-plugins-official Listed
Version: 0.3.1
Forks (GitHub): 5
Stars (GitHub): 33
Not marked · First seen
Not listed
Claude Code: claude-plugins-community Listed
Version: 0.2.3
Forks (GitHub): 5
Stars (GitHub): 33
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
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

zyte-web-data vs dev.fetchgate/fetchgate
Factzyte-web-datadev.fetchgate/fetchgate
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)33No figure on GitHub
Forks (GitHub) (differs)5No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleRemote server (fetchgate.dev/mcp)
Transport (differs)Not statedStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)1Not published
Parts of the bundle (differs)15Not a bundle
LicenceNot statedNot stated
Repository (differs)github.com/zytedata/claude-skillsNot stated
Changes in the last 7 days00
First seen2026-10-112026-10-11
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

zyte-web-data

In its own words, on Claude Code: claude-plugins-official:

Web scraping skills for Claude Code powered by the Zyte API — scrape sites, generate and run Scrapy spiders, define extraction schemas, and ship to Scrapy Cloud.

dev.fetchgate/fetchgate

In its own words, on Official MCP Registry:

Fetch any URL as clean Markdown or metadata, and buy digital goods via x402 — for AI agents.

How to run each

zyte-web-data As a Claude Code plugin

Claude Code
/plugin install zyte-web-data@claude-plugins-official

dev.fetchgate/fetchgate As a remote MCP server

Claude Code
claude mcp add --transport http fetchgate https://fetchgate.dev/mcp

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

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: zyte-web-data · What it can do: dev.fetchgate/fetchgate · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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