Remote MCP · Endpoint

Pagespeed Insights MCP server

No. Pagespeed Insights answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://gateway.pipeworx.io/pagespeed-insights/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/pagespeed-insights
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
92 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Google PageSpeed Insights — runs Lighthouse against any public URL and returns the performance…
Listing
From the official MCP registry (active).
Recent checks of Pagespeed Insights
CheckedResultHandshake
1 day agoHandshake completed92 ms
3 days agoHandshake completed85 ms
5 days agoHandshake completed55 ms
6 days agoHandshake completed53 ms
8 days agoHandshake completed86 ms
9 days agoHandshake completed41 ms
10 days agoHandshake completed49 ms
13 days agoHandshake completed39 ms
15 days agoHandshake completed50 ms
17 days agoHandshake completed40 ms
18 days agoHandshake completed76 ms
19 days agoHandshake completed38 ms
20 days agoHandshake completed61 ms
21 days agoHandshake completed1.26 s
22 days agoHandshake completed49 ms

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

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.

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