Remote MCP · Endpoint

Evolize MCP server

No. Evolize answered an MCP handshake 56 minutes ago.

UpLast checked 56 minutes ago

Server URL

https://evolize.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.evolize/accessibility-scanner
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
469 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Accessibility scans with evidence, public reports, and fresh checks after fixes.
Listing
From the official MCP registry (active).
Recent checks of Evolize
CheckedResultHandshake
56 minutes agoHandshake completed469 ms
3 days agoHandshake completed110 ms
12 days agoHandshake completed506 ms
13 days agoHandshake completed161 ms
14 days agoHandshake completed193 ms
15 days agoHandshake completed151 ms
17 days agoHandshake completed238 ms
18 days agoHandshake completed237 ms
18 days agoHandshake completed91 ms
20 days agoHandshake completed198 ms
22 days agoHandshake completed90 ms
25 days agoHandshake completed244 ms
27 days agoHandshake completed341 ms
29 days agoHandshake completed147 ms

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