# kdbx (oci · ghcr.io/yarrasys/kdbx)

Read-only access to secrets in a local KeePassXC vault. Runs commands with them injected.

- Trust score: 50/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- oci · `ghcr.io/yarrasys/kdbx`: 50/100 (this document), [markdown](https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx.md), [page](https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/yarrasys/kdbx`
- Version: `0.3.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - 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.
  - 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.
  - Install-script risk not yet assessed.
  - 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.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 21 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 65/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 331 tokens (~66/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**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.

## Install

### 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 mcp, plus the required -v, which you supply. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add yarrasys-kdbx -- docker run --rm -i -e KEEPASSXC_DIR -e KDBX_ENV ghcr.io/yarrasys/kdbx:0.3.2 mcp
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Cursor

```json
{
  "mcpServers": {
    "yarrasys-kdbx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "KEEPASSXC_DIR",
        "-e",
        "KDBX_ENV",
        "ghcr.io/yarrasys/kdbx:0.3.2",
        "mcp"
      ]
    }
  }
}
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### VS Code

```json
{
  "servers": {
    "yarrasys-kdbx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "KEEPASSXC_DIR",
        "-e",
        "KDBX_ENV",
        "ghcr.io/yarrasys/kdbx:0.3.2",
        "mcp"
      ]
    }
  }
}
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Codex

```bash
codex mcp add yarrasys-kdbx -- docker run --rm -i -e KEEPASSXC_DIR -e KDBX_ENV ghcr.io/yarrasys/kdbx:0.3.2 mcp
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "yarrasys-kdbx": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "-e",
        "KEEPASSXC_DIR",
        "-e",
        "KDBX_ENV",
        "ghcr.io/yarrasys/kdbx:0.3.2",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Hermes

```yaml
mcp_servers:
  yarrasys-kdbx:
    command: "docker"
    args: ["run", "--rm", "-i", "-e", "KEEPASSXC_DIR", "-e", "KDBX_ENV", "ghcr.io/yarrasys/kdbx:0.3.2", "mcp"]
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Netclaw

```json
{
  "McpServers": {
    "yarrasys-kdbx": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "-e",
        "KEEPASSXC_DIR",
        "-e",
        "KDBX_ENV",
        "ghcr.io/yarrasys/kdbx:0.3.2",
        "mcp"
      ]
    }
  }
}
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

### Other

```json
{
  "mcpServers": {
    "yarrasys-kdbx": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "-e",
        "KEEPASSXC_DIR",
        "-e",
        "KDBX_ENV",
        "ghcr.io/yarrasys/kdbx:0.3.2",
        "mcp"
      ]
    }
  }
}
```

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. The registry lists runner options for this package that are not in this command (they are not ones we reproduce, or they name another package). Check the registry entry before relying on it. Incomplete: the registry marks -v as required and gives no value we can show, so it is not in this command. Add it before you run it.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 50, +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.

### 2026-11-03 (score 49, +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.

### 2026-11-01 (score 48, +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.

### 2026-10-30 (score 47, +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.

### 2026-10-28 (score 46, +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.

### 2026-10-26 (score 45, +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.

### 2026-10-23 (score 44, +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.

### 2026-10-21 (score 43, +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.

## MCP tools (5)

### `kdbx_check` (~58 tokens)

Verify every mapped variable resolves in the active environment.

Input parameters:

- `command` (string): command line to run
- `group` (string): optional group prefix filter
- `path` (string): entry path, e.g. api/openai

### `kdbx_envs` (~58 tokens)

List configured environments and mark the active one.

Input parameters:

- `command` (string): command line to run
- `group` (string): optional group prefix filter
- `path` (string): entry path, e.g. api/openai

### `kdbx_get` (~77 tokens)

Confirm a secret exists at PATH. Always masked — this tool never returns a secret value. Use kdbx_run to actually use a secret.

Input parameters:

- `command` (string): command line to run
- `group` (string): optional group prefix filter
- `path` (string): entry path, e.g. api/openai

### `kdbx_list` (~61 tokens)

List entry paths in the active vault. Never returns secret values.

Input parameters:

- `command` (string): command line to run
- `group` (string): optional group prefix filter
- `path` (string): entry path, e.g. api/openai

### `kdbx_run` (~77 tokens)

Run a command with the active environment's secrets injected. kdbx never prints a secret, and injected values are masked in the captured output.

Input parameters:

- `command` (string): command line to run
- `group` (string): optional group prefix filter
- `path` (string): entry path, e.g. api/openai

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx#diagnostics

## Score history

- 2026-11-05: 50
- 2026-11-04: 49
- 2026-11-03: 49
- 2026-11-02: 48
- 2026-11-01: 48
- 2026-10-31: 47
- 2026-10-30: 47
- 2026-10-29: 46
- 2026-10-28: 46
- 2026-10-27: 45
- 2026-10-26: 45
- 2026-10-25: 44
- 2026-10-24: 44
- 2026-10-23: 44
- 2026-10-22: 43
- 2026-10-21: 43
- 2026-10-20: 42
- 2026-10-19: 42
- 2026-10-18: 41
- 2026-10-17: 41
- 2026-10-16: 39
- 2026-10-15: 39
- 2026-10-14: 39

## Common questions

### 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.

### What did VerifyMCP test on the kdbx MCP server?

VerifyMCP ran 12 checks on kdbx, covering Source repository, Provenance, License, Maintenance and 8 more. 4 items could not be completed, a gap on our side rather than a finding about kdbx: Malware scan, Known CVEs, Install scripts and Dependency health. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to a container image, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- GitHub Container Registry: https://ghcr.io/yarrasys/kdbx
- Repository: https://github.com/yarrasys/kdbx
- Changelog RSS feed: https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx.xml
- Changelog JSON feed: https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx.json
- HTML version of this page: https://verifymcp.io/servers/yarrasys-kdbx/ghcr-io-yarrasys-kdbx