io.github.avansaber/seo-monster vs io.github.ryudi84/seo-analyzer
io.github.avansaber/seo-monster is an MCP server published by avansaber. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ryudi84/seo-analyzer is an MCP server published by ryudi84. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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 |  io.github.avansaber/seo-monster |  io.github.ryudi84/seo-analyzer |
|---|---|---|
| Official MCP Registry | Listed Version: 0.9.3 Downloads/month (PyPI): 826 Downloads/week (PyPI): 537 Forks (GitHub): 69 Stars (GitHub): 500 Not marked · First seen |
Listed Version: 1.0.0 Downloads/month (npm): 144 Downloads/week (npm): 61 Forks (GitHub): 2 Stars (GitHub): 1 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 | io.github.avansaber/seo-monster | io.github.ryudi84/seo-analyzer |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 500 (better) | 1 (worse) |
| Forks (GitHub) (differs) | 69 (better) | 2 (worse) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (seo-monster) | On your machine (sovereign-seo-analyzer-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 19, secrets among them: 11 | Not published |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/avansaber/seo-monster | github.com/ryudi84/sovereign-mcp-servers |
| 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
io.github.avansaber/seo-monster
Local-first SEO MCP: track AI citations, Search Console, GA4, PageSpeed, Cloudflare, IndexNow, CrUX.
io.github.ryudi84/seo-analyzer
MCP server for SEO analysis: meta tags, headings, keywords, sitemaps.
How to run each
io.github.avansaber/seo-monster As a local MCP server: PyPI package
claude mcp add --env "ANTHROPIC_API_KEY=<YOUR_ANTHROPIC_API_KEY>" --env "CF_API_TOKEN=<YOUR_CF_API_TOKEN>" --env "DATAFORSEO_LOGIN=<YOUR_DATAFORSEO_LOGIN>" --env "DATAFORSEO_PASSWORD=<YOUR_DATAFORSEO_PASSWORD>" --env "GEMINI_API_KEY=<YOUR_GEMINI_API_KEY>" --env "GOOGLE_ADS_DEVELOPER_TOKEN=<YOUR_GOOGLE_ADS_DEVELOPER_TOKEN>" --env "OPENAI_API_KEY=<YOUR_OPENAI_API_KEY>" --env "OPENPAGERANK_API_KEY=<YOUR_OPENPAGERANK_API_KEY>" --env "PERPLEXITY_API_KEY=<YOUR_PERPLEXITY_API_KEY>" --env "PSI_API_KEY=<YOUR_PSI_API_KEY>" --env "SEO_MCP_INDEXNOW_KEY=<YOUR_SEO_MCP_INDEXNOW_KEY>" --transport stdio seo-monster -- uvx seo-monsterRequires: ANTHROPIC_API_KEY (secret), CF_API_TOKEN (secret), DATAFORSEO_LOGIN (secret), DATAFORSEO_PASSWORD (secret), GEMINI_API_KEY (secret), GOOGLE_ADS_DEVELOPER_TOKEN (secret), OPENAI_API_KEY (secret), OPENPAGERANK_API_KEY (secret), PERPLEXITY_API_KEY (secret), PSI_API_KEY (secret), SEO_MCP_INDEXNOW_KEY (secret)
io.github.ryudi84/seo-analyzer As a local MCP server: npm package
claude mcp add --transport stdio seo-analyzer -- npx -y sovereign-seo-analyzer-mcpCommands 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
The marketplaces of io.github.ryudi84/seo-analyzer publish no settings it asks for, so we do not compare settings.
What it can do: io.github.avansaber/seo-monster · What it can do: io.github.ryudi84/seo-analyzer · Compare two other plugins
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.