Ext Ops Panel
Open dashboard
Comparison

Website Auditor vs SiteCheck Agent Intel & Dev

Website Auditor is an MCP server published by SpikeyCoder. Marketplaces we read that list it: 2 (Official MCP Registry, npm registry (MCP servers)). SiteCheck Agent Intel & Dev is an MCP server published by bck-stack. 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

Where each is published
MarketplaceWebsite AuditorSiteCheck Agent Intel & Dev
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: 1.0.0
No figure published
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

Website Auditor vs SiteCheck Agent Intel & Dev
FactWebsite AuditorSiteCheck Agent Intel & Dev
Marketplaces that list it (differs)2 (better)1 (worse)
Stars (GitHub) (differs)1No figure on GitHub
Forks (GitHub) (differs)0No figure on GitHub
Last releaseNot publishedNot published
Where it runs (differs)On your machine (website-auditor-mcp)Remote server (api.fadeandco.workers.dev/mcp)
Transport (differs)stdioStreamable HTTP
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
Licence (differs)MITNot stated
Repository (differs)github.com/spikeycoder/website-auditor-mcpNot stated
Changes in the last 7 days (differs)02
First seen (differs)2026-10-112026-10-23
Endpoint at the last check (differs)no remote endpoint we checknot checked yet

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

In its own words, on Official MCP Registry:

AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.

SiteCheck Agent Intel & Dev

In its own words, on Official MCP Registry:

135 pay-per-call agent tools: agent intelligence, token risk, developer and AI data tools. x402

How to run each

Website Auditor As a local MCP server: npm package

Claude Code
claude mcp add --env "WA_API_KEY=<YOUR_WA_API_KEY>" --transport stdio website-auditor-mcp -- npx -y website-auditor-mcp

Requires: WA_API_KEY (secret)

SiteCheck Agent Intel & Dev

No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.

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 SiteCheck Agent Intel & Dev publish no settings it asks for, so we do not compare settings.

What it can do: Website Auditor · What it can do: SiteCheck Agent Intel & Dev · 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.

Where the data comes from: how the catalog is built