DEFAIR MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| list_casesB | List all forensic cases. Returns a list of cases with their case number, name, status, and creation date. Cases are ordered by creation date (newest first). |
| create_caseC | Create a new forensic investigation case. |
| get_caseB | Get details of a specific forensic case. |
| register_evidenceA | Register a new piece of evidence in a forensic case. Computes SHA-256 hash of the file and stores metadata. The original file is never modified or copied. |
| list_evidenceB | List registered evidence items. |
| get_evidenceC | Get details of a specific evidence item. |
| verify_evidenceA | Verify evidence integrity by re-computing its SHA-256 hash. Compares the current file hash against the hash stored at registration. This is a critical forensic operation to detect evidence tampering. |
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 7 tools
Each tool targets a distinct resource (case vs. evidence) and action (list, create, get, register, verify). The purposes are clear and non-overlapping, with no ambiguity in selection.
All tool names follow a consistent verb_noun pattern: list_cases, create_case, get_case, register_evidence, list_evidence, get_evidence, verify_evidence. This is predictable and easy to parse.
Seven tools are well-scoped for a forensic case management server, covering essential operations without redundancy. Each tool earns its place in the set.
The surface covers core case and evidence lifecycle operations, including creation, retrieval, listing, and integrity verification. However, it lacks update and delete operations for cases and evidence, which are common CRUD needs that could be required for full lifecycle management.