# Chrome Ux Report (npm · @pipeworx/mcp-chrome-ux-report)

Real-user Core Web Vitals for any website with enough traffic, from Google's Chrome UX Report…

- Trust score: 82/100 (high trust)
- Change this week: +4
- 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-chrome-ux-report/chrome-ux-report-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-chrome-ux-report/chrome-ux-report-mcp)
- npm · `@pipeworx/mcp-chrome-ux-report`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-chrome-ux-report/pipeworx-mcp-chrome-ux-report.md), [page](https://verifymcp.io/servers/pipeworx-io-chrome-ux-report/pipeworx-mcp-chrome-ux-report)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-chrome-ux-report`
- 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-chrome-ux-report).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - 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.
  - 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add pipeworx-io-chrome-ux-report -- npx -y @pipeworx/mcp-chrome-ux-report
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-chrome-ux-report -- npx -y @pipeworx/mcp-chrome-ux-report
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-chrome-ux-report --command npx --arg -y --arg @pipeworx/mcp-chrome-ux-report
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-chrome-ux-report:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-chrome-ux-report"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-chrome-ux-report -t stdio -c npx -a -y @pipeworx/mcp-chrome-ux-report
```

### Other

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

## 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 82, +1)

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

### 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)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-31 (score 79, 0)

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

### 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 (3)

### `crux_query_origin` (~270 tokens)

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.

Input parameters:

- `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, required): Site origin with scheme and no path, e.g. https://www.shopify.com. For one page, use crux_query_url instead.

### `crux_query_url` (~229 tokens)

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.

Input parameters:

- `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, required): Full page URL including scheme, e.g. https://www.shopify.com/pricing.

### `crux_history` (~242 tokens)

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.

Input parameters:

- `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.

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 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 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 82 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 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 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 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.

## Links

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