Check keyed input response objects and requestState used when retrying an MCP operation after input_required.
On retry, inputResponses are keyed by the identifiers chosen by the server. Response values should be treated as untrusted input and requestState should be echoed exactly as supplied by the server.
Validate inputResponses and requestState sent when retrying an MCP Multi Round-Trip Request.
Use MCP Input Responses Validator as a focused pre-flight utility while building, reviewing or debugging an MCP integration. Paste the relevant configuration, protocol message, metadata, schema or value into the tool and review the returned findings before the same data reaches a production client or server.
Protocol checks are especially useful when debugging interoperability between different MCP clients, servers, gateways and SDK versions. The tool analyzes the data you provide and does not initiate a live MCP exchange.
A clean result means the input passed the rules implemented by this utility. It does not guarantee application security, protocol interoperability or correct business behavior. Test important integrations against the exact MCP client, SDK, gateway and server versions used in your deployment.