Skip to content
KitploitKITPLOIT
ToolsExploitsBlog
Log in
Submit
ToolsExploitsBlog
Submit

Hacking, PenTest, and Cybersecurity Tools for Your Security Arsenal!

Kitploit is a directory of hacking, cybersecurity, and pentesting tools. Discover the latest project updates to find vulnerabilities, analyze systems, automate testing, and strengthen your security.

FeedsContactPrivacy© 2026 Kitploit

Tool Directory

Categories

View all categories
Loading categories
Tools/GitHubGitHub/kowntaewook/mcptrace
Memory ForensicsForensicsInformation GatheringMalware AnalysisDigital ForensicsIncident ResponseAI SecurityLog Analysis
GitHubkowntaewook/mcptrace

MCPTrace

Volatility 3 plugin that carves MCP/JSON-RPC message candidates from Windows and Linux memory dumps, preserving raw bytes, addresses, and SHA-256 for verification.

20658 days agoNot yet reviewed
Share
View Repository

MCPTrace

Latest release: v0.3.0 · Release notes

Current source: post-v0.3.0 development; the changes below have not been tagged as a new release.

MCPTrace is a Volatility 3 plugin for extracting MCP/JSON-RPC message candidates from Windows and Linux memory dumps. It examines process memory for requests, responses, notifications, tool names, and call arguments, then records the recovered content together with its location in memory.

The project focuses on evidence that an analyst can inspect and verify. Each artifact retains its original bytes, process ID, virtual address, encoding, length, and SHA-256 hash. Results can be exported as JSONL for further analysis or comparison with other logs. MCPTrace operates on an acquired memory image and does not require an LLM or an external AI API.

Features

  • Extract UTF-8 and UTF-16LE JSON-RPC artifacts from readable process memory.
  • Identify MCP-related methods and response shapes, including tools/call names and arguments.
  • Show the observed MCP/LSP classification signals and flag conflicting initialize evidence.
  • Preserve original bytes and addresses for later verification against the image.
  • Suggest request/response relationships using the same PID and typed request ID.
  • Apply optional, analyst-defined rules to tool arguments, such as path or URL checks.
  • Export artifacts and per-process summaries, including unreadable bytes, errors, and search limits.
  • Summarize exported JSONL as a case report that checks raw-byte hashes and shows scan limitations.

The current analysis targets are Windows x64 and Linux x86-64. The plugin name refers to the operating system in the memory image, independently of the OS used to run Volatility.

How it works

MCPTrace uses Volatility's process enumeration and address translation. On Windows, it walks process Virtual Address Descriptors (VADs); on Linux, it walks Virtual Memory Areas (VMAs). These mappings define which process address ranges are examined. The two adapters share the same message-carving, correlation, policy, and export code.

Within readable ranges, the scanner searches for literal JSON-RPC version markers and locates candidate JSON objects around them. It handles nested objects, escaped characters, braces inside strings, and messages spanning contiguous read chunks. JSON with duplicate keys or unsupported identifiers is rejected rather than silently reinterpreted. MCP relevance is determined from known method names, response shapes, and associated request IDs; it is not full MCP schema validation.

The ProtocolHint and ClassificationReasons columns explain why an artifact was labeled mcp-candidate, lsp-candidate, ambiguous, or generic-json-rpc. JSONL exports carry the same information as protocol_hint and classification_reasons. A matching Content-Length header is reported as context, not treated as proof of LSP: HTTP and other transports can leave the same header in memory. Ambiguous objects are shown by default so their conflicting signals remain reviewable; use --include-rpc to inspect LSP and generic JSON-RPC artifacts as well. None of these hints proves transmission or execution.

Missing memory is kept missing. The reader does not fill gaps with zeroes or join bytes across separate VADs/VMAs. With --include-partial, unparsed fragments can be shown separately, without inventing missing IDs or arguments. Large unmapped ranges can be skipped using page-table information, and unreadable address ranges remain visible in the scan statistics.

Correlation is deliberately conservative. A numeric ID such as 1 is distinct from the string ID "1", and messages in different processes are not automatically linked. Multiple distinct representations associated with an ID are marked as ambiguous. Candidate relationships do not reconstruct a session, message direction, or execution timeline on their own.

Installation

Requires Python 3.10+. Installation includes the pinned framework dependency, volatility3==2.28.2. Keep the repository's plugins/ directory available: the Python package is installed with pip, while -p plugins loads the Volatility adapters.

