Screaming Frog SEO Spider MCP Server (headless) vs WebPerf Snippets
Screaming Frog SEO Spider MCP Server (headless) is an MCP server published by bzsasson. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). WebPerf Snippets is an MCP server published by nucliweb. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-24. 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 |  Screaming Frog SEO Spider MCP Server (headless) |  WebPerf Snippets |
|---|---|---|
| Official MCP Registry | Listed Version: 0.4.3 Downloads/month (PyPI): 447 Downloads/week (PyPI): 649 Forks (GitHub): 19 Stars (GitHub): 93 Not marked · First seen |
Listed Version: 1.3.0 Forks (GitHub): 90 Stars (GitHub): 1 454 Not marked · First seen |
| PyPI (MCP servers) | Listed Version: 0.4.3 Downloads/month (PyPI): 447 Downloads/week (PyPI): 649 Forks (GitHub): 19 Stars (GitHub): 93 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 | Screaming Frog SEO Spider MCP Server (headless) | WebPerf Snippets |
|---|---|---|
| Marketplaces that list it (differs) | 2 (better) | 1 (worse) |
| Stars (GitHub) (differs) | 93 (worse) | 1 454 (better) |
| Forks (GitHub) (differs) | 19 (worse) | 90 (better) |
| Last release (differs) | 2026-10-17 (worse) | 2026-10-22 (better) |
| Where it runs (differs) | On your machine (screaming-frog-mcp) | On your machine (webperf-snippets) |
| Transport | stdio | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | 1, secrets among them: 0 | 1, secrets among them: 1 |
| Licence (differs) | MIT | Not stated |
| Repository (differs) | github.com/bzsasson/screaming-frog-mcp | github.com/nucliweb/webperf-snippets |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-11 | 2026-10-21 |
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
Screaming Frog SEO Spider MCP Server (headless)
Headless Screaming Frog SEO Spider via its CLI: run crawls, export and filter data, no GUI needed.
WebPerf Snippets
Measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium
How to run each
Screaming Frog SEO Spider MCP Server (headless) As a local MCP server: PyPI package
claude mcp add --transport stdio screaming-frog-mcp -- uvx screaming-frog-mcpWebPerf Snippets As a local MCP server: npm package
claude mcp add --env "CRUX_API_KEY=<YOUR_CRUX_API_KEY>" --transport stdio webperf-snippets -- npx -y webperf-snippets mcpRequires: CRUX_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 Screaming Frog SEO Spider MCP Server (headless) asks for
SF_CLI_PATH
Only WebPerf Snippets asks for
CRUX_API_KEY (secret)
Settings as each marketplace publishes them. Asking for fewer is not better in itself.
What it can do: Screaming Frog SEO Spider MCP Server (headless) · What it can do: WebPerf Snippets · Compare two other plugins
Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Package data comes from the Python Package Index (pypi.org). Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.