Vestige
Related Servers
Alternatives to Vestige
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityNot gradedmaintenanceEnables AI agents to inspect and reverse engineer local software targets, including binaries, JavaScript/Electron apps, .NET assemblies, and websites, returning evidence-backed findings for understanding and building similar features.519,887 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents (and a matching CLI) to inspect native binaries, JavaScript/Electron apps, .NET assemblies, Go/Rust/WASM artifacts, EVM bytecode, SQLite databases, recorded crashes, and websites without source code, explaining how features work and returning the evidence and limitations behind each conclusion. Analysis runs locally, using optional Hopper, Ghidra, or IDA providers for native targets.519,887 npmMIT
- AlicenseNot gradedqualityAmaintenanceEnables MCP-compatible AI assistants to inspect local application internals by analyzing JavaScript/Electron/ASAR and .NET artifacts, tracing dependencies, interfaces, and data flows, and preserving traceable evidence.14MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI agents to local analysis tools that inspect native binaries, JavaScript/Electron apps, .NET assemblies, and websites without source code, so features can be explained, traced, and rebuilt. Every finding is returned with its supporting evidence and stated limitations.519,887 npm1MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to reverse-engineer binaries they own or are authorized to test, exposing static analysis through Ghidra or IDA (functions, strings, xrefs, decompilation, disassembly, raw bytes) plus controlled Windows Sandbox runs. Every recorded claim must cite quoted evidence and addresses, which a verifier checks, and unexamined areas are reported as unknown rather than clean.Apache 2.0
- AlicenseNot gradedqualityBmaintenanceEnables AI clients to inspect local software structure, code, and runtime behavior through evidence-backed analysis, including sources, coverage, and limitations.1MIT
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.