Ext Ops Panel
Open dashboard
Comparison

Apify vs CartScout

Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). CartScout is an MCP server published by Veselin15. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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
MarketplaceApifyCartScout
Docker MCP Catalog Listed
Version: sha256:42cc91f13363
Forks (GitHub): 398
Pulls (Docker Hub): 37 612
Stars (Docker Hub): 0
Stars (GitHub): 13 555
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.1.0
Downloads/month (PyPI): 181
Downloads/week (PyPI): 29
Forks (GitHub): 0
Stars (GitHub): 1
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 CartScout
FactApifyCartScout
Marketplaces that list it11
Stars (GitHub) (differs)13 555 (better)1 (worse)
Pulls (Docker Hub) (differs)37 612No figure on Docker Hub
Forks (GitHub) (differs)398 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)On your machine (mcp/apify-mcp-server)On your machine (cartscout-mcp)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for2, secrets among them: 12, secrets among them: 1
Licence (differs)MITNot stated
Repository (differs)github.com/apify/actors-mcp-servergithub.com/veselin15/cartscout-mcp
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.

CartScout

In its own words, on Official MCP Registry:

Live product prices, stock, variants and deal ratings from Shopify, Walmart, eBay and more.

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)

CartScout As a local MCP server: PyPI package

Claude Code
claude mcp add --env "RAPIDAPI_KEY=<YOUR_RAPIDAPI_KEY>" --transport stdio cartscout-mcp -- uvx cartscout-mcp

Requires: RAPIDAPI_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 CartScout publish no list of tools, so we do not compare tools.

Settings each asks for

Only Apify asks for

  • APIFY_TOKEN (secret)
  • TOOLS

Only CartScout asks for

  • CARTSCOUT_RAPIDAPI_HOST
  • RAPIDAPI_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: CartScout · 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