# KeyZula (npm · @keyzula/cli)

Use passwords and API keys from your KeyZula vault without the assistant seeing them.

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `@keyzula/cli`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli.md), [page](https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli)

## Channel facts

- Registry: `npm`
- Package: `@keyzula/cli`
- Version: `1.2.4`
- 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (UNLICENSED) isn't a recognized OSI-approved license.
  - Actively maintained (last published 16 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 593 tokens (~118/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 71% 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 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the KeyZula MCP server?

KeyZula runs locally as an npm package, launched with npx -y @keyzula/cli mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-keyzula-keyzula -- npx -y @keyzula/cli mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-keyzula-keyzula": {
      "command": "npx",
      "args": [
        "-y",
        "@keyzula/cli",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-keyzula-keyzula": {
      "command": "npx",
      "args": [
        "-y",
        "@keyzula/cli",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-keyzula-keyzula -- npx -y @keyzula/cli mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-keyzula-keyzula": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@keyzula/cli",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-keyzula-keyzula --command npx --arg -y --arg @keyzula/cli --arg mcp
```

### Hermes

```yaml
mcp_servers:
  com-keyzula-keyzula:
    command: "npx"
    args: ["-y", "@keyzula/cli", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-keyzula-keyzula": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@keyzula/cli",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-keyzula-keyzula -t stdio -c npx -a -y @keyzula/cli mcp
```

### Other

```json
{
  "mcpServers": {
    "com-keyzula-keyzula": {
      "command": "npx",
      "args": [
        "-y",
        "@keyzula/cli",
        "mcp"
      ]
    }
  }
}
```

## 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-20 (score 76, +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.

### 2026-11-18 (score 75, +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-16 (score 74, +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-14 (score 73, +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-11-12 (score 72, +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-11-10 (score 71, +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-11-07 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-05 (score 69, +10)

- [security regression] Tool safety: pass → unverified
- [security improvement] Source repository: fail → pass
- [security] Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet.
- [functional regression] Security disclosure: unverified → fail
- [functional regression] Capabilities: fail → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional improvement] Stability: unverified → 0.30
- [functional] First check of Schema quality: unverified
- [functional] Package version: 1.2.3 → 1.2.4

## MCP tools (5)

### `vault_status` (~22 tokens)

Vault status

Shows whether KeyZula is logged in and the vault is unlocked.

### `search_items` (~82 tokens)

Search vault items

Searches the user's KeyZula vault by name, username, website or folder. Returns item names, locations, usernames, websites and the kz:// reference of each field. Secret values are never returned. Use the references with run_command or inject_template.

Input parameters:

- `limit` (integer)
- `query` (string): Text to look for. Leave empty to list items.

### `run_command` (~220 tokens)

Run a command with secrets

Runs a program with secrets from the vault placed in its environment variables, without showing them to you. Give env values as kz:// references (plain strings are passed as they are). References look like "kz://<collection>/<item>/<field>" ("~" is the personal vault). Get them from search_items; never guess them. The command runs directly, not through a shell; for pipes or variable expansion use ["sh", "-c", "…"] and refer to the variable (e.g. "$DB_PASSWORD"). Secret values in the output are replaced with "<concealed by KeyZula>". Do not try to print or transform secrets to get around this.

Input parameters:

- `command` (array, required): Program and arguments, e.g. ["psql", "-c", "select 1"].
- `cwd` (string): Working directory (default: the server's current directory).
- `env` (object): Environment variables, e.g. {"PGPASSWORD": "kz://Production/Postgres/password"}.
- `timeout_seconds` (integer)

### `inject_template` (~161 tokens)

Write a config file with secrets

Fills a template with secrets from the vault and writes the result to a file that only the user can read (mode 0600). Placeholders look like {{ kz://<collection>/<item>/<field> }}. References look like "kz://<collection>/<item>/<field>" ("~" is the personal vault). Get them from search_items; never guess them. The file's content is not returned to you; do not read the written file back.

Input parameters:

- `output_path` (string, required): File to write, e.g. .env
- `overwrite` (boolean)
- `template` (string): Template text. Use this or template_path.
- `template_path` (string): Path of a template file, e.g. .env.tpl

### `generate_password` (~68 tokens)

Generate a password

Generates a strong random password or passphrase. It is not saved to the vault.

Input parameters:

- `kind` (string)
- `length` (integer): password: number of characters
- `symbols` (boolean): password: include symbols
- `words` (integer): passphrase: number of words

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 70
- 2026-11-07: 70
- 2026-11-06: 69
- 2026-11-05: 69
- 2026-11-04: 59
- 2026-11-03: 59
- 2026-11-02: 59
- 2026-11-01: 59
- 2026-10-31: 59
- 2026-10-30: 59
- 2026-10-29: 59
- 2026-10-28: 59
- 2026-10-27: 44

## Common questions

### What is the KeyZula MCP server?

KeyZula is an MCP server listed in the public MCP registry as com.keyzula/keyzula. Use passwords and API keys from your KeyZula vault without the assistant seeing them. This page covers its npm package (@keyzula/cli).

### Is the KeyZula MCP server safe to use?

KeyZula scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 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 KeyZula MCP server expose?

KeyZula exposes 5 tools: vault_status, search_items, run_command, inject_template, generate_password. Their descriptions and schemas cost roughly 553 tokens of context every time the server is loaded.

### Is the KeyZula MCP server still maintained?

KeyZula is still listed as active in the MCP registry. We last reached this channel on 21 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 KeyZula MCP server under?

KeyZula declares the UNLICENSED 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.

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

VerifyMCP ran 16 checks on KeyZula, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@keyzula/cli
- Socket report: https://socket.dev/npm/package/@keyzula/cli
- Repository: https://github.com/KeyZula/mcp-server
- Website: https://keyzula.com/en/ai/
- Changelog RSS feed: https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli.json
- HTML version of this page: https://verifymcp.io/servers/com-keyzula-keyzula/keyzula-cli
