Apify vs Agent Utilities Hosted
Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). Agent Utilities Hosted is an MCP server published by agent-utilities.agent-utilities.workers.dev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-20. 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
| Marketplace |  Apify | |
|---|---|---|
| Docker MCP Catalog | Listed Version: sha256:42cc91f13363 Forks (GitHub): 559 Pulls (Docker Hub): 36 635 Stars (Docker Hub): 0 Stars (GitHub): 12 192 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.12.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
| Fact | Apify | Agent Utilities Hosted |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 12 192 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 36 635 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 559 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/apify-mcp-server) | Remote server (agent-utilities.agent-utilities.workers.dev/mcp/remote) |
| Transport (differs) | stdio | Streamable HTTP |
| Tools it declares (differs) | 10 | Not published |
| Environment variables it asks for (differs) | 2, secrets among them: 1 | Not published |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/apify/actors-mcp-server | Not stated |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | no remote endpoint we check | Responded 4 days ago |
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
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.
Agent Utilities Hosted
Free agent tools: SEO snapshots, sitemap refresh, Wikipedia collections and saved-page MCP guides.
How to run each
Apify As a local MCP server: Docker image
claude mcp add --env "APIFY_TOKEN=<YOUR_APIFY_TOKEN>" --transport stdio apify-mcp-server -- docker run -i --rm -e APIFY_TOKEN mcp/apify-mcp-serverRequires: APIFY_TOKEN (secret)
Agent Utilities Hosted As a remote MCP server
claude mcp add --transport http agent-utilities https://agent-utilities.agent-utilities.workers.dev/mcp/remote --header "Authorization: Bearer <YOUR_TOKEN>"Requires: Authorization header
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Agent Utilities Hosted has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of Agent Utilities Hosted publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of Agent Utilities Hosted publish no settings it asks for, so we do not compare settings.
What it can do: Apify · What it can do: Agent Utilities Hosted · 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.