kdbx
OCI · GHCR.IO/YARRASYS/KDBX
Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.
Available components
Last scanned (10 hours ago)
Scores higher than 77% of OCI 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 Security0
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs could not be checked: this image's dependency list comes from an SBOM its publisher attached, which nothing verifies, so we will not report it as a clean result.Unverified
- Install-script risk not yet assessed.Unverified
- Dependency health could not be checked: this image's dependency list comes from an SBOM its publisher attached. It names packages and versions but not whether each is deprecated, still maintained or linked to its source, so there is nothing we can fairly grade.Unverified
Provenance & Transparency48
- 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 (MIT).Pass
- Actively maintained (last published 21 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability65
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 331 tokens (~66/item across 5 items; 5 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 26 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 5 Nov 2026 · Analysed oci/ghcr.io/yarrasys/kdbx@0.3.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
kdbx_check ~58
Verify every mapped variable resolves in the active environment.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | command line to run |
| group | string | – | optional group prefix filter |
| path | string | – | entry path, e.g. api/openai |
No output schema declared.
No examples provided.
kdbx_envs ~58
List configured environments and mark the active one.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | command line to run |
| group | string | – | optional group prefix filter |
| path | string | – | entry path, e.g. api/openai |
No output schema declared.
No examples provided.
kdbx_get ~77
Confirm a secret exists at PATH. Always masked — this tool never returns a secret value. Use kdbx_run to actually use a secret.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | command line to run |
| group | string | – | optional group prefix filter |
| path | string | – | entry path, e.g. api/openai |
No output schema declared.
No examples provided.
kdbx_list ~61
List entry paths in the active vault. Never returns secret values.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | command line to run |
| group | string | – | optional group prefix filter |
| path | string | – | entry path, e.g. api/openai |
No output schema declared.
No examples provided.
kdbx_run ~77
Run a command with the active environment's secrets injected. kdbx never prints a secret, and injected values are masked in the captured output.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | – | command line to run |
| group | string | – | optional group prefix filter |
| path | string | – | entry path, e.g. api/openai |
No output schema declared.
No examples provided.
How do I install the kdbx MCP server?
kdbx runs locally as a container image, launched with docker run --rm -i -e KEEPASSXC_DIR -e KDBX_ENV ghcr.io/yarrasys/kdbx:0.3.2. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.
oci · ghcr.io/yarrasys/kdbx
claude mcp add yarrasys-kdbx -- docker run --rm -i -e KEEPASSXC_DIR -e KDBX_ENV ghcr.io/yarrasys/kdbx:0.3.2
This image reads KEEPASSXC_DIR and KDBX_ENV. Set them in your client's env block for this server; docker run -e passes each one through to the container.
What is the kdbx MCP server?
kdbx is an MCP server listed in the public MCP registry as io.github.yarrasys/kdbx. Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected. This page covers its container image (ghcr.io/yarrasys/kdbx).
Is the kdbx MCP server safe to use?
kdbx scores 50 out of 100 on VerifyMCP. 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 kdbx MCP server expose?
kdbx exposes 5 tools: kdbx_check, kdbx_envs, kdbx_get, kdbx_list, kdbx_run. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.
Is the kdbx MCP server still maintained?
kdbx 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 kdbx MCP server under?
kdbx declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.