Lazynext Accessibility Checker vs Failure Lab
Lazynext Accessibility Checker lists no tools and runs remotely and Failure Lab lists no tools and runs locally.
| Fact | Lazynext Accessibility Checkercom.lazynext/accessibility-checker | Failure Labio.github.anilloutombam/mcp-failure-lab |
|---|---|---|
| Score | Not checked yet | Not checked yet |
| Status | Not checked yet | Not checked yet |
| Tools | 0 | 0 |
| Can write data | No tools listed | No tools listed |
| Runs | Remote | Local |
| Needs first | – | Node.js |
| Licence | Not stated | MIT |
| Latest version | 1.0.0 | 0.13.2 |
| Known advisories | Not checked yet | 0 |
| Works in | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, oterm, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI | Claude Desktop, Claude Code, Cursor, VS Code, Devin Desktop, Zed, Cline, Continue, Goose, LM Studio, Gemini CLI, Codex, mcp-client-cli, oterm, TUUI, BoltAI, Agenvoy, Amp, AnythingLLM, Augment Code, Bob Shell, ECA, Kiro, Kiro CLI |
| Downloads last week | Not known | 290 |
| Install | Install Lazynext Accessibility Checker | Install Failure Lab |
Scores and status come with our own checks, which have not run on these servers yet. The rest is from the publishers' registry entries, package registries and advisory databases.
Compare Lazynext Accessibility Checker with othersCompare Failure Lab with others