Apify vs io.github.ryuamarines/email-extractor
Apify is an MCP server published by apify. Marketplaces we read that list it: 1 (Docker MCP Catalog). io.github.ryuamarines/email-extractor is an MCP server published by ryuamarines. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. 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): 328 Pulls (Docker Hub): 36 138 Stars (Docker Hub): 0 Stars (GitHub): 10 975 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.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 | io.github.ryuamarines/email-extractor |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 10 975 | No figure on GitHub |
| Pulls (Docker Hub) (differs) | 36 138 | No figure on Docker Hub |
| Forks (GitHub) (differs) | 328 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (mcp/apify-mcp-server) | Remote server (faceted-napped-debtless.ngrok-free.dev/email-extractor/mcp) |
| 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 | Answered with HTTP 404 (21 h 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.
io.github.ryuamarines/email-extractor
Extracts emails from texts. x402 payment required (testnet USDC).
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)
io.github.ryuamarines/email-extractor As a remote MCP server
claude mcp add --transport http email-extractor https://faceted-napped-debtless.ngrok-free.dev/email-extractor/mcpCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only io.github.ryuamarines/email-extractor has a remote endpoint we check. How we check endpoints
Tools each declares
The marketplaces of io.github.ryuamarines/email-extractor publish no list of tools, so we do not compare tools.
Settings each asks for
The marketplaces of io.github.ryuamarines/email-extractor publish no settings it asks for, so we do not compare settings.
What it can do: Apify · What it can do: io.github.ryuamarines/email-extractor · 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.