Lotor
NPM · LOTOR-MCP
A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.
Available components
Last scanned (4 hours ago)
Scores higher than 77% of npm servers
Category Security
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 102 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 320 tokens (~80/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "gated_action" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 0
- Stability: pass → 0.97 functional
- 20 Oct 26 0
- Stability: 0.97 → pass security
- 19 Oct 26 0
- Stability: pass → 0.97 functional
- 17 Oct 26 +1
- Stability: 0.87 → pass security
- 16 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Oct 26 −2
- Stability: pass → 0.80 functional
- 13 Oct 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/lotor-mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
gated_action ~72
Execute a gated action with approval token. FAILS CLOSED: without a valid approval token, returns decision:denied.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | Action to execute |
| approvalToken | object | – | Owner-signed approval token { request, nonce, timestamp, signature } |
| params | object | – | Action parameters |
No output schema declared.
No examples provided.
lotor_status ~162
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 `npm run setup` in a terminal to set their signing passphrase (this needs a real terminal; you cannot do it for them). If hooksRegistered.preToolUse is false, nothing is gated regardless of gateInitialized: point the user at the README install steps. Always tell the user the home path so they can see where the runtime lives.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
query_receipts ~53
Query receipt summaries from the persisted chain (most recent first). Never returns full file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of receipts to return |
| sessionId | string | – | Filter by specific session ID |
No output schema declared.
No examples provided.
verify_chain ~33
Verify the integrity of the receipt chain using the stored public key. Returns ok, brokenAt, reason, and entryCount.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Lotor MCP server?
Lotor runs locally as an npm package, launched with npx -y lotor-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · lotor-mcp
claude mcp add githubscum-lotor -- npx -y lotor-mcp
What is the Lotor MCP server?
Lotor is an MCP server listed in the public MCP registry as io.github.githubscum/lotor. A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign. This page covers its npm package (lotor-mcp).
Is the Lotor MCP server safe to use?
Lotor scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Lotor MCP server expose?
Lotor exposes 4 tools: query_receipts, verify_chain, lotor_status, gated_action. Their descriptions and schemas cost roughly 320 tokens of context every time the server is loaded.
Is the Lotor MCP server still maintained?
Lotor is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Lotor MCP server under?
Lotor declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.