Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Strac MCP DLP

PYPI · STRAC-MCP-DLP · SCANNED SEP 22

Detect and redact PII, PHI, PCI and secrets in text and files before an AI agent sees them.

Available components

+3 this week 58 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security50
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
  • 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 585 tokens (~117/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management63
  • Stability observed for 19 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Strac MCP DLP server?

Strac MCP DLP runs locally as a PyPI package, launched with uvx strac-mcp-dlp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · strac-mcp-dlp

# add to Claude Code
claude mcp add strac-io-strac-mcp-dlp -- uvx strac-mcp-dlp
// .cursor/mcp.json
{
  "mcpServers": {
    "strac-io-strac-mcp-dlp": {
      "command": "uvx",
      "args": [
        "strac-mcp-dlp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "strac-io-strac-mcp-dlp": {
      "command": "uvx",
      "args": [
        "strac-mcp-dlp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add strac-io-strac-mcp-dlp -- uvx strac-mcp-dlp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "strac-io-strac-mcp-dlp": {
      "type": "local",
      "command": [
        "uvx",
        "strac-mcp-dlp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add strac-io-strac-mcp-dlp --command uvx --arg strac-mcp-dlp
# ~/.hermes/config.yaml
mcp_servers:
  strac-io-strac-mcp-dlp:
    command: "uvx"
    args: ["strac-mcp-dlp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "strac-io-strac-mcp-dlp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "strac-mcp-dlp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add strac-io-strac-mcp-dlp -t stdio -c uvx -a strac-mcp-dlp
// mcp.json
{
  "mcpServers": {
    "strac-io-strac-mcp-dlp": {
      "command": "uvx",
      "args": [
        "strac-mcp-dlp"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Sept 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Sept 26 +4
    • Stability: unverified → 0.27 functional
  • 3 Sept 26 49

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 22 Sept 2026 · Analysed pypi/strac-mcp-dlp@0.1.1

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem pypi

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 32 packages
Packages resolved 32
No linked repository 1
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~420 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
detect_file ~70

Detect PII, PHI, PCI and secrets in a local file — image, PDF, scan or text. Strac runs OCR on images and scanned documents. Returns the data element types found, without modifying the file.

NameTypeReqDescription
include_matched_textboolean
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

detect_sensitive_data ~103

Detect sensitive data in text without changing it — personal data (PII), health data (PHI), payment and card data (PCI), and credentials such as API keys, cloud access keys, tokens and connection strings. Returns the data element types Strac found. Use this to decide whether text is safe to send onward; use redact_text when you need the sanitised text itself.

NameTypeReqDescription
include_matched_textboolean
textstringyes

Structured output declared, but exposes no named fields.

No examples provided.

detokenize ~72

Resolve Strac vault tokens (tkn_…) back to their original values. Use this only when the caller is authorised to see the raw sensitive data. Accepts up to 10 tokens per call and requires an IP-allowlisted server-to-server key in live mode.

NameTypeReqDescription
token_idsarrayyes

Structured output declared, but exposes no named fields.

No examples provided.

redact_file ~77

Redact PII, PHI, PCI and secrets out of a local file — image, PDF, scan or text — and write the redacted copy to disk. The original is never modified. Returns the path to the redacted file.

NameTypeReqDescription
output_path
overwriteboolean
pathstringyes

Structured output declared, but exposes no named fields.

No examples provided.

redact_text ~98

Redact PII, PHI, PCI and secrets out of a block of text using Strac DLP. Returns the redacted text plus the data element types that were found. Call this before putting untrusted or user-supplied text into a prompt, a log line, a ticket or any downstream system.

NameTypeReqDescription
include_matched_textboolean
redact_field_modestring
textstringyes

Structured output declared, but exposes no named fields.

No examples provided.

Common questions

What is the Strac MCP DLP server?

Strac MCP DLP is listed in the public MCP registry as io.github.strac-io/strac-mcp-dlp. Detect and redact PII, PHI, PCI and secrets in text and files before an AI agent sees them. This page covers its PyPI package (strac-mcp-dlp).

Is the Strac MCP DLP server safe to use?

Strac MCP DLP scores 58 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 September 2026. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the Strac MCP DLP server expose?

Strac MCP DLP exposes 5 tools: redact_text, detect_sensitive_data, detect_file, redact_file, detokenize. Their descriptions and schemas cost roughly 420 tokens of context every time the server is loaded.

Is the Strac MCP DLP server still maintained?

Strac MCP DLP is still listed as active in the MCP registry. We last reached this channel on 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.