seo-intelligence vs SEO Tools: XMLRiver SERP (Google + Yandex)
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). SEO Tools: XMLRiver SERP (Google + Yandex) is an MCP server published by antohins. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-28. 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 |  SEO Tools: XMLRiver SERP (Google + Yandex) |
|---|---|---|
| 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: 1.8.0 Downloads/month (npm): 209 Downloads/week (npm): 24 Forks (GitHub): 0 Stars (GitHub): 8 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 | SEO Tools: XMLRiver SERP (Google + Yandex) |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (seo-tools-mcp-xmlriver) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 4, secrets among them: 4 | 4, 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/antohins/seo-tools-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
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.
SEO Tools: XMLRiver SERP (Google + Yandex)
Google & Yandex SERP, image/news verticals and URL indexation checks via XMLRiver (read-only).
How to run each
seo-intelligence As a Claude Code plugin
/plugin marketplace add anthropics/claude-plugins-community
/plugin install seo-intelligence@claude-communitySEO Tools: XMLRiver SERP (Google + Yandex) As a local MCP server: npm package
claude mcp add --env "XMLRIVER_KEY=<YOUR_XMLRIVER_KEY>" --transport stdio seo-tools-mcp-xmlriver -- npx -y seo-tools-mcp-xmlriverRequires: XMLRIVER_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
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 SEO Tools: XMLRiver SERP (Google + Yandex) asks for
XMLRIVER_EXCLUDE_DOMAINSXMLRIVER_KEY (secret)XMLRIVER_PRICE_PER_CALLXMLRIVER_USER
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: seo-intelligence · What it can do: SEO Tools: XMLRiver SERP (Google + Yandex) · 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.