io.github.SeoScoreAPI/seoscoreapi-mcp vs mcp-seo-audit
io.github.SeoScoreAPI/seoscoreapi-mcp is an MCP server published by SeoScoreAPI. Marketplaces we read that list it: 1 (Official MCP Registry). mcp-seo-audit is an MCP server published by atomno-mcp. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. 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.SeoScoreAPI/seoscoreapi-mcp |  mcp-seo-audit |
|---|---|---|
| Official MCP Registry | Listed Version: 1.4.1 Downloads/month (npm): 651 Downloads/week (npm): 434 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Listed Version: 0.4.7 Downloads/month (PyPI): 189 Downloads/week (PyPI): 56 Forks (GitHub): 0 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.SeoScoreAPI/seoscoreapi-mcp | mcp-seo-audit |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (seoscoreapi-mcp) | On your machine (atomno-mcp-seo-audit) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 1, secrets among them: 1 | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/seoscoreapi/seoscoreapi-mcp | github.com/atomno-mcp/mcp-seo-audit |
| 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.SeoScoreAPI/seoscoreapi-mcp
SEO audits, AI readability, accessibility, backlinks and score monitoring from SEO Score API.
mcp-seo-audit
Technical SEO site audit MCP: health score, issues, robots, sitemap, JSON-LD.
How to run each
io.github.SeoScoreAPI/seoscoreapi-mcp As a local MCP server: npm package
claude mcp add --env "SEO_SCORE_API_KEY=<YOUR_SEO_SCORE_API_KEY>" --transport stdio seoscoreapi-mcp -- npx -y seoscoreapi-mcpRequires: SEO_SCORE_API_KEY (secret)
mcp-seo-audit As a local MCP server: PyPI package
claude mcp add --env "DETAILWEB_API_KEY=<YOUR_DETAILWEB_API_KEY>" --transport stdio mcp-seo-audit -- uvx atomno-mcp-seo-auditRequires: DETAILWEB_API_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 io.github.SeoScoreAPI/seoscoreapi-mcp asks for
SEO_SCORE_API_KEY (secret)
Only mcp-seo-audit asks for
DETAILWEB_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: io.github.SeoScoreAPI/seoscoreapi-mcp · What it can do: mcp-seo-audit · 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.