A11y Check vs OrionCMD Checks
A side-by-side look at the A11y Check and OrionCMD Checks 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.42FairAuth: not declaredO
OrionCMD ChecksCommunication · Remote HTTP/SSEPay-per-call TLS certificate, DNS/email-auth and domain-expiry checks for any domain (x402 USDC).37FairAuth: not declaredVerdict: choose A11y Check for browser automation work over a hosted endpoint; choose OrionCMD Checks for communication over a hosted endpoint. 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.
OChoose OrionCMD Checks when
- You need dedicated capabilities in the Communication domain.
- You prefer a remote HTTP/SSE transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A A11y Check | O OrionCMD Checks |
|---|---|---|
| Category | Browser Automation | Communication |
| Quality signal | 42/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Confirmed |
| Transport | Remote HTTP/SSE | Remote HTTP/SSE |
| Auth | Not declared | Not declared |
| Pricing | Not declared | Paid service |
| 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 OrionCMD Checks |
Tools & capabilities
A11y Check tools
No tool names declared yet. Check the project README from the listing page.
OrionCMD Checks 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"
}
}
}
OrionCMD Checks
{
"mcpServers": {
"orioncmd-checks": {
"url": "https://api.orioncmd.com/llms.txt"
}
}
}
Frequently asked questions
A11y Check is categorized under Browser Automation and uses a remote HTTP/SSE transport. OrionCMD Checks belongs to Communication and uses a remote HTTP/SSE transport. Pick A11y Check for browser automation work and OrionCMD Checks for communication.
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. OrionCMD Checks is listed as a paid service. 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 orioncmd-checks 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 42/100 (Fair) with 1 views, 0 installs and 0 GitHub stars. OrionCMD Checks has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
