seo-intelligence vs SERPdive Web Search
seo-intelligence is a plugin bundle for AI coding tools published by trentiums. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). SERPdive Web Search is an MCP server published by serpdive.com. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-26. 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 |  seo-intelligence |  SERPdive Web Search |
|---|---|---|
| Claude Code: claude-plugins-community | Listed Version: 3.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.1.4 Downloads/month (npm): 211 Downloads/week (npm): 31 Forks (GitHub): 0 Stars (GitHub): 0 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 | seo-intelligence | SERPdive Web Search |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (better) | 0 (worse) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | Remote server (mcp.serpdive.com/mcp) |
| Transport (differs) | Not stated | Streamable HTTP |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 4 | 1, secrets among them: 1 |
| Parts of the bundle (differs) | 23 | Not a bundle |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/trentiums/seo-intelligence | github.com/serpdive/serpdive-mcp |
| 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 | Not responding since 2026-10-12 |
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
seo-intelligence
AI-powered SEO analysis, competitor comparison, and ranking plans. Analyze any page's SEO health, compare against top-ranking competitors, and get prioritized action plans to rank higher.
SERPdive Web Search
AI-agent web search, answer-ready content. Beats Tavily: 60.7% of quality duels, 20.2% fewer tokens.
How to run each
seo-intelligence As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install seo-intelligence@claude-communitySERPdive Web Search As a remote MCP server
claude mcp add --transport http serpdive-mcp https://mcp.serpdive.com/mcpRequires: SERPDIVE_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only SERPdive Web Search 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
Only seo-intelligence asks for
GOOGLE_CLOUD_API_KEY (secret)OPENAI_API_KEY (secret)PERPLEXITY_API_KEY (secret)SERPAPI_KEY (secret)
Only SERPdive Web Search asks for
SERPDIVE_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: seo-intelligence · What it can do: SERPdive Web Search · Compare two other plugins
Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/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.