Remote MCP · Endpoint

WebSpeed MCP server

No. WebSpeed answered an MCP handshake 3 hours ago.

UpLast checked 3 hours ago

Server URL

https://api.webspeed.pro/mcp

The last check completed an MCP handshake.

Registry name
pro.webspeed/webspeed
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
312 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Measure a page with PageSpeed Insights and compare it with its copy sped up by WebSpeed Fast.
Listing
From the official MCP registry (active).
Recent checks of WebSpeed
CheckedResultHandshake
3 hours agoHandshake completed312 ms
4 days agoHandshake completed309 ms
14 days agoHandshake completed365 ms
15 days agoHandshake completed297 ms
15 days agoHandshake completed326 ms
17 days agoHandshake completed314 ms
18 days agoHandshake completed318 ms
19 days agoHandshake completed294 ms
20 days agoHandshake completed324 ms
21 days agoHandshake completed310 ms
23 days agoHandshake completed323 ms

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

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 WebSpeed and makes no claim about it beyond what these checks measured.