Lockkeeper
PYPI · LOCKKEEPER
Routes each task to the few skills, MCP servers and tools that fit it.
Available components
Last scanned (18 hours ago)
Scores higher than 95% of PyPI servers
Category Developer Tools
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency87
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to Hannay001/lockkeeper). View diagnostics → Pass
- License check failed: the license (FSL-1.1-ALv2) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 37 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 385 tokens (~128/item across 3 items; 3 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 Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 Nov 26 0
- Stability: 0.97 → pass security
- 2 Nov 26 0
- Stability: pass → 0.97 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- 27 Oct 26 0
- Stability: 0.97 → pass security
- 26 Oct 26 +16
- Malware scan: unverified → pass ▲ security
- 23 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
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 4 Nov 2026 · Analysed pypi/lockkeeper@1.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | Hannay001/lockkeeper |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/Hannay001/lockkeeper/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 2977178808 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:4887c66b159388606c198103da597b0cf86d5e34974782e6fb978d9d6000d994 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | setuptools.build_meta |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
audit Audit a skill, plugin or config for prompt injection ~89
Scan a file or folder (a skill, plugin, MCP config, script) for instruction overrides, exfiltration, obfuscated execution, destructive commands and hidden text. Returns a verdict (clean, suspect, hostile) with findings. Run it before trusting or installing a capability.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | File or directory to scan. |
| recursive | boolean | – | Scan a directory recursively (default true). |
No output schema declared.
No examples provided.
route Route a task to the right capabilities ~154
Pick the few installed skills, MCP servers, plugins, tools, agents and commands that fit a task, before starting it. Returns a bounded bundle (10 by default) grouped by role (primary, context, integration, execution, verification, support), each with why it was chosen and how to use it: for skills, the exact SKILL.md path to read. Use this instead of scanning skill lists; it keeps the context small.
| Name | Type | Req | Description |
|---|---|---|---|
| max | integer | – | Bundle size (default: the configured bundle_size, 10 unless changed). |
| runtime | string | – | The agent that will use the bundle (defaults to the server's --runtime). |
| task | string | yes | The task or user prompt, in plain words. |
No output schema declared.
No examples provided.
search Search installed capabilities ~55
Rank installed capabilities for keywords; returns names, types, scores and load paths.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Results (default 10). |
| query | string | yes | Keywords or a short task description. |
| runtime | string | – | – |
No output schema declared.
No examples provided.
How do I install the Lockkeeper MCP server?
Lockkeeper runs locally as a PyPI package, launched with uvx lockkeeper. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · lockkeeper
claude mcp add hannay001-lockkeeper -- uvx lockkeeper
What is the Lockkeeper MCP server?
Lockkeeper is an MCP server listed in the public MCP registry as io.github.Hannay001/lockkeeper. Routes each task to the few skills, MCP servers and tools that fit it. This page covers its PyPI package (lockkeeper).
Is the Lockkeeper MCP server safe to use?
Lockkeeper scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 November 2026. Its build provenance is signed and verified. 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 Lockkeeper MCP server expose?
Lockkeeper exposes 3 tools: route, search, audit. Their descriptions and schemas cost roughly 298 tokens of context every time the server is loaded.
Is the Lockkeeper MCP server still maintained?
Lockkeeper is still listed as active in the MCP registry. We last reached this channel on 4 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 Lockkeeper MCP server under?
Lockkeeper declares the FSL-1.1-ALv2 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.