MCP & Configuration
JSON-RPC Trace Checker
Pair requests and responses, inspect batches, and distinguish missing capture events from protocol errors.
Processed on our CPU server.Submitted input is processed for this run and is not stored.
1024 KiB limitInput
Result
A useful result starts here.
Paste your input or load an example,
then run the tool.
Supported formats & limitations
- JSON format is a chronological array of messages; a batch is an array nested within that capture. JSONL has one message or batch per line.
- Optional envelope: {"session":"name","message":object-or-batch,"timestamp":"supplied value"}. Each session represents one requester; otherwise session is default.
- String and numeric IDs are distinct; numeric spellings compare exactly by value. Null IDs are uncorrelated. Notifications require no response. Numeric ID spelling is limited to 128 characters and exponents between -1000 and 1000. Session names cannot contain NUL.
- Maximum 2,000 messages including batch members, 128 KiB per JSONL line, depth 48 and 24,000 JSON nodes. Reports cap findings at 200 and declare truncation.
- Partial capture turns missing/orphan responses into warnings; duplicate IDs, malformed envelopes and duplicate responses remain errors. No network requests.
Execution budget: 5s; output limit: 4096 KiB. Browser worker startup has a separate 3s allowance.