lotor-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOTOR_HOME | No | Override the default receipts store path (~/.lotor). Keep this on local disk. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| query_receiptsA | Query receipt summaries from the persisted chain (most recent first). Never returns full file contents. |
| verify_chain | Verify the integrity of the receipt chain using the stored public key. Returns ok, brokenAt, reason, and entryCount. |
| lotor_status | Report Lotor runtime status: home path, receipt count, chain integrity, current herding mode (herded | grazing | loose | custom), whether the human-signature gate is set up, and whether the hooks that actually record and gate are registered in Claude Code settings. Call this at the start of a session or whenever the user asks about Lotor. If gateInitialized is false, walk the user through running |
| gated_action | Execute a gated action with approval token. FAILS CLOSED: without a valid approval token, returns decision:denied. |
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 1 tool
With only one tool, there is no risk of confusion or overlapping purposes.
The single tool name 'query_receipts' follows a clear verb_noun pattern, and consistency is trivially maintained.
A single tool is extremely limited for a server likely intended to manage receipts; at minimum, write and full retrieval operations are expected.
The tool surface provides only a query function with no create, update, delete, or full receipt retrieval, leaving critical gaps for any practical workflow.