Ext Ops Panel
Open dashboard
Comparison

BHG Site Tracking Check vs Website Auditor

BHG Site Tracking Check is an MCP server published by BHGSupport. Marketplaces we read that list it: 1 (Official MCP Registry). 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-11-10. 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
MarketplaceBHG Site Tracking CheckWebsite Auditor
Official MCP Registry Listed
Version: 1.0.0
No figure published
Not marked · First seen
Listed
Version: 1.0.29
Downloads/month (npm): 823
Downloads/week (npm): 333
Forks (GitHub): 0
Stars (GitHub): 1
Not marked · First seen
npm registry (MCP servers) Not listed Listed
Version: 1.0.29
Downloads/month (npm): 823
Downloads/week (npm): 333
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

BHG Site Tracking Check vs Website Auditor
FactBHG Site Tracking CheckWebsite Auditor
Marketplaces that list it (differs)1 (worse)2 (better)
Stars (GitHub) (differs)No figure on GitHub1
Forks (GitHub) (differs)No figure on GitHub0
Last release (differs)Not published2026-11-04
Where it runs (differs)Remote server (bhgreports.com/site/mcp)On your machine (website-auditor-mcp)
Transport (differs)Streamable HTTPstdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)Not published2, secrets among them: 1
Licence (differs)Not statedMIT
Repository (differs)Not statedgithub.com/spikeycoder/website-auditor-mcp
Changes in the last 7 days (differs)04
First seen (differs)2026-11-022026-10-11
Endpoint at the last check (differs)Status out of date: last check 40 h ago returned HTTP 405no remote endpoint we check

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

BHG Site Tracking Check

In its own words, on Official MCP Registry:

Checks a public web page in a real browser for analytics and ad conversion tags. No key needed.

Website Auditor

In its own words, on Official MCP Registry:

AI visibility in ChatGPT, Gemini, Claude, Perplexity, Copilot & AI Overviews, plus site audits.

How to run each

BHG Site Tracking Check As a remote MCP server

Claude Code
claude mcp add --transport http site-tracking-check https://bhgreports.com/site/mcp

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)

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Only BHG Site Tracking Check has a remote endpoint we check. How we check endpoints

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 BHG Site Tracking Check publish no settings it asks for, so we do not compare settings.

What it can do: BHG Site Tracking Check · What it can do: Website Auditor · 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