Failure Lab vs .NET MCP Server
Failure Lab lists no tools and runs locally and .NET MCP Server lists no tools.
| Fact | Failure Labio.github.anilloutombam/mcp-failure-lab | .NET MCP Serverio.github.jongalloway/dotnet-mcp |
|---|---|---|
| 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 | MIT |
| Latest version | 0.13.2 | 1.1.2 |
| Known advisories | 0 | 0 |
| 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 .NET MCP Server |
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 .NET MCP Server with others