Website Auditor vs Stobo SEO & AEO Audit
Website Auditor is an MCP server published by SpikeyCoder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). Stobo SEO & AEO Audit is an MCP server published by stobo-app. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-25. 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 |  Website Auditor |  Stobo SEO & AEO Audit |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 0.4.3 Downloads/month (PyPI): 153 Downloads/week (PyPI): 49 Forks (GitHub): 2 Stars (GitHub): 8 Not marked · First seen |
| npm registry (MCP servers) | Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Not listed |
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 | Website Auditor | Stobo SEO & AEO Audit |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 1 (worse) | 8 (better) |
| Forks (GitHub) (differs) | 0 (worse) | 2 (better) |
| Last release | Not published | Not published |
| Where it runs (differs) | On your machine (website-auditor-mcp) | On your machine (stobo-mcp) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for | 2, secrets among them: 1 | 2, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/spikeycoder/website-auditor-mcp | github.com/stobo-app/stobo-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
Website Auditor
AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.
Stobo SEO & AEO Audit
AI-powered SEO and AEO audit for websites
How to run each
Website Auditor As a local MCP server: npm package
claude mcp add --env "WA_API_KEY=<YOUR_WA_API_KEY>" --transport stdio website-auditor-mcp -- npx -y website-auditor-mcpRequires: WA_API_KEY (secret)
Stobo SEO & AEO Audit As a local MCP server: PyPI package
claude mcp add --env "STOBO_API_KEY=<YOUR_STOBO_API_KEY>" --transport stdio seo-audit -- uvx stobo-mcpRequires: STOBO_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 Website Auditor asks for
WA_API_BASE_URLWA_API_KEY (secret)
Only Stobo SEO & AEO Audit asks for
STOBO_API_KEY (secret)STOBO_BASE_URL
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Website Auditor · What it can do: Stobo SEO & AEO Audit · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Data comes from public marketplace files in GitHub repositories of their authors. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.