Remote MCP · Endpoint

Chrome Ux Report MCP server

No. Chrome Ux Report answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/chrome-ux-report/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/chrome-ux-report
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Real-user Core Web Vitals for any website with enough traffic, from Google's Chrome UX Report…
Website
https://pipeworx.io/packs/chrome-ux-report
Repository
https://github.com/pipeworx-io/mcp-chrome-ux-report
Listing
From the official MCP registry (active).
Recent checks of Chrome Ux Report
CheckedResultHandshake
1 hour agoHandshake completed54 ms
9 days agoHandshake completed127 ms
9 days agoHandshake completed129 ms
11 days agoHandshake completed125 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed172 ms
14 days agoHandshake completed103 ms
15 days agoHandshake completed914 ms
16 days agoHandshake completed82 ms
19 days agoHandshake completed156 ms
22 days agoHandshake completed122 ms
24 days agoHandshake completed84 ms
26 days agoHandshake completed67 ms
28 days agoHandshake completed990 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 28 responding of 29.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Chrome Ux Report and makes no claim about it beyond what these checks measured.