MCP Recovery Lab
Related Servers
Alternatives to MCP Recovery Lab
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables testing AI agents against a scripted mock MCP endpoint where each tool call returns a chosen response, fails, hangs or drops the connection, and where assertions verify which tools were called, how often, in what order and with what arguments.318 npm2MIT
- 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-
- AlicenseAqualityCmaintenanceEnables MCP hosts that require a local stdio process to connect to the hosted public demo, forwarding tool discovery and calls for fictional scheduling scenarios, product information, draft-sharing preparation, and optional feedback.5MIT
- AlicenseNot gradedqualityCmaintenanceEnables locally configured MCP servers to be called over stdio and mixed with xAI server-side tools, without relying on hosted xAI MCP.MIT
- AlicenseNot gradedqualityCmaintenanceEnables launching a fixed clean or poisoned MCP test fixture over stdio so agents can be evaluated for task utility and resistance to malicious instructions embedded in tool results.1Apache 2.0
- AlicenseBqualityDmaintenanceEnables bounded, deterministic triage verdicts for server health, fleet status, and timeline investigation through a simulated execution-boundary MCP server.35MIT
TDQS
Scored across 1 tool
There is only one tool, so an agent cannot misselect or confuse it with anything else. Its purpose (look up a simulated order by ID) is stated unambiguously.
The single name 'lookup_order' follows a clear verb_noun snake_case convention. With one tool there is no deviation or mixing of styles to penalize.
A single tool is too thin for a server framed as a 'Recovery Lab' with an order domain; any lookup, listing, or recovery workflow would need more operations. The surface is scoped to one hardcoded action, which is an extreme mismatch for the stated purpose.
The tool only retrieves a single simulated order (ORD-100), with no list, create, update, cancel, or recovery operations. Agents hitting any other order or needing to act on an order reach a dead end.