PageSpeed Insights

click.myagentsPublished by myagents.clickOfficial publisherv1.0.3Updated Nov 4, 2026

Notas do Lighthouse, Core Web Vitals e o que corrigir em qualquer página

The publisher's own server: App Store Connect

VerifiedStreamable HTTPWeb executableDeveloper ToolsData & Analytics

Overview

AI-generated overview

Remote MCP server that gives an assistant Lighthouse scores, Core Web Vitals and fix suggestions for any web page via PageSpeed Insights.

What you can do
  • Retrieve Lighthouse audit results for a given page.
  • Read Core Web Vitals metrics for that page.
  • Get suggestions on what to fix to improve the page's performance.
When to use it
Useful when you want an assistant to check a page's performance and Core Web Vitals and suggest concrete fixes, for example while reviewing or optimizing a site.
Requirements
A remote endpoint at pagespeed.mcp.myagents.click over streamable HTTP; OAuth authentication is required. No environment variables or headers are declared.
Before you install
Sign-in through OAuth is required, so the assistant's access is tied to that account. Page URLs you submit are sent to the remote service and on to the underlying PageSpeed Insights data source.

Installation

In SourceWeft

  1. Open PageSpeed Insights 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/click.myagents%2Fpagespeed/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-insights": {
      "type": "http",
      "url": "https://pagespeed.mcp.myagents.click/mcp"
    }
  }
}

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

3
  1. v1.0.3LatestNov 4, 2026
  2. v1.0.2Oct 22, 2026
  3. v1.0.1Oct 21, 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 Myagents integrations