Parse stdio and SSE log streams, inspect JSON-RPC 2.0 message frames, trace tool execution latency (ms), debug protocol warnings, and auto-mask leaked API credentials for Claude Desktop, Cursor, Zed, and WebMCP servers.
8
6 valid JSON-RPC 2.063ms
across 2 response cycles2
auto-masked in browser0
JSON-RPC / spec warnings2026-10-16T10:15:00.100Z [INFO] stdio rx: {"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2024-11-05","capabilities":{},"clientInfo":{"name":"ClaudeDesktop","version":"1.2.0"}}}
2026-10-16T10:15:00.145Z [INFO] stdio tx: {"jsonrpc":"2.0","id":1,"result":{"protocolVersion":"2024-11-05","capabilities":{"tools":{}},"serverInfo":{"name":"FilesystemMCP","version":"2.1.0"}}}
2026-10-16T10:15:00.150Z [INFO] stdio rx: {"jsonrpc":"2.0","method":"notifications/initialized"}
2026-10-16T10:15:01.000Z [INFO] stdio rx: {"jsonrpc":"2.0","id":2,"method":"tools/list","params":{}}
2026-10-16T10:15:01.080Z [INFO] stdio tx: {"jsonrpc":"2.0","id":2,"result":{"tools":[{"name":"read_file","description":"Read local file content","inputSchema":{"type":"object","properties":{"path":{"type":"string"}}}}]}}
2026-10-16T10:15:02.300Z [INFO] stdio rx: {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"read_file","arguments":{"path":"/Users/himat/secrets/config.env"}}}
2026-10-16T10:15:02.550Z [INFO] stdio tx: {"jsonrpc":"2.0","id":3,"result":{"content":[{"type":"text","text":"API_KEY=[REDACTED_SECRET]
DATABASE_URL=[REDACTED_SECRET]
Paste raw stdout/stderr logs from Claude Desktop, Cursor, Zed, or SSE network streams, or choose a pre-configured sample preset.
Analyze parsed JSON-RPC 2.0 frames, audit protocol spec compliance, filter by method (`tools/call`), and review execution latency waterfalls.
Auto-redact API tokens (`sk-`, `ghp_`, Bearer) and export sanitized log outputs directly to your machine or clipboard with 1-click.
Zero backend uploads. All MCP stdio/SSE log dumps, internal request paths, parameters, and secret tokens are parsed strictly inside local browser memory.
Automatically parses raw stdio output, line-delimited JSON-RPC 2.0 log files, and Server-Sent Events (SSE) streams into structured execution frames.
Renders visual execution waterfalls detailing duration (ms), pending tool calls, sequential initialize handshakes, and response latencies.
Pinpoints spec errors (-32700 Parse error, -32600 Invalid Request, -32601 Method not found, -32602 Invalid params) with line-by-line diagnostic hints.
Scans log streams for sensitive credentials (sk-, ghp_, Bearer, database connection strings) and auto-redacts them before exporting.
Filter logs by method (tools/call, initialize, resources/read) or log level (Info, Warning, Error), and export clean sanitized logs with one click.
HiMat's MCP Log Analyzer operates 100% locally inside client web browser memory. Neither your raw stdio dumps, file paths, tool arguments, nor API keys are ever transmitted over the network.
It is a browser-local debugging and performance analysis tool for Model Context Protocol (MCP) server logs. It parses stdio/SSE JSON-RPC 2.0 message streams, visualizes latency waterfalls, highlights protocol errors, and redacts sensitive API credentials.
No. The HiMat MCP Log Analyzer operates 100% locally in your web browser. Neither your stdio log outputs, file paths, tool arguments, nor API credentials ever leave your machine.
Our tool supports stdio and SSE logs generated by Claude Desktop, Cursor, Zed, Windsurf, and custom MCP server runtimes in TypeScript or Python.
Our local scanner inspects string tokens across log entries for known credential signatures (such as sk-, ghp_, Bearer tokens) and replaces them with [REDACTED_API_KEY] to prevent accidental token leakage.
Yes, 100% free with no account registration required, no usage limits, and zero advertisements.
HiMat Technologies designs production AI agent pipelines, custom Model Context Protocol servers, multi-agent orchestration engines, and 21-day fixed-scope AI pilots with complete source code ownership.
Continue with related utilities, services, and guides from HiMat.