Remote MCP · Endpoint

Axcess — Design Accessibility Evaluation MCP server

No. Axcess — Design Accessibility Evaluation answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://axcess-mcp-server.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.sicxz/axcess
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
40 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Evaluates UI designs for WCAG accessibility issues automated scanners miss. Paid via x402 on Base.
Listing
From the official MCP registry (active).
Recent checks of Axcess — Design Accessibility Evaluation
CheckedResultHandshake
1 hour agoHandshake completed40 ms
1 day agoHandshake completed108 ms
2 days agoHandshake completed42 ms
3 days agoHandshake completed33 ms
4 days agoHandshake completed46 ms
5 days agoHandshake completed29 ms
6 days agoHandshake completed41 ms
9 days agoHandshake completed77 ms
11 days agoHandshake completed44 ms
14 days agoHandshake completed29 ms
16 days agoHandshake completed31 ms
18 days agoHandshake completed34 ms
20 days agoHandshake completed31 ms
22 days agoHandshake completed34 ms
24 days agoHandshake completed23 ms
26 days agoHandshake completed30 ms
27 days agoHandshake completed35 ms
29 days agoHandshake completed42 ms

The last 18 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.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Axcess — Design Accessibility Evaluation and makes no claim about it beyond what these checks measured.