# Pagespeed Insights (npm · @pipeworx/mcp-pagespeed-insights)

Google PageSpeed Insights — runs Lighthouse against any public URL and returns the performance…

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pagespeed-insights-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pagespeed-insights-mcp)
- npm · `@pipeworx/mcp-pagespeed-insights`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights.md), [page](https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-pagespeed-insights`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pagespeed-insights).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 60/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 535 tokens (~267/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Pagespeed Insights MCP server?

Pagespeed Insights runs locally as an npm package, launched with npx -y @pipeworx/mcp-pagespeed-insights. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-pagespeed-insights -- npx -y @pipeworx/mcp-pagespeed-insights
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-pagespeed-insights": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pagespeed-insights"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-pagespeed-insights": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pagespeed-insights"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-pagespeed-insights -- npx -y @pipeworx/mcp-pagespeed-insights
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-pagespeed-insights": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-pagespeed-insights"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-pagespeed-insights --command npx --arg -y --arg @pipeworx/mcp-pagespeed-insights
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-pagespeed-insights:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-pagespeed-insights"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-pagespeed-insights": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-pagespeed-insights"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-pagespeed-insights -t stdio -c npx -a -y @pipeworx/mcp-pagespeed-insights
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-pagespeed-insights": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-pagespeed-insights"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 81, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-04 (score 81, 0)

- [functional regression] Security disclosure: fail → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-03 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (2)

### `pagespeed_audit` (~293 tokens)

Run Google's PageSpeed Insights (Lighthouse) against any public URL and get back the performance, accessibility, best-practices and SEO scores, the lab timing metrics behind them, and the RANKED list of specific fixes with the milliseconds or bytes each one would save — render-blocking resources, unused JavaScript and CSS, unoptimised images, missing text compression. AUTHORITATIVE for "why is this page slow and what do I fix first": this is Google's own analyser running the page on Google's infrastructure, which is what no amount of reading a site's HTML can substitute for. Works on any public site, including a competitor's. A call takes 10-40 seconds because the page is genuinely loaded.

Input parameters:

- `categories` (array): Which Lighthouse categories to run. Defaults to performance only, which is much faster. Options: performance, accessibility, best-practices, seo.
- `locale` (string): BCP-47 locale for the audit titles, e.g. en, fr, ja. Defaults to English.
- `max_opportunities` (number): How many ranked improvement opportunities to return (default 10, max 30).
- `strategy` (string): Device to emulate: mobile (the default, and what Google indexes with) or desktop.
- `url` (string, required): Full page URL to analyse, including the scheme, e.g. https://www.example.com/pricing.

### `pagespeed_field_metrics` (~186 tokens)

Real-user Core Web Vitals for a page AND for its whole origin in one call, from Google's Chrome UX Report as PageSpeed Insights serves it — 75th-percentile Largest Contentful Paint, Interaction to Next Paint, Cumulative Layout Shift and Time to First Byte, with the good/needs-improvement/poor split behind each and Google's own pass/fail verdict. AUTHORITATIVE for whether a page passes Core Web Vitals, and it says plainly when a low-traffic page has no data of its own and Google substituted the origin's — a substitution that otherwise reads as page data and misattributes the whole site's performance to one URL.

Input parameters:

- `strategy` (string): Device class for the field data: mobile (the default) or desktop.
- `url` (string, required): Full page URL, including the scheme, e.g. https://www.example.com/pricing.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights#diagnostics

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Pagespeed Insights MCP server?

Pagespeed Insights is an MCP server listed in the public MCP registry as io.github.pipeworx-io/pagespeed-insights. Google PageSpeed Insights, runs Lighthouse against any public URL and returns the performance… This page covers its npm package (@pipeworx/mcp-pagespeed-insights).

### Is the Pagespeed Insights MCP server safe to use?

Pagespeed Insights scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Pagespeed Insights MCP server expose?

Pagespeed Insights exposes 2 tools: pagespeed_audit, pagespeed_field_metrics. Their descriptions and schemas cost roughly 479 tokens of context every time the server is loaded.

### Is the Pagespeed Insights MCP server still maintained?

Pagespeed Insights is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Pagespeed Insights MCP server under?

Pagespeed Insights declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-pagespeed-insights
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-pagespeed-insights
- Repository: https://github.com/pipeworx-io/mcp-pagespeed-insights
- Website: https://pipeworx.io/packs/pagespeed-insights
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-pagespeed-insights/pipeworx-mcp-pagespeed-insights