mcp-kymograph
recording schema 4 · rules v4

{{v.run}}

{{v.state}}
{{c}}

{{k.title}}

  1. {{l}}

{{k.foot}}

Exchanges

http_request · http_response · http_end, linked to the messages they carried
# Conn HTTP MCP Status Framing {{v.col}} Ended {{x.conn}} {{x.verb}} {{x.mcp}} {{x.status}} {{x.framing}} {{x.sess}} {{x.ended}} — {{v.skipLine}}

Exchange {{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
Signal Locator Path this run Exchange · framing normalized {{f.signal}}{{f.locator}}{{f.path}}{{f.where}}{{f.norm}}
{{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 endpoint event, no metadata URL is ever followed.
  • A framing error costs observation, not the connection. That connection goes verbatim; http_end says framing_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.