Chrome Ux Report
NPM · @PIPEWORX/MCP-CHROME-UX-REPORT · 2 COMPONENTS
Real-user Core Web Vitals for any website with enough traffic, from Google's Chrome UX Report…
Available components
Last scanned (20 hours ago)
Scores higher than 69% of npm servers
Category Monitoring and Observability
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-chrome-ux-report). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability61
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 798 tokens (~266/item across 3 items; 3 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 Management20
- Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 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
- Security disclosure: unverified → fail ▼ functional
- 31 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
- Package version: 0.2.0 → 0.2.1 functional
- 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 4 Nov 2026 · Analysed npm/@pipeworx/mcp-chrome-ux-report@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-chrome-ux-report |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-chrome-ux-report/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606781243 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:6315f7e02087a2373b75044e81dee2716c37f579ccd31076a42017113092cbe2bc6efc40d7e40a857afde0fc954e29bdc2471887195ca931210720ec0 |
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 →
crux_history ~242
How a site's or page's real-user Core Web Vitals have moved over roughly the last 40 weeks, from Google's Chrome UX Report history API. Returns a weekly series of 75th-percentile LCP, INP and CLS with each collection period's dates. AUTHORITATIVE for "did the performance work actually help" and for spotting the week a regression landed — each point is a 28-day trailing window, so consecutive points overlap and a step change in the series marks a real shift in visitor experience.
| Name | Type | Req | Description |
|---|---|---|---|
| form_factor | string | – | Device class to report on: PHONE, DESKTOP, TABLET, or ALL_FORM_FACTORS (the default — every device combined). |
| metrics | array | – | Metrics to return; omit for all available. One or more of largest_contentful_paint, interaction_to_next_paint, cumulative_layout_shift, first_contentful_paint, experimental_time_to_first_byte, round_… |
| origin | string | – | Site origin with scheme and no path, e.g. https://www.shopify.com. Give this OR url. |
| url | string | – | Full page URL. Give this OR origin. |
No output schema declared.
No examples provided.
crux_query_origin ~270
Real-user Core Web Vitals for an entire website, from Google's Chrome UX Report — the 75th-percentile Largest Contentful Paint, Interaction to Next Paint and Cumulative Layout Shift that actual Chrome visitors experienced over the trailing 28 days, plus the good/needs-improvement/poor distribution behind each. AUTHORITATIVE for "is this site passing Core Web Vitals": this is the field dataset Google Search itself uses, so it answers what a lab test such as Lighthouse structurally cannot. PREFER OVER WEB SEARCH for any question about a real site's measured speed, and use it on a competitor's domain as readily as your own — the data is public for every site with enough traffic.
| Name | Type | Req | Description |
|---|---|---|---|
| form_factor | string | – | Device class to report on: PHONE, DESKTOP, TABLET, or ALL_FORM_FACTORS (the default — every device combined). |
| metrics | array | – | Metrics to return; omit for all available. One or more of largest_contentful_paint, interaction_to_next_paint, cumulative_layout_shift, first_contentful_paint, experimental_time_to_first_byte, round_… |
| origin | string | yes | Site origin with scheme and no path, e.g. https://www.shopify.com. For one page, use crux_query_url instead. |
No output schema declared.
No examples provided.
crux_query_url ~229
Real-user Core Web Vitals for ONE specific page, from Google's Chrome UX Report — the 75th-percentile LCP, INP and CLS measured on actual Chrome visits to that exact URL over the trailing 28 days. Use this when a single page (a product page, a landing page, a checkout step) is the question; use crux_query_origin for the site as a whole. A page with too little traffic is absent from the dataset while its origin is present, and that absence is reported plainly rather than as an error.
| Name | Type | Req | Description |
|---|---|---|---|
| form_factor | string | – | Device class to report on: PHONE, DESKTOP, TABLET, or ALL_FORM_FACTORS (the default — every device combined). |
| metrics | array | – | Metrics to return; omit for all available. One or more of largest_contentful_paint, interaction_to_next_paint, cumulative_layout_shift, first_contentful_paint, experimental_time_to_first_byte, round_… |
| url | string | yes | Full page URL including scheme, e.g. https://www.shopify.com/pricing. |
No output schema declared.
No examples provided.
How do I install the Chrome Ux Report MCP server?
Chrome Ux Report runs locally as an npm package, launched with npx -y @pipeworx/mcp-chrome-ux-report. 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-chrome-ux-report
claude mcp add pipeworx-io-chrome-ux-report -- npx -y @pipeworx/mcp-chrome-ux-report
What is the Chrome Ux Report MCP server?
Chrome Ux Report is an MCP server listed in the public MCP registry as io.github.pipeworx-io/chrome-ux-report. Real-user Core Web Vitals for any website with enough traffic, from Google's Chrome UX Report… This page covers its npm package (@pipeworx/mcp-chrome-ux-report).
Is the Chrome Ux Report MCP server safe to use?
Chrome Ux Report scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 Chrome Ux Report MCP server expose?
Chrome Ux Report exposes 3 tools: crux_query_origin, crux_query_url, crux_history. Their descriptions and schemas cost roughly 741 tokens of context every time the server is loaded.
Is the Chrome Ux Report MCP server still maintained?
Chrome Ux Report is still listed as active in the MCP registry. We last reached this channel on 4 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 Chrome Ux Report MCP server under?
Chrome Ux Report declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.