Ext Ops Panel
Open dashboard
Comparison

SyteCheck vs io.github.thegridwork/siteaudit

SyteCheck is an MCP server published by sytecheck.com. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.thegridwork/siteaudit is an MCP server published by thegridwork. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-05. 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
MarketplaceSyteCheckio.github.thegridwork/siteaudit
Official MCP Registry Listed
Version: 0.1.4
Downloads/month (npm): 375
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
Not marked · First seen
Listed
Version: 1.0.1
Downloads/month (npm): 116
Downloads/week (npm): 45
Forks (GitHub): 0
Stars (GitHub): 0
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

SyteCheck vs io.github.thegridwork/siteaudit
FactSyteCheckio.github.thegridwork/siteaudit
Marketplaces that list it11
Stars (GitHub)00
Forks (GitHub)00
Last release (differs)2026-10-29Not published
Where it runs (differs)On your machine (@ascentws/sytecheck-mcp)On your machine (gridwork-siteaudit)
Transportstdiostdio
Tools it declaresNot publishedNot published
Environment variables it asks for (differs)2, secrets among them: 1Not published
LicenceNot statedNot stated
Repository (differs)github.com/bertpc/sytecheck-mcpgithub.com/thegridwork/siteaudit
Changes in the last 7 days00
First seen2026-10-112026-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

SyteCheck

In its own words, on Official MCP Registry:

Scan a website for SEO, accessibility, performance and security issues, and read the report.

io.github.thegridwork/siteaudit

In its own words, on Official MCP Registry:

Audit websites for accessibility, performance, SEO, design, and mobile. 47 WCAG checks.

How to run each

SyteCheck As a local MCP server: npm package

Claude Code
claude mcp add --env "SYTECHECK_API_KEY=<YOUR_SYTECHECK_API_KEY>" --transport stdio sytecheck-mcp -- npx -y @ascentws/sytecheck-mcp

Requires: SYTECHECK_API_KEY (secret)

io.github.thegridwork/siteaudit As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio siteaudit -- npx -y gridwork-siteaudit

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 io.github.thegridwork/siteaudit publish no settings it asks for, so we do not compare settings.

What it can do: SyteCheck · What it can do: io.github.thegridwork/siteaudit · 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.

Where the data comes from: how the catalog is built