mcpanonimohealth
Related Servers
Alternatives to mcpanonimohealth
No user-submitted related servers found.
Related Servers
- AlicenseAqualityAmaintenanceAn MCP server that redacts PII/PHI from text before it ever reaches an LLM — self-hosted, fail-closed, and HIPAA-aware.3MIT
- AlicenseNot gradedqualityCmaintenanceA local MCP server for RGPD-compliant document Q&A, enabling Claude Code to ingest, query, search, delete, and audit personal documents entirely on-device.MIT
- AlicenseNot gradedqualityDmaintenanceA local, containerized MCP server that uses a local LLM to sanitize documents by removing or transforming PII before content is sent to public LLM services.MIT

omitly-mcpofficial
AlicenseAqualityBmaintenanceMCP server for local, verifiable PDF redaction. Enables AI agents to find sensitive regions, locate text, redact PDFs on-device, verify redaction and tamper-evidence seals, and generate PDFs—without uploading confidential documents.8272 npm-- AlicenseAqualityCmaintenanceMCP server and CLI for detecting, redacting, and auditing PHI in medical text before it reaches AI agents.4MIT
- AlicenseAqualityBmaintenanceMCP server providing on-prem PII detection and anonymization tools (scan and is_sensitive) for AI agents, ensuring data stays local.4MIT
TDQS
Scored across 6 tools
Each tool maps to a distinct workflow step: environment check, two different initiation methods (batch via folder selectors vs. localhost), status polling, result retrieval, and cleanup. The overlap between processar_lote_local and selecionar_e_desidentificar is resolved by their explicit input methods and return behavior, so no ambiguity remains.
All tool names use lowercase_with_underscores and follow an imperative verb pattern (verificar, processar, selecionar, consultar, obter, descartar). The only deviation is 'selecionar_e_desidentificar', which uses a compound verb phrase instead of a simple verb_noun, but the overall style is still consistent and predictable.
With six tools, the server is well-scoped for its purpose. Each tool is necessary to complete the anonymization workflow: readiness check, two processing triggers, polling, result retrieval, and cleanup. There is no redundancy or bloat.
The tool set provides a complete lifecycle for the anonymization process: verify environment, initiate processing (batch or localhost), monitor job status, retrieve the final text, and discard temporary data. No critical operation is missing for the stated domain.