PageLens AI vs Website Auditor
PageLens AI is an MCP server published by PageLens-AI. 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-10-29. 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 |  PageLens AI |  Website Auditor |
|---|---|---|
| Official MCP Registry | Listed Version: 1.0.0 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 Forks (GitHub): 0 Stars (GitHub): 1 Not marked · First seen |
| npm registry (MCP servers) | Not listed | Listed Version: 1.0.26 Downloads/month (npm): 970 Downloads/week (npm): 107 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 | PageLens AI | Website Auditor |
|---|---|---|
| Marketplaces that list it (differs) | 1 (worse) | 2 (better) |
| Stars (GitHub) | 1 | 1 |
| Forks (GitHub) | 0 | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (www.pagelensai.com/api/mcp) | On your machine (website-auditor-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/pagelens-ai/pagelensai-mcp-server | github.com/spikeycoder/website-auditor-mcp |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Responded 26 h ago, requires a key | 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
PageLens AI
AI website audit: security, SEO, performance, UX and accessibility checks with actionable fixes.
Website Auditor
AI visibility + site audits: see if ChatGPT, Perplexity, Claude & Gemini recommend a website.
How to run each
PageLens AI As a remote MCP server
claude mcp add --transport http pagelensai-mcp-server https://www.pagelensai.com/api/mcpWebsite Auditor As a local MCP server: npm package
claude mcp add --env "WA_API_KEY=<YOUR_WA_API_KEY>" --transport stdio website-auditor-mcp -- npx -y website-auditor-mcpRequires: WA_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Only PageLens AI 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 PageLens AI publish no settings it asks for, so we do not compare settings.
What it can do: PageLens AI · 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.