A side-by-side look at the A11y Check and Tudetic Product Search MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose A11y Check for browser automation work over a hosted endpoint; choose Tudetic Product Search for developer tools. You can also run both side by side in one mcpServers block.
Rows where the two servers differ are marked.
| Spec | A A11y Check | T Tudetic Product Search |
|---|---|---|
| Category | Browser Automation | Developer Tools |
| Quality signal | 43/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | Remote HTTP/SSE | — |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | None listed | None listed |
| Verified owner | Community listing | Community listing |
| GitHub stars | — | — |
| Directory activity | 1 views 0 installs 0 upvotes | 0 views 0 installs 0 upvotes |
| Tools | Not listed | Not listed |
| Full listing | View A11y Check | View Tudetic Product Search |
No tool names declared yet. Check the project README from the listing page.
No tool names declared yet. Check the project README from the listing page.
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.
{
"mcpServers": {
"a11y-check-2": {
"url": "https://nexaaly.com/mcp"
}
}
}
No confirmed install command for Tudetic Product Search yet — follow the setup steps linked from its listing page rather than a guessed package name.