mcp server
a11y-check
Real-browser WCAG audit that also finds keyboard-inoperable controls axe-core misses, with fixes.
Description as published by the maintainer. Source
- version 1.2.0
- active
- browser automation
active — Registry entry last updated 2026-07-31. Dashed tags are derived by ZBS Index from the published description, not stated by the maintainer.
What this server can do
The endpoint published in the registry did not answer (HTTP 410). The listing points at a server that is not running. The functions below are the last successful declaration, not a fresh answer.
Endpoint status observed on . Source: https://nexaaly.com/mcp.
1 function, named and described by the server itself. Parameter names are shown because they say more about what a function does than its name usually does.
check_accessibility(url)- Audit one web page for accessibility problems using a real browser. Runs axe-core (WCAG 2.1 AA) plus checks that standard scanners do not perform: controls that look clickable but cannot be operated by keyboard, error messages not programmatically linked to their field, CAPTCHA barriers, duplicate main landmarks, and missing skip links. Returns findings WITH the code change that fixes each one. Use this when someone asks whether a site is accessible, whether it meets WCAG or the European Accessibility Act, or whether keyboard and screen-reader users can operate its controls. Required: url.
Last successful function declaration observed on . Source: https://nexaaly.com/mcp. We list what the server declared; we do not call any of these functions.
Signals
These are separate measurements of different things. They are deliberately not combined into one score, because a popularity number that mixes website traffic with saves and stars cannot be checked or acted on.
| Signal | Value | What it measures | Window | Observed | Source |
|---|---|---|---|---|---|
| Latest published version | 1.2.0 | Latest version string the maintainer published to the registry. | as of fetch | Model Context Protocol | |
| Registry record last updated | 2026-07-31 | When the registry record was last updated by its maintainer. | point in time | Model Context Protocol | |
| First listed in the MCP Registry | 2026-07-31 | Date this server was first published to the official MCP Registry. Not a usage or quality measure. | point in time | Model Context Protocol | |
| mcp tools declared | 1 tools | Number of functions the server itself declared when asked to list them. This is what the server offers an agent, not a measure of how well any of them work. | as of probe | nexaaly.com | |
| mcp endpoint status | unreachable | The endpoint published in the registry did not answer (HTTP 410). The listing points at a server that is not running. | as of probe | nexaaly.com |
Where to get it
This record as data
Every field on this page, with its source and observation date, is in the catalog JSON. Fetch the whole kind at once instead of parsing this HTML.
GET /api/v1/entries/mcp_server.json