mahrem-mcp
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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_fileB | Scan local TXT, Markdown, DOCX or text PDF without returning raw values. Report extraction warnings. |
| mask_fileC | Mask local TXT/MD/DOCX/PDF to plain text. Detection is partial: human review is required. |
| restore_fileC | Restore placeholders into a local output file; never returns the restored clear text. |
| forget_sessionB | Erase one in-memory placeholder mapping after the restored file is created. |
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 4 tools
Each tool maps to a distinct stage in the masking workflow: scan for warnings, mask to produce placeholders, restore to reinsert values, and forget to clean up session state. Although scan and mask both operate on local files, their outputs and purposes are clearly differentiated.
All four names follow a consistent snake_case verb_noun pattern (scan_file, mask_file, restore_file, forget_session), making the set predictable and easy to navigate.
Four tools is well-scoped for a focused privacy-preserving file workflow; each tool earns its place without redundancy.
The set covers the core lifecycle of scan, mask, restore, and cleanup, but lacks any tool to list or inspect active sessions/placeholder mappings, which could be a minor gap for multi-file use.