keyshroud
NPM · KEYSHROUD
Agent-safe secrets from self-hosted Vaultwarden/Bitwarden: injected into commands, masked in output
Available components
Last scanned (7 hours ago)
Scores higher than 69% of npm 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 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 & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to dinhkarate/keyshroud). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability70
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 333 tokens (~83/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 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 4 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 supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 18 Oct 26 +15
- Stability: 0.07 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Package version: 0.6.0 → 0.6.1 functional
- 17 Oct 26 −14
- Malware scan: pass → unverified ▼ security
- Stability: unverified → 0.07 ▲ functional
- Package version: 0.5.3 → 0.6.0 functional
- 15 Oct 26 +41
- Injection markers: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: dinhkarate/keyshroud security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- Package version: 0.5.1 → 0.5.3 functional
- Package version: 0.5.1 → 0.5.2 functional
- 14 Oct 26 40
First indexed and scored.
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 18 Oct 2026 · Analysed npm/keyshroud@0.6.1
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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | dinhkarate/keyshroud |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/dinhkarate/keyshroud/.github/workflows/release.yml@refs/tags/v0.6.1 |
| Rekor log index | 3308115572 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:1fbc7b53a6e7e70c8e35cdf11741f1df6c38db771a055b41f194005fd2cf235c225a05b56c56f976086c871bf2245d2680864f3a24ce4d8fcf40ba4e1 |
Background: How many MCP packages publish verified provenance →
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 →
secrets_list ~39
List the names of secrets wired for this machine. Never returns values.
| Name | Type | Req | Description |
|---|---|---|---|
| env_file | string | – | Optional dotenv file of bw:// references to include |
No output schema declared.
No examples provided.
secrets_request ~103
Ask the human to store a new secret. Opens a native hidden-input dialog on the user's desktop and stores the value in the vault; where no dialog can be shown, returns a terminal command for the user to run instead. The value never passes through the conversation.
| Name | Type | Req | Description |
|---|---|---|---|
| env_name | string | yes | UPPER_SNAKE_CASE variable name |
| item_name | string | yes | Vault item name to create |
| purpose | string | – | Short note stored with the item |
No output schema declared.
No examples provided.
secrets_run ~121
Run a shell command with vault secrets injected as environment variables. Secret values in stdout/stderr are replaced with <redacted:NAME>. Reference secrets as $NAME inside the command; never echo them.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | Shell command run with /bin/sh -c |
| cwd | string | – | Working directory |
| env_file | string | – | Dotenv file of bw:// references to add |
| only | array | – | Inject only these names |
| timeout_ms | number | – | Kill the command after this many milliseconds (default 120000) |
No output schema declared.
No examples provided.
vault_status ~23
Report vault lock state, server, and item count. Never returns values.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the keyshroud MCP server?
keyshroud runs locally as an npm package, launched with npx -y keyshroud. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · keyshroud
claude mcp add dinhkarate-keyshroud -- npx -y keyshroud
What is the keyshroud MCP server?
keyshroud is an MCP server listed in the public MCP registry as io.github.dinhkarate/keyshroud. Agent-safe secrets from self-hosted Vaultwarden/Bitwarden: injected into commands, masked in output. This page covers its npm package (keyshroud).
Is the keyshroud MCP server safe to use?
keyshroud scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 18 October 2026. It declares no install or post-install scripts. 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 keyshroud MCP server expose?
keyshroud exposes 4 tools: secrets_list, secrets_run, secrets_request, vault_status. Their descriptions and schemas cost roughly 286 tokens of context every time the server is loaded.
Is the keyshroud MCP server still maintained?
keyshroud is still listed as active in the MCP registry. We last reached this channel on 18 October 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 keyshroud MCP server under?
keyshroud declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.