lispex mcp serve starts a local stdio server from the installed Native
binary. Every request and response uses a closed versioned frame.
Tools
| Tool | Input | Result |
|---|---|---|
lispex_reference | topic and optional exact name | installed forms, procedures, reader grammar, resources, or routes |
lispex_eval | source and optional datum | Rust tree observation with value, stdout, warnings, and diagnostics |
lispex_diagnostic | one E3xx or W3xx code | exact catalog explanation and trigger condition |
lispex_compare_routes | named court, source, and optional input | route observations, agreement status, resources, and lineage |
The reference tool uses topics forms, procedures, reader, resources,
and routes. Unknown names return known: false, which lets an assistant
correct a request against the installed version.
Fixed comparisons
| Court | Products |
|---|---|
tree-rust | built-in Rust tree and Rust VM |
rust-topaz | Rust VM and the exact Topaz VM selected at startup |
all-four | Rust tree, Rust VM, selected Topaz VM, and a fresh AOT product |
Select optional Topaz products through absolute paths when starting the server.
lispex mcp serve \
--topaz-vm /absolute/path/to/topaz-vm \
--topaz-compiler /absolute/path/to/topaz-compiler \
--rust-tools /absolute/path/to/rust-toolsEach comparison retains the named route set and records agreement,
partial_comparison, answer_selected, terminal statuses, resource values,
and product identities.
Resource profile
| Resource | Value |
|---|---|
| source per request | 65,536 bytes |
| input per request | 16,384 bytes |
| evaluation result | 1 MiB |
| evaluation wall time | 5 seconds |
| comparison result | 4 MiB |
all-four wall time | 11 minutes |
The server returns timeout, cancellation, input, product, build, cleanup, and process terminal states explicitly. It is an authoring surface for reviewed source. Application rules from external users belong in the Resource-Controlled Evaluator.
Data and authority flow
Source and optional datum enter over local stdio. The worker holds request data in memory and releases it when the request ends. Tool results contain the source hash, observations, resource values, and diagnostics. Absolute startup paths select optional products for the lifetime of that server.
MCP produces authoring observations. Lispex Vouch consumes exact source and input through its own authenticated request, current re-execution, and local gate. The host application consumes the gate result and owns the external action.