pulsemcp verified Safe content atomic mcp-remote

Lighthouse Performance Auditing

This MCP server provides comprehensive Lighthouse performance analysis capabilities through automated web performance auditing and deep analysis tools. Built with TypeScript and featuring integration with Google's Lighthouse engine, Puppeteer, and Chrome launcher, it offers four core tools: URL analysis with configurable device types and audit categories, deep analysis with critical request chain examination and unused code detection, batch analysis for multiple URLs in parallel, and prompt generation for AI-assisted performance optimization workflows. The implementation includes specialized analyzers for Core Web Vitals, performance patterns, problem detection, and score breakdowns, with browser pool management for efficient parallel processing and comprehensive reporting that generates prioritized recommendations with impact assessments, making it ideal for web developers, performance engineers, and automated CI/CD pipelines that need programmatic access to detailed website performance insights and optimization guidance.

Cognium trust score

93%

Tier

Verified

Composite of vulnerability cleanliness, spec conformance, provenance, stability, and usage signals — scanned and weighted by Cognium. Human and agent signals are tracked separately. Last scanned 2026-09-28.

Scan details: Circle-IR · 2026-09-28 · Appeal

View full trust & usage report →

Metadata

Version: 1.0.0
Skill type: atomic
Execution layer: mcp-remote
Category: devops-ci
Source: PulseMCP
Repository: github.com/mizchi/lighthouse-mcp
Author type: human
Last scanned: 2026-09-28
Updated: 2026-09-28

View source Find related skills

MCP

Resolve Lighthouse Performance Auditing from your agent

Streamable HTTP transport at https://api.skillsregistry.net/mcp. No auth for read tools. Discovery: .well-known/mcp.json.

One command in your shell — Claude Code wires it up and verifies the connection. Run /mcp in any session to confirm.

claude mcp add --transport http --scope user skillsregistry https://api.skillsregistry.net/mcp

Swap --scope user for --scope project to commit it to .mcp.json.

Your client Same endpoint everywhere; only the config key differs. The full list is in the descriptor.

Claude Desktop · Settings → Connectors → Add custom connector

https://api.skillsregistry.net/mcp

Paste the URL as the connector endpoint. No authentication.

ChatGPT · Settings → Connectors → Create (developer mode) → MCP server URL

https://api.skillsregistry.net/mcp

Authentication: none. Works in chat and deep research — the server exposes the connector search and fetch tools.

Codex CLI · ~/.codex/config.toml

[mcp_servers.skillsregistry]
url = "https://api.skillsregistry.net/mcp"