MCP Lighthouse Audit
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_pageA | Run a detailed Lighthouse audit on a URL. Returns scores for all categories and a list of failed audits with specific elements that need fixing. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool, there is no possibility of confusion between tools. The purpose is clearly defined as running a Lighthouse audit.
The single tool name 'audit_page' follows a clear verb_noun pattern, which is consistent and descriptive.
A single tool for a Lighthouse audit server is functional but feels minimal. The tool is well-scoped, yet the server could benefit from additional related tools (e.g., audit_mobile, compare_audits).
The tool covers the core audit action comprehensively, returning all category scores and failed audits. However, there are no supplementary operations like retrieving historical audits or configuring audit options.