memory_analyze_imageLABSCO SUMMARY
Volatility3's coverage with a fast path in front of it.
The three-tier routing is the design: pslist, malfind, netscan and similar go to the Rust engine, the analysis tools sit in Python, and anything else falls through to Volatility3 so nothing is lost. Check the status call first — which tiers are available depends on what your install picked up.
What it is
A Python MCP server for memory forensics that routes each tool across three engines — a Rust child process (memoxide), Python analyzers, and Volatility3 — picking the fastest backend that covers the request.
What you get
- A memory image loaded and analysed, with session state tracked and listed across an investigation
- A full triage pass over an image, for when you need the shape of it before the detail
- Process work: the process tree, command history, and hunting for process anomalies
- Threat hunting: injected code found, C2 connections identified, and credentials extracted, with YARA and VirusTotal integration on the Python tier
- Artifacts recovered — a process dumped, a VAD region dumped, and dumpable files listed
- Any Volatility3 plugin run directly, with the available plugins listed, covering filescan, handles, svcscan, driverscan and the rest
- Server status reported, so you can see which engines are actually available before relying on one
Requirements
A recent Python with uv, and a memory image on disk. Prebuilt Rust binaries ship for aarch64-linux and x86_64-linux and are auto-detected; Volatility3 is auto-detected at /opt/volatility3, or you point the server at wherever yours lives. The full install brings YARA and VirusTotal support; the minimal one is Volatility3 only.
Setup effort
One command — uv pip install mem-forensics-mcp
USE CASES
Getting oriented on an image you were just handed
Load it and run the full triage pass before deciding which thread to pull.
Finding the process that should not be there
Read the process tree, then hunt for anomalies rather than eyeballing the list.
Confirming code injection
Search for injected code in the image and dump the VAD region behind the finding for closer analysis.
Identifying command and control
Surface the C2 connections held in memory alongside the command history that led to them.
Working out what the attacker took
Extract credentials present in memory, and dump the process holding them for the report.
Reaching for a plugin the wrappers do not cover
List the available Volatility3 plugins and run the one you need directly.
19 tools
Listed in project docs. Your client may show a different list.
memory_run_pluginmemory_list_pluginsmemory_list_sessionsmemory_get_statusmemory_full_triagememory_hunt_process_anomaliesmemory_get_process_treememory_find_injected_codememory_find_c2_connectionsmemory_get_command_historymemory_extract_credentialsmemory_dump_processmemory_dump_vadmemory_list_dumpable_filesvt_lookup_hashvt_lookup_ipvt_lookup_domainvt_lookup_fileBEFORE YOU INSTALL
What to know first
Tools you get
19 tools named in the project's documentation.
INSTALLATION
Connect your client
Server setup
uv pip install mem-forensics-mcpMCP Clients
Claude Code
claude mcp add mem-forensics-mcp \
--scope user \
-- uv run --directory /opt/mem_forensics-mcp python -m mem_forensics_mcp.server