git clone https://github.com/Kowntaewook/MCPTrace.git
cd MCPTrace
python -m venv .venv

Activate the environment for your shell:

  • Windows PowerShell: .\.venv\Scripts\Activate.ps1
  • Linux/macOS shell: source .venv/bin/activate

Then install MCPTrace:

python -m pip install .

Usage

Run the following examples from the repository root with the virtual environment active. Replace the image paths and PIDs with your evidence and target processes. MCP clients and servers may run in separate processes, so inspect both where relevant.

Windows

Check that Volatility can interpret the image and enumerate its processes before running MCPTrace. Windows symbol preparation may require network access.

vol -f windows.raw windows.info.Info
vol -f windows.raw windows.pslist.PsList
mkdir output-windows
vol -p plugins -f windows.raw -o output-windows windows.mcptrace.MCPTrace --pid 4242 5252 --dump

Linux

Place ISF symbols matching the dump's exact kernel build in symbols/linux/. If linux.pslist.PsList cannot resolve its kernel or layer requirements, resolve the image/symbol setup before interpreting MCPTrace output.

vol -s symbols -f linux.lime linux.pslist.PsList
mkdir output-linux
vol -p plugins -s symbols -f linux.lime -o output-linux linux.mcptrace.MCPTrace --pid 4242 --dump
  • Omit --pid to scan all processes, or pass multiple PIDs: --pid 4242 5252.
  • --dump exports per-process JSONL files to the directory specified by -o.
  • Use vol -p plugins windows.mcptrace.MCPTrace -h (or the Linux equivalent) for all options.

For a JSON rendering of the full result table, put the global -r json option before the plugin name. This is separate from the per-process JSONL exports produced by --dump.

vol -p plugins -f windows.raw -r json windows.mcptrace.MCPTrace --pid 4242 > findings.json

To create a content-minimized case summary from JSONL exports:

python -m mcptrace.report output-linux/mcptrace.pid-4242.jsonl --output case-report.json

The report checks exported raw-byte hashes and lengths, lists classification signals and scan limitations, and omits message bodies and arguments. It does not assign timestamps or prove that a recovered message was sent or executed. See the no-Windows validation record for the paired controlled-buffer comparison and its limits.

Common options

OptionPurpose
--pid 4242 5252Select process IDs; omit to examine all processes enumerated by the adapter.
--dumpExport displayed artifacts and scan summaries as JSONL using the global -o directory.
--include-partialInclude raw, unparsed fragments without reconstructing missing fields.
--include-rpcAlso display generic JSON-RPC candidates without confirmed MCP relevance.
--policy PATHApply local rules to tool arguments; see the Windows and Linux examples.
--suspicious-onlyShow policy matches and summaries; requires a nonempty policy.
--max-records NBound candidate records per process before filtering; default: 10000.
--max-object-bytes NBound the size of one complete JSON object; default: 65536 bytes.
--max-bytes NBound attempted address-range bytes per process; 0 means unlimited.
Download Tool

Most Popular

View all →

Discover the most used tools by our community.

  • 1

    OsintHunter

    letox4/osinthunter

    🎯 The ultimate OSINT toolkit: investigation graph, confidence scoring, alias families, map, timeline and reports. 49 modules, 400+ sites, no API keys required.

    906
  • 2

    ghostlock-app

    yukonga/ghostlock-app

    GhostLock One-Tap Execution App (CVE-2026-43499)

    725
  • 3

    looking-glass

    anonghosty/looking-glass

    CSIRT platform that ingests Shadowserver reports into MongoDB and replays them as interactive maps, analysis, findings, advisories and executive dashboards.

    442
  • 4

    wifit3

    derv82/wifit3

    Wifite but USB-only & cross-platform.

    434
  • 5

    jumpserver

    jumpserver/jumpserver

    JumpServer is an open-source Privileged Access Management (PAM) platform that provides DevOps and IT teams with on-demand and secure access to SSH, RDP, Kubernetes, Database and RemoteApp endpoints through a web browser.

    412
  • 6

    SafeLine

    chaitin/safeline

    Self-hosted WAF and reverse proxy that filters malicious HTTP traffic, blocks SQL injection, XSS, and bot attacks, with rate limiting and dynamic HTML/JS encryption.

    360

Explore all tools

Browse our collection of tools

View all tools →