Failure Lab MCP Server

MCP Failure Lab

A chaos-engineering and resilience-testing toolkit for Model Context Protocol servers.

Documentation · Project page

Quick start

Run a real deterministic delay scenario without cloning the repository or installing the package globally:

npx mcp-failure-lab demo

Example output:

MCP Failure Lab — Demo
Running a real 500ms delay scenario...

Scenario: Deterministic delay demo
Outcome: success
Duration: ~500 ms
Assertions: passed

The exact duration may vary slightly between runs. No API key or external MCP server is required.

Display the available commands:

npx mcp-failure-lab --help

Start the built-in MCP server over stdio:

npx mcp-failure-lab serve

Or start a local Streamable HTTP endpoint:

npx mcp-failure-lab serve --transport http

Purpose

MCP Failure Lab helps server authors reproduce delays, hanging tools, cancellation, and transport loss in a deterministic way.

It provides controlled failure behavior for testing timeout handling, cancellation cleanup, transport-loss recovery, assertions, and CI outcomes.

Current scope

MCP Failure Lab runs deterministic JSON scenarios against its own built-in MCP server from the command line.

Available now:

• ping, delay, hang, and disconnect tools
• MCP communication over stdio and Streamable HTTP
• Code-first and JSON scenario definitions
• Outcome and maximum-duration assertions
• MCP result assertions
• Sequential observer calls for post-condition verification
• Console and JSON reporting
• Machine-readable command errors
• CI-friendly exit codes
• Unit, integration, and end-to-end tests

Not implemented:

• External MCP client orchestration
• Target-client adapters
• JUnit reporting
• Malformed-message, duplicate-response, and session-loss faults

MCP Failure Lab is not currently a general-purpose proxy or an external MCP client test orchestrator.

How it works

MCP Failure Lab runs deterministic scenarios through its built-in MCP client and server. A scenario invokes ping, delay, hang, or disconnect, records the observed outcome and duration, and evaluates the declared expectations.

Optional observer calls run sequentially on the same MCP client connection to verify post-conditions through a separate tool path.

See the architecture documentation for diagrams, responsibilities, and implementation boundaries.

Documentation

Full guides and references are available at mcplab.dev/docs.

• Getting started
• Scenarios
• Fault tools
• CLI reference
• Reporting
• Architecture
• Examples
• Troubleshooting

Requirements

• Node.js 22.19.0 or newer
• npm

Protocol compatibility

MCP Failure Lab targets MCP 2026-07-28 by default. Its CLI server uses the SDK v2 era-aware serving entries, and its built-in scenario client pins 2026-07-28 so modern behavior is exercised explicitly.

The server also accepts the 2025-11-25 initialization flow for compatibility. HTTP compatibility is stateless: each request receives a fresh server instance, and legacy session GET and DELETE operations are not supported. That path remains covered by integration tests, but new development targets 2026-07-28. The existing ping, delay, hang, and disconnect fault tools have the same user-facing behavior in both eras; protocol features that rely on server-initiated requests differ between eras and are outside these fault tools.

Installation

Run the package directly with npx:

npx mcp-failure-lab demo

No global installation is required.

To install the command globally:

npm install -g mcp-failure-lab

CLI

# Run the built-in demonstration
npx mcp-failure-lab demo

# Display command help
npx mcp-failure-lab --help

# Display the installed version
npx mcp-failure-lab --version

# Start the MCP server over stdio
npx mcp-failure-lab serve

# Start Streamable HTTP with local-safe defaults
npx mcp-failure-lab serve --transport http

# Override the HTTP endpoint explicitly
npx mcp-failure-lab serve --transport http --host localhost --port 4000 --path /mcp

The serve process waits for an MCP client. Press Ctrl+C to shut it down gracefully.

Streamable HTTP listens on http://127.0.0.1:3000/mcp by default. The server validates the request path plus Host and Origin headers. Binding another host is an explicit choice; this mode does not provide authentication or TLS, so do not expose it to an untrusted network. Put authentication and TLS termination in a trusted front end if remote access is required.

Run a scenario

Scenario files use JSON:

{
  "name": "bounded delay succeeds",
  "call": {
    "tool": "delay",
    "args": {
      "delayMs": 250
    }
  },
  "timeoutMs": 1000,
  "expect": {
    "outcome": "success",
    "maxDurationMs": 500
  }
}

From a repository checkout, run the included scenario:

npm run dev -- run examples/scenarios/delay-success.json

Generate machine-readable output:

npm run dev -- run examples/scenarios/delay-success.json --report json

The command exits with:

For result assertions, observer calls, reporting formats, and timeout behavior, see the scenario and reporting documentation.

Fault tools

See the fault tools reference for arguments and behavior.

Inspect the server

Launch MCP Inspector against the published package:

npx @modelcontextprotocol/inspector npx mcp-failure-lab serve

Connect over stdio, list the available tools, and invoke ping, delay, hang, or disconnect.

For Streamable HTTP, start the server separately and connect Inspector to http://127.0.0.1:3000/mcp.

Do not share or commit temporary authentication tokens included in Inspector URLs.

External integration validation

MCP Failure Lab was independently validated with a Future AGI simulation using an independent Python MCP client. The experiment invoked the real hang tool over stdio and applied a client-side timeout before evaluating simulated agent responses.

This is an external validation example, not an official Future AGI integration or endorsement.

See the Future AGI example for results and reproduction steps.

Development

Clone the repository and install its dependencies:

git clone https://github.com/anilloutombam/mcp-failure-lab.git
cd mcp-failure-lab
npm install

Run the development CLI:

npm run dev -- --help

Before opening a pull request, run:

npm run format:check
npm run typecheck
npm test
npm run build

See CONTRIBUTING.md for the contribution workflow.

Roadmap

Planned work is tracked in GitHub Issues.

Roadmap items are not part of the current implementation unless explicitly documented as available.

License

MIT