Skip to main content
Glama

Related Servers

Alternatives to MCP Failure Lab

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A 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 npm
      10
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables 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 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      A comprehensive reference implementation demonstrating all features of the Model Context Protocol (MCP) specification, serving as documentation, learning resource, and testing tool for MCP implementations.
      1
      MIT

    TDQS

    B3.3/5.0

    Scored across 10 tools

    Disambiguation4/5

    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.

    Naming Consistency4/5

    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).

    Tool Count5/5

    Ten tools is well-scoped for a failure-injection lab. Each tool represents a distinct test scenario and none feels redundant or excessive.

    Completeness4/5

    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.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week