Public log

redacta-mcp

MCP server that acts as a stateful privacy boundary: pseudonymises patient identifiers and PII before they reach an AI agent, keeps the reversal mapping outside the model context, and restores identifiers only at the trusted boundary. Runs locally, nothin

npm · fingerprint 331f3deea1e10cab56936520 · repository · RSS

7tools
1recorded versions
20mtracked
tracking started

What changed

Nothing, since tracking began. That is the good outcome, and it is what most servers look like.

Current tools

Show all 7 tool fingerprints
check_output
d091f7ee3eb0ea74
discard_session
790f076922155cfb
protect
469f1f5c1e41d3c7
redact
076fd283c6f6d134
reinstate
552008c726d12a31
release_to_file
2c75988cd934ac05
self_check
eb906ac0ec65bbe5

Watch this server yourself

If you run this server, put the proxy in front of it. It pins these exact fingerprints on first connect and stops the session if they move.

npx -y mcp-pin@0.2.3 -- <your redacta-mcp command>

Or subscribe to this page's RSS feed to be told when it changes.

Badge

mcp-pin status badge for redacta-mcp

The badge states one fact about time and nothing else. It never claims a server is safe.

[![mcp-pin](https://mcp-pin.gautamkhosla.com/badge/95bcf2f0f995fd68.svg)](https://mcp-pin.gautamkhosla.com/servers/95bcf2f0f995fd68.html)