crux_history
Pack: chrome-ux-report · Endpoint: https://gateway.pipeworx.io/chrome-ux-report/mcp
No MCP client? Call it directly: GET https://gateway.pipeworx.io/v1/tools/crux_history for the schema, then POST the same URL with its arguments for the data.
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.
Parameters
| Name | Type | Required | Description |
|---|---|---|---|
origin | string | no | Site origin with scheme and no path, e.g. https://www.shopify.com. Give this OR url. |
url | string | no | Full page URL. Give this OR origin. |
Example call
Arguments
{
"origin": "https://www.shopify.com"
}
curl
curl -X POST https://gateway.pipeworx.io/chrome-ux-report/mcp \
-H 'Content-Type: application/json' \
-d '{"jsonrpc":"2.0","id":1,"method":"tools/call","params":{"name":"crux_history","arguments":{"origin":"https://www.shopify.com"}}}'
TypeScript (@pipeworx/sdk)
import { Pipeworx } from '@pipeworx/sdk';
const pipeworx = new Pipeworx();
const result = await pipeworx.call('crux_history', {
"origin": "https://www.shopify.com"
});
More examples
{
"url": "https://en.wikipedia.org/wiki/Main_Page",
"metrics": [
"largest_contentful_paint",
"cumulative_layout_shift"
]
}
Connect
Add this to your MCP client config, or use one-click install buttons:
{
"mcpServers": {
"chrome-ux-report": {
"url": "https://gateway.pipeworx.io/chrome-ux-report/mcp"
}
}
}
See Getting Started for client-specific install steps.