MCP / JSON-RPC Message Inspector
Checks Model Context Protocol traffic offline. Paste one JSON-RPC message, an array or JSON Lines and get structure checks for ids, initialize, tool schemas, tool calls, content blocks and errors.
Use the tool
Why this tool exists
When an MCP server and client do not agree, the failure is often a small shape error: a missing jsonrpc field, a null id, a tool whose required property is not declared, or a notification that carries an id. Reading raw logs for these is tedious. Paste a captured conversation here and each message is classified as a request, response, notification or error, then checked against the rules the protocol sets. Requests without a matching response are listed. It is an offline linter for logs and test fixtures, not a client: it cannot connect to a live server or test whether a tool works. Your messages stay in the browser, which helps when logs contain internal tool names.
How to use it
- Paste one JSON-RPC message, a JSON array of messages, or one message per line.
- Run the inspection to see each message classified and marked ok or PROBLEMS.
- Fix the listed problems in your server or client, and check any requests that have no response.
Frequently asked questions
What does it check?
It checks jsonrpc "2.0", request or response shape, ids, params, the required fields of initialize, tools/call, resources/read and prompts/get, tool names and inputSchema in tools/list results, content block types and error objects.
Can it test a live MCP server?
No. It only reads text you paste. It will not connect to a server, call a tool or check that responses are semantically correct.
How are mixed formats handled?
It first tries to parse the whole input as JSON, either one object or an array. If that fails it reads one JSON message per line and reports the line number of any parse error.
Why are null ids flagged?
MCP does not allow null request ids, so a null or non-string, non-number id is reported. Notifications must have no id at all.