Pagespeed Insights
NPM · @PIPEWORX/MCP-PAGESPEED-INSIGHTS · 2 COMPONENTS
Google PageSpeed Insights — runs Lighthouse against any public URL and returns the performance…
Available components
Last scanned (4 hours ago)
Scores higher than 68% of npm servers
Category Testing and QA
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-pagespeed-insights). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 4 Nov 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 29 Oct 26 78
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/@pipeworx/mcp-pagespeed-insights@0.2.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-pagespeed-insights |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-pagespeed-insights/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3685247484 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7240ed4e1f5a35f28a673a2c67eba261a84b97a36fce82604332d375f2da25884fdf5f5e866d1e570458b65f20ea56d2af8fdf6fd909082ad283ef112 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
pagespeed_audit ~293
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Full page URL to analyse, including the scheme, e.g. https://www.example.com/pricing. |
No output schema declared.
No examples provided.
pagespeed_field_metrics ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| strategy | string | – | Device class for the field data: mobile (the default) or desktop. |
| url | string | yes | Full page URL, including the scheme, e.g. https://www.example.com/pricing. |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-pagespeed-insights
claude mcp add pipeworx-io-pagespeed-insights -- npx -y @pipeworx/mcp-pagespeed-insights
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.