A11y Check vs APIShed
A side-by-side look at the A11y Check and APIShed MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
A
APIShedDeveloper ToolsValidates PESEL/NIP/REGON/IBAN/Luhn/ISBN/EAN/SWIFT-BIC/VAT; RPN calc, date math, hashing, tokens37FairAuth: not declaredVerdict: choose A11y Check for browser automation work as a local process; choose APIShed for developer tools. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose A11y Check when
- You need dedicated capabilities in the Browser Automation domain.
- You prefer a local stdio subprocess transport.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | A APIShed | |
|---|---|---|
| Category | Browser Automation | Developer Tools |
| Quality signal | 41/100 · Fair | 37/100 · Fair |
| Install command | Confirmed | Not confirmed yet |
| Transport | 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.
APIShed 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": {
"command": "npx",
"args": [
"-y",
"@a11ychk/mcp"
]
}
}
}
APIShed
No confirmed install command for APIShed yet — follow the setup steps linked from its listing page rather than a guessed package name.
Frequently asked questions
A11y Check is categorized under Browser Automation and uses a local stdio subprocess. APIShed belongs to Developer Tools and uses an install path we have not confirmed yet. Pick A11y Check for browser automation work and APIShed 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. APIShed has no confirmed install command yet — follow its own setup instructions.
A11y Check has no declared pricing — check the project's own site. APIShed 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 and apished 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 41/100 (Fair) with 1 views, 0 installs and 3 GitHub stars. APIShed has 37/100 (Fair) with 0 views, 0 installs and 0 GitHub stars.
