Vestige
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| VESTIGE_DATA_DIR | No | Absolute path to the Vestige data directory | |
| VESTIGE_HTTP_HOST | No | Bind host for the streamable HTTP transport (e.g. "0.0.0.0"); required to enable HTTP mode via --http | |
| VESTIGE_HTTP_PORT | No | Bind port for the streamable HTTP transport (e.g. "8420"); clients connect to http://host:port/mcp | |
| VESTIGE_LOG_LEVEL | No | Log level for the server (e.g. "info") | |
| VESTIGE_HTTP_TOKEN | No | Bearer token required by the streamable HTTP transport for any non-loopback bind (constant-time compared) |
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
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vestige_register_targetA | Register a file or directory for analysis. Validates the path (canonicalization, symlink policy, allowed roots), computes SHA-256, and identifies the format. Read-only: the artifact is never modified. |
| vestige_list_targetsA | List all registered analysis targets with identity digests. |
| vestige_get_targetC | Get one registered target's metadata plus which providers support it. |
| vestige_list_providersA | List providers with capabilities and live availability (including installation guidance when a tool like Ghidra is missing). |
| vestige_analyzeA | Start an asynchronous analysis job on a registered target. Returns a jobId immediately; poll vestige_job_status. Progress notifications are sent when the client supplies a progressToken in _meta. |
| vestige_job_statusB | Get the status, progress, and result counts of an analysis job. |
| vestige_job_cancelB | Cancel a queued or running analysis job. Evidence already persisted is retained and the job becomes 'cancelled'. |
| vestige_list_findingsB | List evidence-linked findings for a target, optionally filtered by kind or confidence, with pagination. |
| vestige_get_evidenceA | Fetch one evidence record by id. Records are re-authenticated against their content digest before being served. |
| vestige_export_reportB | Export a deterministic markdown or JSON report for a target into the Vestige workspace and return its absolute path. |
| vestige_diagnosticsA | Report versions, configuration facts, data directories, and provider availability. Never contains secrets. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| vestige_investigate_target | Step-by-step investigation plan for a registered target using Vestige tools, with evidence-first guidance. |
| vestige_triage_javascript | Focused triage plan for JavaScript and Electron artifacts: entry points, IPC surface, routes, dependencies. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 11 tools
Each tool targets a distinct resource or action: target registration/listing/retrieval, provider discovery, asynchronous analysis, job status/cancellation, findings listing, evidence retrieval, report export, and diagnostics. Boundaries are clear, especially between starting an analysis and checking its job status.
Most tools use the consistent vestige_ prefix with verb_noun naming (register_target, list_targets, get_target, list_providers, list_findings, get_evidence, export_report). Minor deviations appear in vestige_analyze, vestige_diagnostics, and noun-first job operations (vestige_job_status, vestige_job_cancel), but the set remains predictable.
Eleven tools is well-scoped for an artifact analysis workflow, covering registration, provider discovery, asynchronous job control, findings/evidence access, reporting, and diagnostics without obvious padding.
The surface covers the core lifecycle from target registration through analysis, job monitoring, evidence/finding inspection, and report export. Minor gaps exist around target lifecycle management such as unregistering/removing registered targets, but agents can work around this.