MCPMischief – A misbehaving MCP server for client testing

A deliberately chaotic MCP server that helps developers test error handling in their MCP gateways and clients

Problem

Developers building MCP gateways or clients struggle to test edge cases because publicly available MCP servers are all well-behaved. One builder explicitly said they needed an MCP server that misbehaves (errors, disconnects, malformed data) to stress-test their own gateway, but couldn't find any. This testing gap means their products can crash when real-world MCP servers act unpredictably.

Solution

A configurable MCP server that can be triggered to produce various failure scenarios: malformed JSON, timeouts, disconnects, duplicate IDs, oversized payloads, rate limiting, protocol version mismatches, etc. It runs locally or hosted, includes test cases and log replay, so developers can reproduce issues repeatedly.

Users

Infrastructure engineers and indie developers building MCP gateways, AI agent frameworks, and multi-model routing layers.

MVP

Implement a locally runnable MCP server with 10+ failure modes (timeout, disconnect, error codes, malformed responses); provide a simple UI to toggle which failure to trigger; support probabilistic or rule-based triggering per request; output structured logs for correlating client behavior; publish Docker image and npm package for easy CI integration.

Revenue

Open-core with a paid hosted version (zero setup), team collaboration dashboard (shared test scenarios, history replay), and CI integration; subscription at $9-19/developer/month, or one-time $99 license.

Why now

MCP is becoming the de facto standard for AI agent-tool interaction, and many gateways and clients are emerging, but testing infrastructure is still primitive. An indie developer can quickly fill this gap with a lightweight tool that doesn't depend on large models.