Remote MCP · Endpoint

UI Verify MCP server

No. UI Verify answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://uiverify.ai/api/mcp

The last check completed an MCP handshake.

Registry name
io.github.igrlk/uiverify
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
114 ms
Tools exposed
14 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
MCP server for visual regression testing: triage a PR's UI diffs from your coding agent.
Listing
From the official MCP registry (active).
Recent checks of UI Verify
CheckedResultHandshake
1 hour agoHandshake completed114 ms
2 days agoHandshake completed99 ms
4 days agoHandshake completed94 ms
5 days agoHandshake completed210 ms
7 days agoHandshake completed690 ms
8 days agoHandshake completed111 ms
9 days agoHandshake completed71 ms
12 days agoHandshake completed373 ms
13 days agoHandshake completed110 ms
15 days agoHandshake completed101 ms
17 days agoHandshake completed126 ms
18 days agoHandshake completed122 ms
19 days agoHandshake completed109 ms
20 days agoHandshake completed100 ms
20 days agoHandshake completed86 ms
21 days agoHandshake completed118 ms
23 days agoHandshake completed234 ms

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

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