Forensics MCP Server
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Forensics MCP Server check this file for hidden malware indicators"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Self-Assembling Forensic MCP Server (FastMCP / Python)
A modular Digital Forensics and Incident Response (DFIR) Model Context Protocol (MCP) server built with Python and FastMCP (mcp>=2.0.0).
It dynamically discovers host & container forensic utilities at startup and automatically self-assembles functional tools, resources, and triage prompts for local LLMs and AI agents (Ollama, Claude, Cursor, Antigravity, etc.).
π Features
π Dynamic Capability Discovery: Probes host environment paths, installed binaries (
exiftool,strings,volatility3,binwalk,tshark,objdump,gdb,yara), and Docker runtimes. Missing tools are gracefully reported without crashing.π§© Self-Assembling Tool Primitives: Automatically registers only the tools available in the host environment.
π‘οΈ Air-Gapped & Offline Ready: Built-in offline threat intelligence database with known sample signatures (EICAR, WannaCry, Mimikatz) for secure, zero-data-leakage incident response.
π Tamper-Evident Chain of Custody: Every tool execution, inspected artifact, SHA-256 checksum, and action parameter is cryptographically hashed and logged to an append-only ledger (
evidence/chain_of_custody.jsonl).π©Ί Self-Reporting Health & Resources: Real-time capability matrix (
forensics://capabilities), custody logs (forensics://custody), and system health (forensics://health).β‘ Dual Transport: Supports standard STDIO for native MCP clients (Cursor, Claude, Antigravity) and SSE/HTTP for web LLM agents (Ollama, Open WebUI).
Related MCP server: findevil-agent
π Quick Start
1. Prerequisites
Python 3.10+ (or uv)
2. Run the Server
Option A: Native STDIO Transport (For Local Agents / Cursor / Claude)
cd /home/b47m4n/Projects/forensics-mcp-framework
uv run src/server.pyOption B: SSE / HTTP Transport (For Web / Remote LLMs)
cd /home/b47m4n/Projects/forensics-mcp-framework
uv run src/server.py --transport sse --port 8000π Connecting to Local LLMs & Agents
1. Antigravity / Claude / Cursor (claude_desktop_config.json / mcp.json)
{
"mcpServers": {
"forensic-analyzer": {
"command": "uv",
"args": [
"--directory",
"/home/b47m4n/Projects/forensics-mcp-framework",
"run",
"src/server.py"
]
}
}
}2. Local LLM via Ollama + MCP
Connect your local model (e.g. llama3.1, qwen2.5-coder) via SSE endpoint:
http://localhost:8000/sse
π οΈ Discovered Tool Catalog
Tool | Category | Dynamic Condition | Description |
| Metadata & Files | Always Available | Computes hashes (MD5/SHA256), EXIF tags, and detects MIME mismatches |
| Static Analysis | Always Available | Extracts printable ASCII & Unicode strings |
| Threat Detection | Always Available | Scans for C2 URLs, IP addresses, Base64 blobs, command execution |
| Threat Intel | Always Available | Checks hashes against offline signatures and optional live APIs |
| Diagnostics | Always Available | Health status, storage check, and tool readiness |
| Memory Forensics |
| Volatility 3 |
| Memory Forensics |
| Volatility 3 |
| Memory Forensics |
| Volatility 3 |
| Memory Forensics |
| Volatility 3 |
| Memory Forensics |
| Volatility 3 |
| File Carving |
| Firmware signature and filesystem carving |
| Network Forensics |
| Dissects PCAP network packet captures |
| Reverse Eng |
| Disassembles binary machine instructions |
| Debugging |
| Automated batch debugging inspection |
| Signature Match |
| Scans evidence against YARA rule files |
π Project Architecture
forensics-mcp-framework/
βββ pyproject.toml
βββ .env.example
βββ README.md
βββ evidence/ # Evidence locker & chain of custody ledger
β βββ suspect_photo.jpg
β βββ eicar_test.com
β βββ chain_of_custody.jsonl
βββ src/
βββ server.py # Master FastMCP bootstrap & dynamic assembler
βββ core/
β βββ discovery.py # Host & container capability scanner
β βββ custody.py # Tamper-evident append-only chain of custody
β βββ health.py # System diagnostics & health reporter
βββ tools/
β βββ metadata.py # ExifTool & MIME mismatch detector
β βββ strings_ioc.py # String & IOC scanner (IP, URL, Base64, shell)
β βββ threat_intel.py # Offline/online threat intelligence
β βββ memory_vol.py # Volatility 3 memory analysis engine
β βββ dynamic_cli.py # CLI wrappers (binwalk, tshark, objdump, gdb)
βββ resources/
β βββ system_resources.py# MCP Resources
βββ prompts/
βββ triage_prompts.py # Structured DFIR workflowsAvailable Tools
5 toolscheck_threat_intelB
Queries threat intelligence databases (with safe offline fixture fallback) for a file hash.
Inputs: file_hash (required), case_id. Returns: result
extract_metadataB
Extracts file metadata, computes cryptographic hashes (MD5, SHA-1, SHA-256, SHA-512), and detects MIME-type masquerading.
Inputs: file_path (required), case_id. Returns: result
extract_stringsC
Extracts printable ASCII & Unicode strings from an evidence artifact.
Inputs: file_path (required), case_id, min_length, max_results, +1 more. Returns: result
scan_iocsC
Scans an evidence artifact for Indicators of Compromise: IPs, C2 URLs, email addresses, suspicious commands, and Base64 payloads.
Inputs: file_path (required), case_id. Returns: result
system_health_checkA
Inspects real-time host forensic capability readiness, storage, and chain-of-custody status.
Inputs: no named parameters. Returns: result
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelogβ¦
TDQS
Scored across 5 tools
Each tool targets a distinct forensic task: system readiness, metadata extraction, string extraction, IOC scanning, and threat intel lookup. There is no functional overlap, and the descriptions clearly delineate their purposes.
All tool names follow a consistent verb_noun pattern (e.g., system_health_check, extract_metadata, scan_iocs), using snake_case throughout. The naming is predictable and aligns with forensic terminology.
Five tools is appropriate for a forensic server covering host readiness, file analysis, and threat detection. Each tool serves a necessary function without redundancy or gaps in the core workflow.
The toolset covers essential forensic steps: health check, metadata extraction, string extraction, IOC scanning, and threat intel. A minor gap is the absence of a tool for parsing specific artifact types (e.g., registry hives or logs), but the set is sufficient for basic evidence triage.
Maintenance
Related MCP Connectors
Discover, invoke, and verify ForceDream agents with cryptographic proofs. 14 local, 21 hosted tools.
34 security tools for AI agents: phishing links, exposure maps, DNS, SSL, PQC, history, pivots.
Persistent memory and knowledge management for AI agents with semantic search and 50+ tools.
Agent tools for discovery, payment safety, data extraction, and DeFi.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to interface with Velociraptor for digital forensics and incident response tasks, including file/memory scans, remediation actions, and artifact collection across multiple operating systems.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous digital forensics and incident response through 21 typed forensic tools covering disk, memory, registry, network, timeline, carving, and patterns, integrated with AI-driven reasoning and self-correction.MIT
- AlicenseNot gradedqualityBmaintenanceEnables autonomous digital forensics and incident response by wrapping SIFT Workstation tools as MCP tools and orchestrating a multi-agent AI pipeline for evidence analysis and remediation planning.2MIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to analyze memory dumps for forensic investigation, leveraging a fast Rust engine and full Volatility3 plugin coverage via the Model Context Protocol.1MIT