DFA
This server does not currently have a deployable release on Glama. Follow the repository's setup instructions to install and configure it for your MCP client, including any required credentials and local dependencies.
DFA: Digital Forensics Anything
One MCP server for DFIR across memory, disk, timeline, and network evidence.
DFA connects your coding agent to forensic tools with a methodology-first workflow: evidence integrity outranks speed, every conclusion cites its evidence and its limitations, and every tool call is written to a hash-chained chain-of-custody log.
MVP (v0.1.0): memory forensics via Volatility 3. Disk (Sleuth Kit), timeline (plaso), YARA/EVTX providers and the evaluation harness are next. See ARCHITECTURE.md.
Quick start
# 1. Volatility 3 engine (the analysis backend)
python3 -m venv .venv && .venv/bin/pip install volatility3
export DFA_VOL_BIN="$PWD/.venv/bin/vol" # or put vol on PATH
# 2. DFA itself
npm install
npm run build
# 3. Check the engine
npx dfa-agents doctor
# 4. Register with your agent (Claude Code example)
# Add to your MCP config:
# { "command": "node", "args": ["/path/to/dfa/dist/main.js", "serve"] }Related MCP server: mem-forensics-mcp
Tools (MCP)
Tool | Purpose |
| OS / image metadata — run first ( |
| Process list / tree / hidden processes |
| Injected code regions |
| Sockets / connections |
| Cmdlines / loaded DLLs / file objects |
| Linux family: |
| Engine availability check |
| Verify custody hash chain |
| Generate the forensic HTML report |
All analysis tools are read-only against the image. Large outputs are truncated inline (200 rows); the full output is hashed into custody — cite the custody sequence number, not the truncated view.
Forensic report
dfa_report_generate (or dfa-agents report --out report.html) renders a
self-contained HTML report — no external resources, a restrictive CSP — with
six sections: case information, evidence inventory, chain-of-custody timeline,
methodology, findings, limitations. A banner shows chain integrity
(intact/broken) with the tip hash. Over MCP the tool takes a file name and
writes under ~/.dfa/reports/; neither path ever overwrites an existing file.
Print to PDF from the browser for a fixed copy.
Findings should cite custody seq numbers and state their limitations;
a finding without evidence does not enter the report.
Chain of custody
Every tool call appends a JSONL record to ~/.dfa/custody.jsonl
(override with DFA_CUSTODY_LOG):
seq | tool | argsHash | evidenceHash (image SHA-256) | outputHash | prevHash | hashEach record's hash chains to the previous one. dfa_custody_verify
re-walks the chain and reports the first broken link, if any.
Environment variables
Variable | Default | Purpose |
|
| Path to the Volatility 3 executable |
|
| dfa's own writable directory (custody log, reports, Volatility cache) |
|
| Custody audit log location |
|
| Where |
| (unset) | Extra Volatility symbol (ISF) directories, |
| (unset) | When set, memory images must resolve (realpath) under this directory |
Image SHA-256 hashes are cached per process by path + size + mtime, so repeated tool calls against the same image don't re-read gigabytes.
Skill
skills/dfir-investigate/ — install into your agent for the forensic
workflow: six-phase methodology, evidence discipline, and the
memory-forensics reference. It tells the agent when to use DFA and how to
report findings with limitations.
Development
npm run dev # tsx, stdio MCP on stdin/stdout
npm test # vitest
npm run build # tsc -> dist/Acknowledgements
Volatility 3, the memory analysis engine DFA drives.
REA (Reverse Engineer Anything), whose MCP design DFA benchmarks against.
License
MIT, see LICENSE.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
This server cannot be deployed
Maintenance
Related MCP Connectors
A paid remote MCP for agent memory MCP, built to return verdicts, receipts, usage logs, and audit-re
Zero-log MCP server with 49 tools for AI guardrails, secret scanning, MCP linting & EU compliance.
Hosted MCP server and Agent Skills for specs, engineering threads, and project memory.
Security scanner for MCP servers. Detect vulnerabilities, prompt injection, and tool poisoning.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceA production-grade, type-safe MCP server for memory forensics via Volatility 3, enabling LLM-assisted incident response without timeouts or evidence spoliation.1MIT
- AlicenseBqualityBmaintenanceMulti-tier memory forensics MCP server combining a fast Rust engine with Volatility3 coverage for analyzing memory dumps.1531 PyPI5MIT
- AlicenseBqualityDmaintenanceComprehensive forensic analysis MCP server enabling AI agents to analyze files, Chromium and Firefox browser artifacts, with VirusTotal, DIE, Binwalk integrations.51MIT
- FlicenseNot gradedqualityBmaintenanceEnables evidence-backed memory forensics through an official Volatility 3 installation, letting clients inventory memory images, discover plugins, run analyses with validated arguments, and read back saved outputs, execution records, and hashes. Runs locally over stdio with no model API key, keeping queries controlled and outputs preserved for citation.-