Ocultar Pii

io.github.Edu963Published by GitHub account Edu963v0.1.2Updated Oct 24, 2026

Zero-egress PII redaction for Claude. Runs locally — no data leaves your infrastructure.

VerifiedSTDIODesktop onlySecurity & MonitoringAI & ML

Overview

AI-generated overview

A local MCP bridge to Ocultar, a PII/PHI masking engine that replaces personal data with reversible tokens before text reaches a cloud model.

What you can do
Mask text or JSON by replacing personal data such as names, emails, IDs, cards, phones and addresses with deterministic tokens, returning a hit report with the detected types and counts. Restore masked tokens to their originals from the local encrypted vault when an auditor token is configured. Manage the persistent entity registry, including seeding canonical names so variants map to the same token. Check the health and status of the local masking engine.
When to use it
Use it when prompts containing personal or health data must pass through a cloud LLM without the raw data leaving your infrastructure, and you want masking and controlled re-identification inside the assistant workflow.
Requirements
Runs as a local process (PyPI package ocultar-claude-mcp via Python, or an MCPB bundle) and needs a locally running Ocultar Refinery reachable at OCULTAR_URL. The refinery itself needs OCU_MASTER_KEY, OCU_SALT and OCU_AUDITOR_TOKEN; the MCP side uses OCULTAR_API_KEY and OCULTAR_AUDITOR_TOKEN, which must match the server's OCU_AUDITOR_TOKEN. Desktop only.
Before you install
The refinery logs each raw, unmasked prompt locally to the encrypted vault to support the audit diff view; leaving OCULTAR_AUDITOR_TOKEN unset disables reveal and the diff view. The reveal tool restores original personal data, so anyone holding the auditor token can unmask it. The vault and master key are sensitive secrets. Masking quality depends on the detection tiers, and Tier 2 NER only works with a compatible local sidecar.

Installation

In SourceWeft

  1. Open Ocultar Pii in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.