A11y Check vs Polyxd
A side-by-side look at the A11y Check and Polyxd MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
A11y CheckBrowser Automation · Remote HTTP/SSECheck a web page for accessibility problems in a real browser, with the code that fixes each one.43FairAuth: not declaredP
PolyxdDeveloper Tools · Local subprocess (stdio)Write Polyxd UI documents, check them, and show them as real screens in any design-system pack.41FairAuth: not declaredVerdict: choose A11y Check for browser automation work over a hosted endpoint; choose Polyxd for developer tools as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
AChoose A11y Check when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a remote HTTP/SSE transport.
PChoose Polyxd when
- You need dedicated capabilities in the Developer Tools domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A A11y Check | P Polyxd |
|---|---|---|
| Category | Browser Automation | Developer Tools |
| Quality signal | 43/100 · Fair | 41/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Local subprocess (stdio) |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing |
Tools & capabilities
A11y Check tools
No tool names declared yet. Check the project README from the listing page.
Polyxd tools
No tool names declared yet. Check the project README from the listing page.
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
A11y Check
{
"mcpServers": {
"a11y-check-2": {
"url": "https://nexaaly.com/mcp"
}
}
}
Polyxd
{
"mcpServers": {
"polyxd": {
"command": "npx",
"args": [
"-y",
"polyxd"
]
}
}
}
Frequently asked questions
A11y Check is categorized under Browser Automation and uses a remote HTTP/SSE transport. Polyxd belongs to Developer Tools and uses a local stdio subprocess. Pick A11y Check for browser automation work and Polyxd for developer tools.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
A11y Check has no declared pricing — check the project's own site. Polyxd has no declared pricing — check the project's own site. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add a11y-check-2 and polyxd as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, A11y Check has a quality signal of 43/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. Polyxd has 41/100 (Fair) with 0 views, 0 installs and 5 GitHub stars.