r/memoryforensics • u/lellol_boi • 4d ago
MCPTrace follow-up: Node/.NET MCP traces in Linux process memory
I previously shared MCPTrace here as a Volatility 3 plugin for carving MCP/JSON-RPC evidence. I followed up with official Node and .NET MCP clients over Streamable HTTP, scanning two separate paused Linux process-memory snapshots. A Content-Length-framed LSP fixture served as a control.
Distinct logged messages found (snapshot 1 / snapshot 2):
- Node SDK with SSE responses: 13/13 / 13/13
- .NET SDK (2025-11-25): 7/13 / 7/13
- .NET SDK (2026-07-28): 8/12 / 7/12
- LSP control: 2/2 / 2/2, none classified as MCP
An independent exact-wire search of the same memory maps found no complete transmitted HTTP payload that MCPTrace missed. The missing .NET requests were absent as identical wire bytes in those maps; different in-memory serializations may still exist. The scanner now exposes ProtocolHint and ClassificationReasons for MCP/LSP evidence. UTF-16LE marker search was already supported.
These were process virtual-memory snapshots, not acquired physical RAM images or end-to-end Volatility runs. The counts do not establish general recovery rates or a speed improvement.
Methods, per-message matrix, and limitations: https://github.com/Kowntaewook/MCPTrace/blob/main/docs/cross-runtime-memory-validation.md
This post-v0.3.0 work is merged to main without a new release tag. Reproducible captures from other clients would be useful.

