{{v.run}}
{{v.state}}{{k.title}}
- {{l}}
{{k.foot}}
Exchanges
http_request · http_response · http_end, linked to the messages they carriedExchange {{sel.n}}
{{sel.verb}} · {{sel.mcp}}request head · masked
{{sel.req}}
response head · masked
{{sel.res}}
body
{{sel.body}}
{{sel.note}}
Findings in this run
statements evaluated on what the server sent, before any rule{{v.noFindingsText}}
{{v.leftTitle}}
{{v.leftJson}}
verdict
{{v.verdictJson}}
What holds in every HTTP run
- The forwarding side parses HTTP, never MCP. Heads, Content-Length, chunk boundaries. JSON-RPC and SSE are parsed on a copy that cannot block it.
- One destination, fixed before the run. No redirect, no
endpointevent, no metadata URL is ever followed. - A framing error costs observation, not the connection. That connection goes verbatim;
http_endsaysframing_error. - A batch is one message event, each element inspected on its own, its index part of a finding’s path (2025-03-26 only).
- HTTP+SSE (2024-11-05) is refused at the manifest: it lets the server choose where the client sends.
- Counts are made where traffic is forwarded and written into run_finished — the cross-check that survives dropped events.