Failure Lab vs Periphery Code Audit
Failure Lab lists no tools and runs locally and Periphery Code Audit lists no tools.
| Fact | Failure Labio.github.anilloutombam/mcp-failure-lab | Periphery Code Auditio.github.zyntx-lab/periphery-mcp-server |
|---|---|---|
| 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 | Local | Not known |
| Needs first | Node.js | – |
| Licence | MIT | Not stated |
| Latest version | 0.13.2 | 1.0.0 |
| Known advisories | 0 | Not checked yet |
| Works in | 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 | No install config |
| Downloads last week | 290 | Not known |
| Install | Install Failure Lab | Install Periphery Code Audit |
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 Failure Lab with othersCompare Periphery Code Audit with others