MCP Config, Requests & Apps Checker

Check Claude Desktop settings, MCP 2026 requests, and MCP Apps tool and UI resource metadata in your browser. No commands run or servers connected.

Input

Choose a JSON type to load its public example. Your edits stay in place when you change modes.

Choose JSON type

Result

Run immediately with the editable example.

Supported syntax and processing

Statically inspect Claude Desktop local settings, MCP 2026 request envelopes, and MCP Apps tool and UI resource metadata in your browser. Commands and HTML are not run, servers are not contacted, and input is not included in results or analytics.

Claude Desktop settings mode checks command/args/env shapes under mcpServers and Windows path escaping. MCP 2026-07-28 request mode checks the JSON-RPC request envelope and current protocol version and clientCapabilities in params._meta. MCP Apps tool mode checks _meta.ui.resourceUri and visibility in one tools/list tool object. UI resource mode checks the ui:// URI, HTML MIME type, text or base64 content, and optional CSP and permission fields in one resources/read contents item.

Input example

The MCP Apps tool mode starts with an example whose _meta.ui.resourceUri points to a ui:// resource. The UI resource mode loads a resources/read contents item with the same URI, the text/html;profile=mcp-app MIME type, and sample CSP and permissions. The two objects are checked separately; the live server link is not tested.

Supported range and boundaries

JSON input is limited to 50,000 characters. Settings mode allows 1–50 servers, commands up to 2,048 characters, up to 200 args of 2,048 characters each, and up to 100 env values of 8,192 characters. Request mode checks only part of the envelope. Apps mode checks a tool object and resource contents item separately, so it does not match the URIs or confirm the resource exists on a server. It does not validate HTML5, execute HTML, check host-specific CSP acceptance, connect to servers, validate full method schemas, or authenticate. Commands are not run and input values are not echoed.

Inputs and results stay in your browser. They are not saved or put in URLs or analytics. Leaving or refreshing the page restores the public example.

Frequently asked questions

What JSON should I paste in MCP Apps tool mode?

Paste one tool object from the tools array in a tools/list result. Its _meta.ui.resourceUri should be a ui:// URI pointing to the MCP Apps UI resource.

What JSON should I paste in UI resource mode?

Paste one UI resource item from the contents array in a resources/read result. Its URI must start with ui:// and its mimeType must be text/html;profile=mcp-app. The HTML is never executed.

Does this check whether the tool and resource URIs actually connect?

No. The two JSON objects are checked separately. This does not confirm that resourceUri exists on your server or that the tool and resource URIs match. No server or host is contacted.

Does this check whether CSP and browser permissions are safe?

It checks only the current MCP Apps field shapes: CSP string arrays and permission names and objects. It does not assess domain safety, HTML code, host-specific CSP behavior, or user permission grants.

Where are pasted settings and HTML sent?

Nowhere. JSON checks run only in your browser. Input such as server names, URIs, HTML, and CSP values is not repeated in results or included in analytics or URLs.

Calculation criteria and reference materials

Verification of calculation criteria: · Calculation·verification principles · Report errors