phi-guard-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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_phiB | Detect PHI-like identifiers and return structured findings. |
| redact_phiB | Detect and redact PHI-like identifiers with placeholders. |
| audit_deidentificationB | Return an audit-oriented summary of PHI-like identifiers and limitations. |
| validate_no_phiB | Validate whether text has no detected PHI-like identifiers. |
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 serves a distinct purpose: scanning, redacting, validating absence, and auditing. There is no overlap in function.
Tools follow a verb_phi or verb_deidentification pattern, but 'audit_deidentification' uses a different noun than the others ('phi'), causing slight inconsistency.
Four tools is appropriate for a focused PHI detection/redaction server. It covers key operations without excess.
The set covers detection, redaction, validation, and audit. A minor gap is the lack of a tool to manage or customize identifier patterns, but the core workflow is complete.