Skip to main content
The complete error vocabulary, generated from the err factory map in @the-40-thieves/reliquary-tc-shared so it never drifts from the running server. See the API Reference for the response envelope these codes travel in, and the Tool Catalog for the surface that raises them. Errors arrive in the standard MCP error shape. The code below is what appears in the structured payload; it is stable across releases and is what a client should branch on. Messages are defaults and may be replaced at the throw site with something more specific about the failure.
This table is generated from the error factory (bun run docgen:render). Do not hand-edit the region between the markers — add the error to the shared err map and regenerate.
Every failure reliquary-tc returns carries one of these 39 canonical codes, 39 of which ship a recovery hint. The code is the stable contract — branch on it rather than on the message, which is a human-readable default that may be replaced with something more specific at the throw site.

Reading the Recovery column

Recovery hints say what to do instead; the retryable flag on the error says whether to retry. They are deliberately separate — a code can be non-retryable and still have a clear next step. A hint is a fixed string chosen by code alone. No path, query, caller, vault or argument is in scope where it is selected, so a hint cannot leak vault content by construction rather than by review. An em dash means the taxonomy declares no hint for that code — a considered choice, made because guidance that only restates the message is noise, not an omission. Where a failure can name specifics, those arrive in the error’s details object (for example details.required on forbidden, or the offending field on validation_error). Read details in preference to parsing message text.