Ext Ops Panel
Open dashboard
Comparison

Apollo.io vs ai.spideriq/leads

Apollo.io is a plugin bundle for AI coding tools published by Apollo.io. Marketplaces we read that list it: 1 (Claude: knowledge-work-plugins). ai.spideriq/leads is an MCP server published by spideriq.ai. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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

Where each is published
MarketplaceApollo.ioai.spideriq/leads
Claude: knowledge-work-plugins Listed
Version: 0.1.0
Forks (GitHub): 3 583
Stars (GitHub): 32 412
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.9.0
Downloads/month (npm): 339
Downloads/week (npm): 206
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

Apollo.io vs ai.spideriq/leads
FactApollo.ioai.spideriq/leads
Marketplaces that list it11
Stars (GitHub) (differs)32 412No figure on GitHub
Forks (GitHub) (differs)3 583No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)Remote server (mcp.apollo.io/mcp)On your machine (@spideriq/mcp-leads)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Parts of the bundle (differs)4Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/anthropics/knowledge-work-pluginsgithub.com/spideriq/spideriq
Changes in the last 7 days00
First seen2026-10-112026-10-11
Endpoint at the last check (differs)Responded 5 days agono 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

Apollo.io

In its own words, on Claude: knowledge-work-plugins:

Prospect, enrich leads, and load outreach sequences with Apollo.io — one-click MCP server integration for Claude Code and Cowork.

ai.spideriq/leads

In its own words, on Official MCP Registry:

SpiderIQ Leads: lead-gen MCP (jobs, campaigns, IDAP, Maps, People, Verify, company intel, spiderPR)

How to run each

Apollo.io As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/knowledge-work-plugins
/plugin install apollo@knowledge-work-plugins

ai.spideriq/leads As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio leads -- npx -y @spideriq/mcp-leads

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only Apollo.io 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

Neither one's marketplaces publish the settings it asks for.

What it can do: Apollo.io · What it can do: ai.spideriq/leads · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/knowledge-work-plugins/blob/HEAD/.claude-plugin/marketplace.json. 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.

Where the data comes from: how the catalog is built