PageSpeed & Lighthouse Checker vs Bing Webmaster AI CLI MCP
PageSpeed & Lighthouse Checker is an MCP server published by monietools. Marketplaces we read that list it: 1 (Official MCP Registry). Bing Webmaster AI CLI MCP is an MCP server published by stufently. Marketplaces we read that list it: 2 (Official MCP Registry, PyPI (MCP servers)). 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
| Marketplace | ||
|---|---|---|
| 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: 0.1.4 Downloads/month (PyPI): 0 Downloads/week (PyPI): 169 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| PyPI (MCP servers) | Not listed | Listed Version: 0.1.4 Downloads/month (PyPI): 0 Downloads/week (PyPI): 169 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
| Fact | PageSpeed & Lighthouse Checker | Bing Webmaster AI CLI MCP |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) (differs) | 0 (last published figure) | 1 |
| Forks (GitHub) (differs) | 0 (last published figure) | 0 |
| Last release (differs) | Not published | 2026-10-15 |
| Where it runs (differs) | Remote server (mcp.apify.com) | On your machine (bing-webmaster-ai-cli-mcp) |
| Transport (differs) | Streamable HTTP | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 2, secrets among them: 1 |
| Licence (differs) | Not stated | MIT |
| Repository (differs) | github.com/monietools/monie-tools | github.com/stufently/bing-webmaster-ai-cli-mcp |
| Changes in the last 7 days (differs) | 2 | 0 |
| First seen (differs) | 2026-10-19 | 2026-10-11 |
| 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.
Bing Webmaster AI CLI MCP
Read Bing Webmaster data and change it, directly or through a reviewed plan.
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
Bing Webmaster AI CLI MCP As a local MCP server: PyPI package
claude mcp add --env "BING_WM_API_KEY=<YOUR_BING_WM_API_KEY>" --transport stdio bing-webmaster-ai-cli-mcp -- uvx bing-webmaster-ai-cli-mcp
Requires: BING_WM_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: Bing Webmaster AI CLI MCP · 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.