HANK SafeHarbor

HIPAA Safe Harbor de-identification for clinical notes and PDFs, detects the 18 identifiers and replaces each with a consistent, realistic fake instead of a redacted hole, so documents stay readable. Runs fully local, no PHI egress; over REST, MCP, and web.

API and MCP calls need an API key. Create a key or subscribe in the HANK Console.

The full API reference is generated from the service's own OpenAPI document.

Open the API referenceDownload the OpenAPI document

The server uses Streamable HTTP. Send your API key as a bearer token on every request. Tools use the safeharbor_<tool> name pattern.

claude mcp add safeharbor --transport http https://api.hank.ai/v1/safeharbor/mcp/ --header "Authorization: Bearer YOUR_API_KEY"

{
  "mcpServers": {
    "safeharbor": {
      "type": "http",
      "url": "https://api.hank.ai/v1/safeharbor/mcp/",
      "headers": {
        "Authorization": "Bearer YOUR_API_KEY"
      }
    }
  }
}

The live connect page has the same configuration with your key filled in.