Remote MCP · Endpoint

EuroA11y MCP server

No. EuroA11y answered an MCP handshake 39 minutes ago.

UpLast checked 39 minutes ago

Server URL

https://euroa11y.com/mcp

The last check completed an MCP handshake.

Registry name
com.euroa11y/euroa11y
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
250 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Accessibility audit of a web page (WCAG 2.2 AA, RGAA) and European Accessibility Act scope check
Listing
From the official MCP registry (active).
Recent checks of EuroA11y
CheckedResultHandshake
39 minutes agoHandshake completed250 ms
3 days agoHandshake completed567 ms
13 days agoHandshake completed446 ms
13 days agoHandshake completed291 ms
15 days agoHandshake completed435 ms
16 days agoHandshake completed314 ms
17 days agoHandshake completed311 ms
18 days agoHandshake completed456 ms
18 days agoHandshake completed405 ms
20 days agoHandshake completed408 ms
22 days agoHandshake completed352 ms
25 days agoHandshake completed665 ms
27 days agoHandshake completed331 ms

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

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