Bulk PageSpeed & Lighthouse Checker: Core Web Vitals from CSV

io.github.Nero-EnginePublished by GitHub account Nero-Enginev0.1.0Updated Oct 24, 2026

Google PageSpeed Insights (Lighthouse) scores, Core Web Vitals and top speed fixes for every URL...

The publisher's own server: core.blue

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

A remote Apify MCP server that runs bulk Google PageSpeed Insights (Lighthouse) checks on many URLs and returns scores, Core Web Vitals and top speed fixes.

What you can do
Run Lighthouse/PageSpeed checks across a list of URLs in bulk and collect the results in one pass. Return Google PageSpeed Insights scores, Core Web Vitals metrics and the top speed fixes for each URL. Intended for auditing site performance at scale rather than one page at a time.
When to use it
Useful when you need performance audits for many pages at once, such as checking a whole site's Core Web Vitals or comparing speed across a list of URLs, without running each check by hand.
Requirements
A remote endpoint at mcp.apify.com over streamable HTTP, with OAuth authentication. An Apify API token is required, sent in the Authorization header as a Bearer token. Network access is needed.
Before you install
The Authorization header carries your Apify API token, a secret. Runs are billed per event to your Apify account, so bulk checks can incur costs. Results depend on Google PageSpeed Insights data being fetched for the URLs you submit.

Installation

In SourceWeft

  1. Open Bulk PageSpeed & Lighthouse Checker: Core Web Vitals from CSV 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.Nero-Engine%2Fbulk-pagespeed-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": {
    "bulk-pagespeed-lighthouse-checker-core-w": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=nerolabs/bulk-pagespeed-checker"
    }
  }
}

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. v0.1.0LatestOct 1, 2026

Score

67% 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.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Core integrations