PageSpeed & Lighthouse Checker

io.github.monietoolsPublished by GitHub account monietoolsv1.0.0Updated Oct 27, 2026

Lighthouse scores, Core Web Vitals (LCP, CLS, INP/TBT) and top fixes for any URL, mobile or desktop.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

Remote Apify-hosted MCP server that runs Lighthouse audits on any URL and returns scores, Core Web Vitals and top fixes for mobile or desktop.

What you can do
  • Run Lighthouse audits on a given URL, choosing mobile or desktop emulation.
  • Retrieve performance scores and Core Web Vitals metrics such as LCP, CLS and INP/TBT.
  • Get a list of the top recommended fixes for the audited page.
When to use it
Useful when you want an assistant to check page speed and Core Web Vitals for a site or a specific page, compare mobile versus desktop results, or get prioritized performance fixes without running Lighthouse locally.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. Authentication is required: an Apify API token sent as a Bearer token in the Authorization header, or OAuth sign-in if the client supports it. An Apify account is needed.
Before you install
The server requires an Apify API token, which is a credential granting access to your Apify account; keep it private. Audits are run through Apify, so the URLs you submit are sent to that third party, and usage may be subject to Apify account limits or billing.

Installation

In SourceWeft

  1. Open PageSpeed & Lighthouse Checker in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.monietools%2Fpagespeed-lighthouse-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "pagespeed-lighthouse-checker": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=poised_beardlichen/pagespeed-lighthouse-checker"
    }
  }
}

README

This repository has no README.

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 19, 2026

Score

60% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.