forensic-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| FORENSIC_MCP_AUDIT_LOG | No | Ruta del fichero JSONL de auditoría. Por defecto: audit/audit.jsonl. | |
| FORENSIC_MCP_EVIDENCE_ROOT | No | Directorio raíz externo permitido para las evidencias forenses. El servidor confina todos los accesos a esa raíz y rechaza cualquier ruta externa. |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| hash_evidence_fileA | Compute and optionally verify MD5 and SHA-256 hashes of a file or raw disk image in strict read-only mode, returning mandatory 6-field provenance. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only a single tool exposed, there is no possibility of confusing it with another; its purpose (hashing a file or disk image read-only with provenance) is unambiguous.
The single name hash_evidence_file follows a clear verb_noun snake_case convention and is self-descriptive.
One tool is far too thin for a forensic evidence server, which implies hashing, verification, manifest generation, and custody tracking. The surface is essentially a single operation.
Hashing with provenance is a solid core operation, but there is no batch/directory hashing, known-hash list comparison workflow, manifest or chain-of-custody output, or metadata extraction, leaving notable gaps for real forensic use.