Redacta
Related Servers
Alternatives to Redacta
- AlicenseAqualityBmaintenancePubCrawl provides LLMs with access to PubMed, FDA/UK drug labeling, and ClinicalTrials.gov. It enables searching literature, retrieving abstracts and full texts, comparing US and UK drug labels, and exploring clinical trials.14422 npm15MIT
- AlicenseAqualityBmaintenanceDeployment-readiness harness for AI document-QA and extraction systems. Scaffolds grounding checks, privacy redaction and cost tracking into a project, composing OpenGATE, Redacta and PubCrawl.550 npm1MIT
Related Servers
- FlicenseAqualityBmaintenancePII sanitization layer for autonomous AI agent pipelines. Detects and redacts emails, phone numbers, national IDs, private keys, and financial data before text reaches LLMs. Supports EN, ES (LATAM), PT (BR/PT), DE, JA.12-
- AlicenseAqualityBmaintenanceZero-dependency in-memory PII airgap & reversible masking proxy for Cloud LLMs (GDPR Art. 32 compliant).44Apache 2.0
- AlicenseAqualityBmaintenanceLocal pseudonymisation MCP server that detects PII in text, replaces it with opaque tokens before sending to cloud LLMs, and restores tokens afterward.2163 npm2MIT
- AlicenseNot gradedqualityBmaintenanceEnables irreversible anonymisation of documents and spreadsheets (PDF, Word, PowerPoint, HTML, Excel, CSV) into consistent pseudonymised Markdown before they reach an AI, keeping names, national IDs, bank details and contact data unrecoverable. Runs as a free online HTTP endpoint needing no key, or locally with the full engine bundled so nothing leaves the machine.MIT
- FlicenseNot gradedqualityBmaintenanceEnables reversible anonymization of SSNs, credit cards, passport numbers, emails, and phone numbers in prompts before sending them to external LLMs, and restores original tokens from completions using local HMAC isolation.7-
- FlicenseNot gradedqualityBmaintenanceEnables reversible anonymization of sensitive PII such as SSNs, credit cards, passport numbers, emails, and phone numbers before sending prompts to external LLMs, then restores original values locally using HMAC isolation.7-
TDQS
Scored across 7 tools
Each tool has a clearly distinct purpose: protect vs redact are differentiated by legacy status and return behavior, release_to_file vs reinstate by client vs server-side mapping, plus check_output, discard_session, and self_check each occupy unique roles. No ambiguity in selection.
All tools use snake_case and a verb-first pattern, though the structure varies (protect, release_to_file, check_output, discard_session, redact, reinstate, self_check). The legacy tools follow the same style but the naming is consistent enough to be predictable.
Seven tools is well-scoped for a redaction/restoration server: core redaction, restoration, leakage checking, session management, and legacy compatibility all have dedicated tools without bloating the surface.
The full lifecycle is covered: redaction (protect), restoration (release_to_file), output verification (check_output), session cleanup (discard_session), and leftover scanning (self_check), plus legacy paths. No obvious gaps for the intended domain.