mcp-kymograph
tool 0.2.0 · source sha256:5e0b…a4d1
Corpus manifest

corpus.yaml

$ kymograph corpus check corpus.yaml
Read whole · 7 entries · 2 scenarios load manifest sha256:0f3e…92aa Every entry is pinned. Where each may run is decided by its provenance, before anything starts.
Refused whole — nothing starts · exit 2
  • entries[6].source.revision: "example/shell-tools@main" names a branch — a full 40-character commit id is required
  • entries[7].launch.transport: "http+sse" is not supported (stdio, streamable-http)
  • entries[2].scenarios[0]: ../scenarios/clock.yaml does not load — line 9: unknown key "postion"
A manifest is never read in part: one bad entry refuses all of them.

Entries and what they pin

server_version is the server’s own content, never the version it announces
Entry Source server_version Launch Scenarios May run under
{{e.name}}
{{e.prov}}
{{e.source}} {{e.version}}
{{e.versionNote}}
{{e.transport}}
{{e.launch}}
{{e.scenarios}}
{{i.mark}} {{i.name}}
{{e.isoNote}}

Provenance decides isolation

provenancehostruncrunsc (gVisor)remote reference✓✓—✕ poison✓✓—✕ real-world✕✕only here · not provided yetendpoint only · engagement

Refused, never downgraded. runc shares the host’s kernel: it keeps a server off the network, not off the kernel — which is why a real-world entry runs only under gVisor. A remote endpoint is not run here at all; its egress is not observed.

Reproduction triple — notes-legacy

"reproduction": { "entry": {"name": "notes-legacy", "server_version": "sha256:e0c41f…9a12", "launch": "sha256:6b20…d3f9", "transport": "streamable-http"}, "tool": {"version": "0.2.0", "source": "sha256:5e0b…a4d1"}, "scenario": {"name": "all-signals", "digest": "sha256:77b0d3…41ee"}, "environment": {"isolation": "runc", "sandbox_image": "sha256:4b1e9c…07ad", "target_image": "sha256:91fd2e…c3b0"}}
  • server_version: digest over sorted (relative path, file hash) pairs of exactly the files named — .git, __pycache__ and compiled files left out, symbolic links refused
  • The same bytes under another layout are another server; a change to Kymograph never moves it
  • The tool’s source digest moves between commits even when a development version does not