Lighthouse Audit
Related Servers
Alternatives to Lighthouse Audit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables running comprehensive website audits from any MCP client, returning actionable plain-language reports covering SEO, accessibility, performance, security, and more.644 npmMIT
- AlicenseNot gradedqualityCmaintenanceRuns Google PageSpeed Insights audits against any public URL, returning Lighthouse scores, lab timing metrics, ranked fixes, and real-user Chrome UX Report field data.258 npmMIT
- AlicenseAqualityCmaintenanceEnables running Lighthouse web performance audits via MCP, providing Core Web Vitals, performance scores, and optimization suggestions for single or multiple URLs.21,529 npm1MIT
- AlicenseAqualityBmaintenanceEnables auditing any public website, returning a scored plain-English report that flags issues costing customers, covering speed, phone experience, search visibility, contact options, writing quality, and modernity.1MIT
- FlicenseNot gradedqualityDmaintenanceEnables auditing of websites for performance, SEO, accessibility, security, and mobile readiness, with tools to validate URLs, run page audits, save results, and retrieve reports.1-
- FlicenseAqualityDmaintenanceEnables MCP-compatible agents to run real browser-based performance scans on any URL and receive a rich Markdown dashboard with Core Web Vitals, grades, and actionable recommendations.1-
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of misselection or overlap. Its purpose (run a Lighthouse audit via PageSpeed Insights) is clearly stated and distinct by definition.
A single tool named run_lighthouse follows a clear verb_noun convention. With only one tool there is no possibility of inconsistent naming patterns.
The server is focused on one narrow capability, but a single tool makes for a thin surface with no alternatives or complementary operations. It is borderline appropriate for the scope rather than well-scoped.
The core audit operation is covered, but notable lifecycle gaps exist: no audit history, no result retrieval/comparison, no desktop toggle surfaced in the tool list, and whole-site or authenticated pages are explicitly unsupported. Agents can perform a one-off audit but cannot persist or compare results.