Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

KeyZula

NPM · @KEYZULA/CLI

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

Available components

+3 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% of npm servers

Category Security

Trust breakdown (7 categories)

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
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency32
Schema Quality & AI Usability69
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 593 tokens (~118/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 Management83
  • Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 71% 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 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 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
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 20 Nov 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.

  • 18 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.

  • 16 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.

  • 14 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.

  • 12 Nov 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.

  • 10 Nov 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.

  • 7 Nov 26 +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.

  • 5 Nov 26 +10
    • Tool safety: pass → unverified ▼ security
    • 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. security
    • Security disclosure: unverified → fail ▼ functional
    • Capabilities: fail → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • Stability: unverified → 0.30 ▲ functional
    • First check of Schema quality: unverified functional
    • Package version: 1.2.3 → 1.2.4 functional
Diagnostics

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 21 Nov 2026 · Analysed npm/@keyzula/cli@1.2.4

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~553 tokens

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 →

Tool Tokens
generate_password ~68

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

NameTypeReqDescription
kindstring––
lengthinteger–password: number of characters
symbolsboolean–password: include symbols
wordsinteger–passphrase: number of words

No output schema declared.

No examples provided.

inject_template ~161

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.

NameTypeReqDescription
output_pathstringyesFile to write, e.g. .env
overwriteboolean––
templatestring–Template text. Use this or template_path.
template_pathstring–Path of a template file, e.g. .env.tpl

No output schema declared.

No examples provided.

run_command ~220

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.

NameTypeReqDescription
commandarrayyesProgram and arguments, e.g. ["psql", "-c", "select 1"].
cwdstring–Working directory (default: the server's current directory).
envobject–Environment variables, e.g. {"PGPASSWORD": "kz://Production/Postgres/password"}.
timeout_secondsinteger––

No output schema declared.

No examples provided.

search_items ~82

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.

NameTypeReqDescription
limitinteger––
querystring–Text to look for. Leave empty to list items.

No output schema declared.

No examples provided.

vault_status ~22

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

npm · @keyzula/cli

# add to Claude Code
claude mcp add com-keyzula-keyzula -- npx -y @keyzula/cli mcp
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.