Apify vs vendor-directory-builder
Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). vendor-directory-builder is a plugin bundle for AI coding tools published by DataSift. Marketplaces we read that list it: 1 (Community GitHub marketplaces). As of our marketplace pass on 2026-10-19. 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): 499 Pulls (Docker Hub): 36 533 Stars (Docker Hub): 0 Stars (GitHub): 11 956 Not marked · First seen |
Not listed |
| Community marketplace datasift-ty-personal/siftstack | Not listed | Listed Version: not stated Forks (GitHub): 22 Stars (GitHub): 23 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 | vendor-directory-builder |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 11 956 (better) | 23 (worse) |
| Pulls (Docker Hub) (differs) | 36 533 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 499 (better) | 22 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/apify-mcp-server) | Installs as a plugin bundle |
| Transport (differs) | stdio | Not stated |
| 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 | github.com/datasift-ty-personal/siftstack |
| Changes in the last 7 days (differs) | 0 | 2 |
| First seen (differs) | 2026-10-11 | 2026-10-15 |
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.
vendor-directory-builder
Build a vetted, filterable directory of local service providers (general contractors, subcontractors, trade crews, or any vendors) for a target market by mining a community source (a Facebook group, forum, subreddit,...
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)
vendor-directory-builder As a Claude Code plugin
/plugin marketplace add datasift-ty-personal/siftstack
/plugin install vendor-directory-builder@siftstackCommands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
The marketplaces of vendor-directory-builder publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of vendor-directory-builder publish no settings it asks for, so we do not compare settings.
What it can do: Apify · What it can do: vendor-directory-builder · Compare two other plugins
Data comes from the Docker MCP Catalog (desktop.docker.com/mcp/catalog) and Docker Hub. Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.