Remote MCP · Endpoint

Chrome Web Store MCP server

No. Chrome Web Store answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://gateway.pipeworx.io/chrome-web-store/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/chrome-web-store
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
459 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Chrome Web Store — public extension listing data: a single extension by id, free-text search, and…
Listing
From the official MCP registry (active).
Recent checks of Chrome Web Store
CheckedResultHandshake
19 minutes agoHandshake completed459 ms
9 days agoHandshake completed936 ms
9 days agoHandshake completed322 ms
11 days agoHandshake completed346 ms
12 days agoHandshake completed1.47 s
13 days agoHandshake completed278 ms
14 days agoHandshake completed180 ms
15 days agoHandshake completed127 ms
16 days agoHandshake completed281 ms
19 days agoHandshake completed78 ms
22 days agoHandshake completed333 ms
24 days agoHandshake completed72 ms
26 days agoHandshake completed1.01 s
28 days agoHandshake completed1.23 s

The last 14 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 Chrome Web Store and makes no claim about it beyond what these checks measured.