site-traffic-teardown vs Website Auditor
site-traffic-teardown is a plugin bundle for AI coding tools published by zhuyansen. Marketplaces we read that list it: 1 (Community GitHub marketplaces). Website Auditor is an MCP server published by SpikeyCoder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). As of our marketplace pass on 2026-10-30. 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 |  site-traffic-teardown |  Website Auditor |
|---|---|---|
| Community marketplace davepoon/buildwithclaude | Listed Version: 0.1.2 Forks (GitHub): 0 Stars (GitHub): 0 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 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 | site-traffic-teardown | Website Auditor |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (worse) | 1 (better) |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (website-auditor-mcp) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Parts of the bundle (differs) | 1 | Not a bundle |
| Licence | MIT | MIT |
| Repository (differs) | github.com/zhuyansen/site-traffic-teardown | github.com/spikeycoder/website-auditor-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-28 | 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
site-traffic-teardown
Competitor traffic and SEO teardown for any website: finds the competitors (Semrush organic competitors), screens them by Similarweb visits, pulls one side-by-side table (3-month trend, channel mix, Semrush keywords and backlinks, Ahrefs DR) and reads it into growth-engine types and three opportunities. Each stage quotes first for free and runs its billed calls only after the user says yes to that quote, and AIsa rows and pages read along the way stay data. Needs a paid AIsa API key and the AIsa CLI (npm i -g @aisa-one/cli@0.6.9), under $1 per domain.
Website Auditor
AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.
How to run each
site-traffic-teardown As a Claude Code plugin
/plugin marketplace add davepoon/buildwithclaude
/plugin install site-traffic-teardown@buildwithclaudeWebsite 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)
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
The marketplaces of site-traffic-teardown publish no settings it asks for, so we do not compare settings.
What it can do: site-traffic-teardown · What it can do: Website Auditor · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the public npm registry (registry.npmjs.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.