Skip to main content
Glama

Related Servers

Alternatives to Redacta

  • A
    license
    A
    quality
    A
    maintenance
    PubCrawl 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.
    2
    14
    158 npm
    14
    MIT
  • A
    license
    A
    quality
    A
    maintenance
    Deployment-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.
    2
    5
    53 npm
    1
    MIT

Related Servers

  • A
    license
    A
    quality
    A
    maintenance
    Local pseudonymisation MCP server that detects PII in text, replaces it with opaque tokens before sending to cloud LLMs, and restores tokens afterward.
    2
    56 npm
    2
    MIT
  • A
    license
    Not graded
    quality
    C
    maintenance
    Enables local, in-memory de-identification of PII, PHI, and credentials with deterministic reversible surrogate tokens before LLM transmission, then restores originals from volatile session mappings and audits for exposures without network egress or disk writes.
    577 npm
    Apache 2.0
  • A
    license
    Not graded
    quality
    C
    maintenance
    Strips personal data and credentials from text before it reaches a model, log, or ticket, using checksum-verified detection for cards, IBANs, routing numbers, SSNs, contact details, and API keys. Placeholders such as <EMAIL_1> can later be swapped back in so the model's response is restored with the original values.
    2 npm
    MIT
  • F
    license
    A
    quality
    C
    maintenance
    Detects and redacts sensitive personal information such as names, emails, phone numbers, ID numbers, and locations in text before it is processed by AI agents, using configurable mask, hash, or remove strategies.
    1
    -

TDQS

A4.4/5.0

Scored across 7 tools

Disambiguation5/5

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.

Naming Consistency4/5

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.

Tool Count5/5

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.

Completeness5/5

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.

Maintenance

ActivityActive
ResponsivenessNo issues