Remote MCP · Endpoint

ViewportWitness by Apex Labs MCP server

No. ViewportWitness by Apex Labs answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://qa.honeygate.app/mcp

The last check completed an MCP handshake.

Registry name
io.github.Baffles78/viewport-witness
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
54 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Agent website testing: browser QA, visual regression, Markdown extraction, and security checks.
Listing
From the official MCP registry (active).
Recent checks of ViewportWitness by Apex Labs
CheckedResultHandshake
16 minutes agoHandshake completed54 ms
8 days agoHandshake completed94 ms
9 days agoHandshake completed68 ms
11 days agoHandshake completed56 ms
12 days agoHandshake completed77 ms
13 days agoHandshake completed79 ms
14 days agoHandshake completed71 ms
14 days agoHandshake completed76 ms
16 days agoHandshake completed147 ms
19 days agoHandshake completed684 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed991 ms
26 days agoHandshake completed450 ms
28 days agoHandshake completed49 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 29 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 ViewportWitness by Apex Labs and makes no claim about it beyond what these checks measured.