zero-trace-lite
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_pathA | Report supported leak patterns in a folder or a text file. Reads plain text only: home paths with a login name, common secret-key formats, inline passwords, database URIs with a password, secrets in .claude/settings*.json, e-mail addresses. Read-only. |
| scan_textA | Report supported leak patterns in a piece of text. Reads plain text only: home paths with a login name, common secret-key formats, inline passwords, database URIs with a password, secrets in .claude/settings*.json, e-mail addresses. Read-only. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
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.