re-leak-scan
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 | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_leak_scanA | Return pattern-catalog summary + dependency availability. Always returns The optional |
| extract_stringsA | Extract printable ASCII and UTF-16LE strings from path. Args: path: file to scan min_length: minimum string length (default 8) max_strings: per-encoding cap (default 50,000) Returns a dict with On a 500+ MB GameAssembly.dll, prefer the section-aware
:func: |
| find_secretsA | Run the regex leak catalog over path's string table. Args:
path: file to scan
detector_set: comma-separated list of pattern names to apply
(default: all categories except the noisy Returns:: |
| scanA | Full pipeline: extract strings → apply all detectors → return findings. Convenience wrapper for the typical workflow. Equivalent to
Returns the same shape as :func: |
| verify_sentry_dsnA | Parse a Sentry DSN and (if Args:
dsn: a single Sentry DSN string (the full URL, including
the Returns:: The probe hits |
| verify_confluence_urlA | Probe a Confluence URL to confirm reachability + anon-access. Returns:: A 200 means the page is publicly readable (anon-accessible). A 401/403 means it's behind auth (still reachable). A connection error means unreachable. Note: this only checks the URL — the actual content of the Confluence page is the analyst's responsibility. |
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 6 tools
Most tools are distinct: check_leak_scan for status, extract_strings for raw extraction, find_secrets for catalog detection, scan as a wrapper, and verification tools for URLs/DSNs. However, find_secrets and scan overlap significantly, as scan is essentially a convenience wrapper for find_secrets with all detectors.
Tools predominantly use verb_noun snake_case (e.g., extract_strings, verify_confluence_url), but 'scan' is a bare verb, breaking the pattern. This minor inconsistency does not hinder readability.
With 6 tools, the set is well-scoped for a leak scanning server, covering status checking, string extraction, detection, full pipeline, and specific verifications. No unnecessary tools, and the count is appropriate for the domain.
The tool surface covers the core workflow: status check, extraction, detection, and verification for two common services. Minor gaps exist, such as pattern catalog management (listing/updating) and support for more service types, but essential operations are present.