Lotor
NPM · LOTOR-MCP · SCANNED AUG 3
A local receipt and approval gate for AI agent sessions. The agent can act, but it cannot sign.
Available components
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 →
Supply Chain Security86
- No malware found by supply-chain analysis.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- Only part of the dependency tree could be resolved (94 of 98), so this covers what we could see, not the whole tree. 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 8 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Add this component to your MCP client. Where a client-specific snippet is available, pick your client below and copy it straight into your config; otherwise use the connection detail shown.
npm · lotor-mcp
claude mcp add githubscum-lotor -- npx -y lotor-mcp
codex mcp add githubscum-lotor -- npx -y lotor-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"githubscum-lotor": {
"type": "local",
"command": [
"npx",
"-y",
"lotor-mcp"
],
"enabled": true
}
}
} openclaw mcp add githubscum-lotor --command npx --arg -y --arg lotor-mcp
mcp_servers:
githubscum-lotor:
command: "npx"
args: ["-y", "lotor-mcp"] {
"mcpServers": {
"githubscum-lotor": {
"command": "npx",
"args": [
"-y",
"lotor-mcp"
]
}
}
} 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.
- 3 Aug 26 +32
- Provenance: unverified → fail ▼ security
- Install scripts: unverified → pass ▲ security
- Known CVEs: unverified → partial ▲ security
- License: unverified → pass ▲ functional
- Dependency health: unverified → partial ▲ functional
- Maintenance: unverified → pass ▲ functional
- Stability: unverified → 0.27 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- Schema quality: unverified → good ▲ functional
- Licence: Apache-2.0 functional
- 2 Aug 26 +15
- Malware scan: unverified → pass ▲ security
- 31 Jul 26 −7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 +22
- Tool coverage: unverified → 100 ▲ functional
- 28 Jul 26 −22
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 27 Jul 26 28
First indexed and scored.
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 3 Aug 2026 · Analysed npm/[email protected]
Provenance none
Ecosystem: npm · Outcome: none
Dependencies 94 packages
94 packages in the resolved dependency tree · 94 deprecated · 29 stale.
The dependency tree was only partially resolved, so these counts may be incomplete.
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.
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.