zero-trace-lite
Related Servers
Alternatives to zero-trace-lite
No user-submitted related servers found.
Related Servers
AlicenseNot gradedqualityAmaintenanceLets your assistant check text for credentials and personal details before passing it to another tool. Runs on your device over stdio and makes no network calls.39AGPL 3.0- AlicenseNot gradedqualityBmaintenanceEnables an agent to scan text for leaked credentials locally before it writes or commits it, flagging known key, token, private-key and sensitive-filename patterns with redacted, line-level findings and no network calls. Detection is deliberately specific to avoid false positives that would block unattended agents.MIT
- AlicenseAqualityDmaintenanceScans diffs, files, and snippets for leaked secrets like AWS keys, GitHub tokens, and private keys, returning redacted findings while running fully locally without network calls.1MIT
- AlicenseNot gradedqualityCmaintenanceScans text and files for common secrets (AWS, GitHub, etc.) and redacts them to prevent credential leakage in AI-assisted development. Runs entirely locally with no telemetry.MIT

Skarnofficial
AlicenseNot gradedqualityBmaintenanceScans AI coding sessions and assistant configs for leaked secrets and risky hooks; local, redacted37MIT- AlicenseNot gradedqualityCmaintenanceRead-only scanner that finds leaked secrets in MCP client configs, agent logs and shell history without printing values.Apache 2.0
TDQS
Scored across 2 tools
The two tools differ by input source: scan_path takes a folder or file, while scan_text takes an inline string. The descriptions make this boundary explicit, though the tool names could sound more distinct since both perform the same underlying scan.
Both names use the same verb_noun snake_case pattern and start with the same verb, scan, so they form a completely predictable pair.
A lite, read-only leak scanner can reasonably be this small, but with only two closely related tools the surface feels thin. It is unlikely that routing many inputs needs more than these two tools.
The scanner covers detection for paths and text, the two main input shapes, but the lifecycle stops at reporting. There is no way to redact or export findings, list or configure supported patterns, or scan non-text sources, which are visible gaps for a leak-scanning domain.