apollo vs AffiliateSpy
apollo is a plugin bundle for AI coding tools published by apolloio. Marketplaces we read that list it: 4 (Claude Code: claude-plugins-official, Official MCP Registry, Claude Code: claude-plugins-community, Community GitHub marketplaces). AffiliateSpy is an MCP server published by mattrow. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-15. 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 |  apollo |  AffiliateSpy |
|---|---|---|
| Claude Code: claude-plugins-official | Listed Version: 0.1.1 Forks (GitHub): 10 Stars (GitHub): 28 Not marked · First seen |
Not listed |
| Official MCP Registry | Listed Version: 0.1.1 Forks (GitHub): 10 Stars (GitHub): 28 Not marked · First seen |
Listed Version: 1.3.0 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
| Claude Code: claude-plugins-community | Listed Version: 0.1.1 Forks (GitHub): 10 Stars (GitHub): 28 Not marked · First seen |
Not listed |
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 | apollo | AffiliateSpy |
|---|---|---|
| Marketplaces that list it (differs) | 4 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 28 (better) | 0 (worse) |
| Forks (GitHub) (differs) | 10 (better) | 0 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (mcp.apollo.io/mcp) | Remote server (www.affiliatespy.io/api/mcp) |
| Transport | Streamable HTTP | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | Not published | Not published |
| Parts of the bundle (differs) | 6 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/apolloio/apollo-mcp-plugin | github.com/wayfinity/affiliatespy-skills |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 41 h ago | Responded 7 h ago, requires a key |
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
apollo
Prospect, enrich leads, load outreach sequences, and query sales analytics with Apollo.io — one-click MCP server integration for Claude Code and Cowork.
AffiliateSpy
Find and recruit the creators and sites already promoting your competitors, with proof.
How to run each
apollo As a Claude Code plugin
/plugin install apollo@claude-plugins-officialAffiliateSpy As a remote MCP server
claude mcp add --transport http affiliatespy https://www.affiliatespy.io/api/mcp --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.
Both endpoints responded at the last daily 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
Neither one's marketplaces publish the settings it asks for.
What it can do: apollo · What it can do: AffiliateSpy · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-official/blob/HEAD/.claude-plugin/marketplace.json. 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.