PageSpeed & Lighthouse Checker vs WebPerf Snippets
PageSpeed & Lighthouse Checker is an MCP server published by monietools. Marketplaces we read that list it: 1 (Official MCP Registry). 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 |  PageSpeed & Lighthouse Checker |  WebPerf Snippets |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 (last published figure) Stars (GitHub): 0 (last published figure) Not marked · First seen |
Listed Version: 1.3.0 Forks (GitHub): 90 Stars (GitHub): 1 454 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 | PageSpeed & Lighthouse Checker | WebPerf Snippets |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | 0 (last published figure) | 1 454 |
| Forks (GitHub) (differs) | 0 (last published figure) | 90 |
| Last release (differs) | Not published | 2026-10-22 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (webperf-snippets) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Licence | Not stated | Not stated |
| Repository (differs) | github.com/monietools/monie-tools | github.com/nucliweb/webperf-snippets |
| Changes in the last 7 days (differs) | 2 | 4 |
| First seen (differs) | 2026-10-19 | 2026-10-21 |
| Endpoint at the last check (differs) | Not responding since 2026-10-24 | no 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
PageSpeed & Lighthouse Checker
Lighthouse scores, Core Web Vitals (LCP, CLS, INP/TBT) and top fixes for any URL, mobile or desktop.
WebPerf Snippets
Measure Core Web Vitals and debug web performance with 56 snippets in a headless Chromium
How to run each
PageSpeed & Lighthouse Checker
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
Requires: Authorization header
WebPerf 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.
Only PageSpeed & Lighthouse Checker 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 PageSpeed & Lighthouse Checker publish no settings it asks for, so we do not compare settings.
What it can do: PageSpeed & Lighthouse Checker · What it can do: WebPerf Snippets · 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.