Ext Ops Panel
Open dashboard
Comparison

Apify vs Torob

Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). Torob is an MCP server published by sepehr071. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). As of our marketplace pass on 2026-11-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
MarketplaceApifyTorob
Docker MCP Catalog Listed
Version: sha256:42cc91f13363
Forks (GitHub): 449
Pulls (Docker Hub): 39 333
Stars (Docker Hub): 0
Stars (GitHub): 15 731
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 0.2.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 273
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
PyPI (MCP servers) Not listed Listed
Version: 0.2.1
Downloads/month (PyPI): 0
Downloads/week (PyPI): 273
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 Torob
FactApifyTorob
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)15 731 (better)1 (worse)
Pulls (Docker Hub) (differs)39 333No figure on Docker Hub
Forks (GitHub) (differs)449 (better)0 (worse)
Last release (differs)Not published2026-11-11
Where it runs (differs)On your machine (mcp/apify-mcp-server)On your machine (torob-mcp)
Transportstdiostdio
Tools it declares (differs)10Not published
Environment variables it asks for (differs)2, secrets among them: 11, secrets among them: 0
LicenceMITMIT
Repository (differs)github.com/apify/actors-mcp-servergithub.com/sepehr071/torob-mcp
Changes in the last 7 days (differs)05
First seen (differs)2026-10-112026-10-18

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.

Torob

In its own words, on Official MCP Registry:

Unofficial read-only Torob: compare Iranian shop prices, price history, deal checks and baskets.

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)

Torob As a local MCP server: PyPI package

Claude Code
claude mcp add --transport stdio torob-mcp -- uvx torob-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 Torob publish no list of tools, so we do not compare tools.

Settings each asks for

Only Apify asks for

  • APIFY_TOKEN (secret)
  • TOOLS

Only Torob asks for

  • TOROB_MCP_PROXY

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

What it can do: Apify · What it can do: Torob · 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. Package data comes from the Python Package Index (pypi.org). 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