Ext Ops Panel
Open dashboard
Comparison

Apify vs io.github.codeislaw101/katzilla

Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.codeislaw101/katzilla is an MCP server published by codeislaw101. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-12. 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
MarketplaceApifyio.github.codeislaw101/katzilla
Docker MCP Catalog Listed
Version: sha256:42cc91f13363
Forks (GitHub): 322
Pulls (Docker Hub): 36 049
Stars (Docker Hub): 0
Stars (GitHub): 10 774
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.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

Apify vs io.github.codeislaw101/katzilla
FactApifyio.github.codeislaw101/katzilla
Marketplaces that list it11
Stars (GitHub) (differs)10 774No figure on GitHub
Pulls (Docker Hub) (differs)36 049No figure on Docker Hub
Forks (GitHub) (differs)322No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/apify-mcp-server)On your machine (@katzilla/mcp)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/apify/actors-mcp-servergithub.com/codeislaw101/katzilla
Changes in the last 7 days00
First seen2026-10-112026-10-11

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

Apify

In its own words, on Docker MCP Catalog:

Apify is the world's largest marketplace of tools for web scraping, data extraction, and web automation. You can extract structured data from social media, e-commerce, search engines, maps, travel sites, or any other website.

io.github.codeislaw101/katzilla

In its own words, on Official MCP Registry:

300+ free public & government data sources behind one API key, for AI agents.

How to run each

Apify As a local MCP server: Docker image

Claude Code
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio apify-mcp-server -- docker run -i --rm -e APIFY_TOKEN mcp/apify-mcp-server

Requires: APIFY_TOKEN (secret)

io.github.codeislaw101/katzilla As a local MCP server: npm package

Claude Code
claude mcp add --env "KATZILLA_API_KEY=<YOUR_KATZILLA_API_KEY>" --transport stdio katzilla -- npx -y @katzilla/mcp

Requires: KATZILLA_API_KEY (secret)

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.codeislaw101/katzilla publish no list of tools, so we do not compare tools.

Settings each asks for

Only Apify asks for

  • APIFY_TOKEN (secret)
  • TOOLS

Only io.github.codeislaw101/katzilla asks for

  • KATZILLA_API_KEY (secret)

Settings as each marketplace publishes them. Asking for fewer is not better in itself.

What it can do: Apify · What it can do: io.github.codeislaw101/katzilla · 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