What it does
A mock MCP server that deliberately exhibits non-standard or problematic behavior, designed as a test fixture for validating how MCP clients handle edge cases, misbehaving servers, and error conditions. Implements the MCP protocol surface but with intentional deviations or omissions to stress-test client robustness and error recovery paths.
Who it's for
MCP framework maintainers, testing engineers, and client library developers who need to validate error handling, timeouts, graceful degradation, and protocol compliance. Particularly useful for teams building MCP clients that must remain stable when encountering problematic or non-compliant servers.
Common use cases
- Test client resilience against servers that violate MCP spec or send malformed messages
- Validate timeout and cancellation handling under adverse conditions
- Verify graceful degradation when a server returns no tools or incomplete responses
- Integration test MCP client libraries for robustness without side effects or external dependencies
Setup pitfalls
- Install only in isolated test environments; not intended for production use
- Provides no actual MCP tools — useful only for testing client behavior
- Requires test isolation if multiple test suites share the same agent instance to prevent cross-contamination
- No CI infrastructure — verify test compatibility manually across target platforms and Node versions