re-vtil
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_vtilA | Return vtil-cli version + supported architectures. Reports |
| lift_handlerA | Lift arch / code to VTIL intermediate language. Args:
arch: target architecture — one of Returns:: Each lifted instruction is one of VTIL's IL primitives
( On a missing binary, returns |
| optimizeA | Run VTIL optimization passes over a lifted IL tree. Args:
il: the IL tree produced by :func: Returns:: The output IL is in the same shape as the input — drop-in
replacement for downstream |
| emit_pseudo_cA | Emit a pseudo-C reading of a lifted IL tree. The output is best-effort — VTIL's Args:
il: the IL tree (raw from Returns:: |
| simplify_lifted_ilA | Run the curated default pass set on a lifted IL tree. The canonical pass order comes from
Args:
il: the IL tree produced by :func: Returns:: |
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 5 tools
Each tool targets a distinct operation: checking the CLI, lifting code, optimizing IL generically, optimizing with a curated preset, and emitting pseudocode. There is no functional overlap.
Names follow a verb_noun pattern with underscores, mostly consistent (check_vtil, emit_pseudo_c, lift_handler, optimize, simplify_lifted_il). The verb 'simplify' is slightly different from 'optimize', but both are clear and the pattern is predictable.
Five tools is well-scoped for a binary lifting MCP server: verification, lifting, two optimization variants, and output. Neither too few nor too many.
The core workflow (lift -> optimize -> emit) is fully covered. The only minor gap is the lack of a tool for raw IL inspection or comparison, but the provided set is sufficient for typical reverse engineering tasks.