faultydata
Server Details
Cited, replayable HTTP failure signatures — test any HTTP client against real outages.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-06-18
- URL
- ChatGPT
- –
- Claude
- –
TDQS
Scored across 5 tools
Each tool targets a distinct action (list, detail, replay instructions, battery start, report score), so an agent can generally tell them apart. Minor overlap exists because get_specimen returns a 'replay signature' while replay_instructions separately explains replaying, which could cause slight confusion about where replay details live.
Four tools follow a clear verb_noun pattern (get_report, get_specimen, list_specimens, start_battery). replay_instructions breaks that pattern as a noun phrase, but the overall convention remains readable and predictable.
Five tools is well-scoped for a focused failure-specimen registry with battery scoring. Each tool clearly earns its place without redundancy or thinness.
The surface covers listing and fetching specimens, replay guidance, starting a battery, and scoring a report, which matches the core read/run workflow. Minor gaps exist around searching/filtering specimens or checking battery run status, but agents can work around them.
Available Tools
5 toolsget_reportCInspect
Score a battery session and return the report card.
Inputs: token (required).
get_specimenAInspect
Get a specimen's anatomy (the incident story), citation, and replay signature.
Inputs: id (required).
list_specimensAInspect
List every failure specimen in the FaultyData registry as a compact summary (id, title, category, severity, path, real-world flag, test tags). Use get_specimen for the full story and signature.
Inputs: no named parameters.
replay_instructionsBInspect
How to replay a specimen against a client-under-test (URL, curl, params for seed/key).
Inputs: id (required).
start_batteryAInspect
Mint a report-card battery token. The client then runs /run/{token}/{id} per specimen and reports outcomes.
Inputs: client.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Parallel-burst abuse testing for agent APIs with replayable evidence packs.
Keyless webhook endpoints: capture, wait, replay, forward, and generate types from real traffic.
End-to-end API testing — generate and run tests from OpenAPI, curl, Postman, or real user traffic.
Find real software, security and AI-agent failures that resemble your design, with safeguards.
Related MCP Servers
- AlicenseNot gradedqualityCmaintenanceLocal-first MCP and coding-agent reliability harness that captures bounded, sanitized failure evidence and generates deterministic executable regression tests. Capture is opt-in; no API key or hosted service is required.2Apache 2.0
- AlicenseAqualityCmaintenanceReplay-verified minimal JSON reproductions and deterministic TypeScript/OpenAPI drift checks. Local-first CLI and MCP server.283 npm1Mozilla Public 2.0
- AlicenseNot gradedqualityBmaintenanceEnables agents and developers to test HTTP client retry behavior against a synthetic service that emits 429/503 responses followed by 200, with Retry-After headers and server-observed attempt traces, plus optional sharing of synthetic evidence findings.MIT
- AlicenseCqualityBmaintenanceServes configurable fake service worlds as MCP tools with fault injection, recording every call and enabling seeded pytest assertions on final state.42Apache 2.0
Glama MCP Gateway
Add one secure layer between your agents and this server.