MCP & Configuration

MCP Response Validator

Validate supplied released MCP response envelopes, tool content and structured output schemas.

Processed on our CPU server.Submitted input is processed for this run and is not stored.

256 KiB limit

Input

Paste your input or load an example,
then run the tool.

Supported formats & limitations

Released MCP 2025-11-25 schema is embedded from a pinned upstream revision, with its license and SHA-256 recorded. Only a single response object; no batches, requests, remote calls or rendering of content.
128 KiB response; shared depth/node/array limits. Result/error are mutually exclusive. Result IDs are strings/integers; error IDs may be absent in this released revision; null IDs are invalid.
tools/call validates all released content union shapes and object structuredContent. Optional object-root outputSchema checks structuredContent with the shared Draft 7/2020-12 engine and local references. null means no schema.
Protocol error envelopes skip output-schema checks with an explicit finding. Tool isError is an execution error marker, not a malformed response.
Unknown extension fields are allowed by the upstream schema. URI/base64/date format annotations, request correlation, capability negotiation and semantic correctness are outside coverage. Input text, images and resource URLs stay inert.
Server CPU processing with no input history or outbound requests. MCP access and public deployment remain separate launch tasks.

Execution budget: 5s; output limit: 4096 KiB. Browser worker startup has a separate 3s allowance.