Email Verification MCP vs FastMCP server for Apollo
Email Verification MCP is an MCP server published by FoundryNet. Marketplaces we read that list it: 1 (Official MCP Registry). FastMCP server for Apollo is an MCP server published by adelaidasofia. Marketplaces we read that list it: 2 (Official MCP Registry, Claude Code: claude-plugins-community). As of our marketplace pass on 2026-10-30. 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 |  Email Verification MCP |  FastMCP server for Apollo |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.1.0 Forks (GitHub): 0 Stars (GitHub): 3 Not marked · First seen |
| Claude Code: claude-plugins-community | Not listed | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 3 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 | Email Verification MCP | FastMCP server for Apollo |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 3 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (email-verify-mcp-production.up.railway.app/mcp) | On your machine (https://github.com/adelaidasofia/apollo-mcp/releases/download/v0.1.0/apollo-mcp.mcpb) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | Not published | 1 |
| Parts of the bundle (differs) | Not a bundle | 2 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/foundrynet/email-verify-mcp | github.com/adelaidasofia/apollo-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Not responding since 2026-10-16 | no remote endpoint we check |
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
Email Verification MCP
Verify emails — deliverability, disposable/role/free detection, MX validity, domain age.
FastMCP server for Apollo
FastMCP server for Apollo.io — 22 tools: sequences, campaign health, mailbox warmup, enrichment,…
How to run each
Email Verification MCP As a remote MCP server
claude mcp add --transport http email-verify-mcp https://email-verify-mcp-production.up.railway.app/mcpFastMCP server for Apollo As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install apollo-mcp@claude-communityRequires: APOLLO_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only Email Verification MCP has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Email Verification MCP publish no settings it asks for, so we do not compare settings.
What it can do: Email Verification MCP · What it can do: FastMCP server for Apollo · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. 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.