MCP Failure Lab
Related Servers
Alternatives to MCP Failure Lab
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceFault injection and reliability scoring for MCP servers. Scans tool output schemas, injects corrupted payloads, and measures contract enforceability. Model-free, deterministic, no LLM required.1419 PyPI1Apache 2.0
- AlicenseAqualityAmaintenanceConformance test harness for Model Context Protocol servers, validating JSON-RPC, transport, capability, schema, and more across multiple spec versions.12108 npmMIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server that breaks on demand, allowing you to test your client against auth failures, disappearing tools, flaky responses, and token expiry from a web UI.7 npm10MIT
- AlicenseNot gradedqualityBmaintenanceEnables reproducible testing of MCP client recovery behavior by injecting deterministic tool-call faults such as errors, delays, malformed results, and disconnects through a single probe tool.255 npmMIT
- FlicenseNot gradedqualityBmaintenanceEnables distributed multi-agent chaos latency injection and fault fuzzing, allowing MCP-compatible clients to inject network faults and retrieve structured execution telemetry.8-
- AlicenseNot gradedqualityDmaintenanceA comprehensive reference implementation demonstrating all features of the Model Context Protocol (MCP) specification, serving as documentation, learning resource, and testing tool for MCP implementations.1MIT
TDQS
Scored across 10 tools
Most tools target clearly distinct failure modes such as delay, disconnect, hang, malformed_message, and duplicate_response. However, ping and protocol_ping_liveness both concern liveness checking and could be confused, keeping this from a perfect score.
All tool names use consistent snake_case and are descriptive. The main deviation is grammatical style: some are bare verbs (delay, disconnect, hang, ping) while others are noun phrases (oversized_response, malformed_message).
Ten tools is well-scoped for a failure-injection lab. Each tool represents a distinct test scenario and none feels redundant or excessive.
The set covers core transport, protocol, timing, and cancellation failure modes, including oversized responses, malformed messages, duplicates, and post-cancellation responses. It lacks explicit injection of JSON-RPC error responses or invalid request IDs, which are common client-handling tests.