pseudonym-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": true
} |
| prompts | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| mask_textA | Pseudonymize sensitive entities in text before sending to a cloud LLM. Replaces national ID numbers, tax IDs, phone numbers, IBANs, cards and email addresses via regex, and person names and organization names via local Ollama NER — with opaque tokens like [PESEL:1], [PERSON:2], [ORG:1]. Every locale pack runs by default. The response reports active_locales, and disabled_locales plus a locale_warning whenever the server was narrowed with --lang and can therefore miss identifiers from other countries. Returns the masked text plus a session_id. Store the session_id to restore the original values later using unmask_text. |
| unmask_textA | Restore original sensitive values in text that was previously masked by mask_text. Replaces tokens like [PESEL:1], [PERSON:2] with the original values stored in the session identified by session_id. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| pseudonymize_task | Convenience workflow for masking text, running a task, and restoring originals. Not a privacy boundary for prompt arguments. |
| privacy_scan_file | Convenience workflow for OCR, masking, task execution, and restore. Not a privacy boundary for extracted prompt content. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 2 tools
The two tools have clearly opposite and distinct purposes: mask_text replaces sensitive entities with tokens, and unmask_text reverses that process. There is no overlap or ambiguity in their roles.
Both tools follow a consistent verb_noun pattern: mask_text and unmask_text. The prefix 'mask' versus 'unmask' clearly indicates the complementary action.
With only two tools, the server is minimal but appropriately scoped for its narrow purpose of pseudonymization and restoration. Though slightly below the typical 3-15 range, each tool is essential and earns its place.
The core lifecycle of pseudonymization is fully covered: masking and unmasking. The session_id mechanism enables restoration, and no additional operations are necessary for the stated purpose.