Gandoki
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| X-OpenRouter-Key | No | Your OpenRouter API key, passed in the X-OpenRouter-Key HTTP header (BYOK). Used only for your specific scan request to enable the AI features; never logged, stored, or shared. |
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": true
} |
| logging | {} |
| prompts | {
"listChanged": true
} |
| resources | {
"subscribe": false,
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_domainsC | Scan a list of domains for exposed secrets and debug exposures. |
| scan_fileC | Scan a CSV or TXT domain list. |
| get_jobB | Fetch job status and (if done) its findings. |
| list_jobsC | List recent jobs. |
| get_findingC | Fetch a single finding by id (accepted or retracted). |
| explain_findingC | Explain a finding in plain language, keeping the honesty contract. |
| diff_jobsB | Compare ACCEPTED findings between two jobs (new / fixed / persisting). |
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 7 tools
Most tools are clearly distinct: the two scan tools differ by source (inline list vs. file), and job/finding retrieval tools are separated by granularity (list/get/diff). The only mild overlap is scan_domains vs. scan_file, which descriptions resolve adequately.
Every tool follows a consistent verb_noun snake_case pattern (scan_domains, get_job, list_jobs, diff_jobs, explain_finding). No mixed conventions or vague verbs.
Seven tools is well-scoped for a domain scanning and findings-review service, covering the full scan-to-inspect workflow without bloat or thinness.
Covers scanning, job inspection, finding retrieval, explanation, and cross-job diffing, which is a coherent lifecycle. Minor gaps: there is no tool to accept/retract findings even though get_finding references those states, and no job cancellation.