secretscanner
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 |
|---|---|
| scan_secretsA | Escanea un directorio o archivo en busca de contraseñas, tokens y claves API hardcodeadas. Args: target_path: Ruta absoluta o relativa al archivo o carpeta que se desea analizar. Returns: Un resumen en texto plano de los secretos encontrados. |
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 1 tool
With only one tool, there is no ambiguity. The tool has a distinct purpose of scanning for secrets.
The single tool name 'scan_secrets' follows a clear verb_noun pattern, consistent within itself.
A single tool is appropriate for a focused secret scanning server, though it feels minimal.
The tool covers the core scanning functionality but lacks features like result filtering or detailed reports, leaving some gaps.