Remote MCP · Endpoint

Mozilla Observatory MCP server

No. Mozilla Observatory answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://gateway.pipeworx.io/mozilla-observatory/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/mozilla-observatory
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
56 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
MDN HTTP Observatory — grade any website's HTTP security headers and get the specific fixes, from…
Listing
From the official MCP registry (active).
Recent checks of Mozilla Observatory
CheckedResultHandshake
5 hours agoHandshake completed56 ms
9 days agoHandshake completed225 ms
10 days agoHandshake completed516 ms
11 days agoHandshake completed238 ms
12 days agoHandshake completed190 ms
14 days agoHandshake completed1.78 s
15 days agoHandshake completed128 ms
15 days agoHandshake completed95 ms
17 days agoHandshake completed460 ms
19 days agoHandshake completed175 ms
22 days agoHandshake completed58 ms
24 days agoHandshake completed157 ms
27 days agoHandshake completed76 ms
29 days agoHandshake completed242 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 26 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.

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