io.github.mdfifty50-boop/secure-vault
NPM · SECURE-VAULT-MCP · SCANNED SEP 25
Encrypted secrets and credential management for agents
Available components
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 Security98
- 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
- 31 of 96 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- 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 153 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability45
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 583 tokens (~72/item across 8 items; 7 tools + 1 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 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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
How do I install the io.github.mdfifty50-boop/secure-vault MCP server?
io.github.mdfifty50-boop/secure-vault runs locally as an npm package, launched with npx -y secure-vault-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 · secure-vault-mcp
claude mcp add mdfifty50-boop-secure-vault -- npx -y secure-vault-mcp
{
"mcpServers": {
"mdfifty50-boop-secure-vault": {
"command": "npx",
"args": [
"-y",
"secure-vault-mcp"
]
}
}
} {
"servers": {
"mdfifty50-boop-secure-vault": {
"command": "npx",
"args": [
"-y",
"secure-vault-mcp"
]
}
}
} codex mcp add mdfifty50-boop-secure-vault -- npx -y secure-vault-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mdfifty50-boop-secure-vault": {
"type": "local",
"command": [
"npx",
"-y",
"secure-vault-mcp"
],
"enabled": true
}
}
} openclaw mcp add mdfifty50-boop-secure-vault --command npx --arg -y --arg secure-vault-mcp
mcp_servers:
mdfifty50-boop-secure-vault:
command: "npx"
args: ["-y", "secure-vault-mcp"] {
"McpServers": {
"mdfifty50-boop-secure-vault": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"secure-vault-mcp"
]
}
}
} assistant mcp add mdfifty50-boop-secure-vault -t stdio -c npx -a -y secure-vault-mcp
{
"mcpServers": {
"mdfifty50-boop-secure-vault": {
"command": "npx",
"args": [
"-y",
"secure-vault-mcp"
]
}
}
} 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.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Sept 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.
- 23 Sept 26 −4
- Stability: pass → 0.77 functional
- 22 Sept 26 +1
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 −3
- Stability: pass → 0.83 functional
- 16 Sept 26 +1
- Stability: 0.97 → pass security
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 25 Sept 2026 · Analysed npm/secure-vault-mcp@0.1.1
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 96 packages
| Packages resolved | 96 |
|---|---|
| Stale | 31 |
| 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 →
audit_secret_access ~70
View an audit trail of who accessed which secrets over a time range.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | – | Filter by specific agent (omit for all agents) |
| secret_name | string | – | Filter by specific secret name (omit for all secrets) |
| time_range | string | – | Time range to query |
No output schema declared.
No examples provided.
get_agent_token ~129
Issue a short-lived, scoped token for an agent to use a secret. The agent receives an opaque token ID — never the raw secret. Use inject_secret_to_request to apply the token to an outbound request.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Identifier of the requesting agent |
| scope | string | – | Permission scope for this token |
| service | string | yes | Service name to get a token for (must match a stored secret's service) |
| ttl_seconds | integer | – | Token time-to-live in seconds (default 300 = 5 min, max 86400 = 24h) |
No output schema declared.
No examples provided.
health_check ~20
Returns server health, uptime, version, and call stats
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inject_secret_to_request ~94
Return a request object with the secret injected. Pass a token_id obtained from get_agent_token and a request template with a {{SECRET}} placeholder. The server substitutes the real secret — the agent never handles the raw value.
| Name | Type | Req | Description |
|---|---|---|---|
| request_template | string | yes | Request template with {{SECRET}} placeholder (e.g. JSON body, header string, URL) |
| token_id | string | yes | Token ID from get_agent_token |
No output schema declared.
No examples provided.
rotate_secrets ~69
Rotate all secrets for a given service. Old values are overwritten, and all outstanding tokens for those secrets are invalidated.
| Name | Type | Req | Description |
|---|---|---|---|
| new_value | string | yes | The new secret value to replace the old one |
| service | string | yes | Service whose secrets to rotate (e.g. "openai") |
No output schema declared.
No examples provided.
scan_config_for_leaks ~92
Scan a config text for exposed secrets — API keys, tokens, passwords, private keys. Uses 12 regex patterns covering AWS, GitHub, OpenAI, Anthropic, Slack, Stripe, and generic credentials.
| Name | Type | Req | Description |
|---|---|---|---|
| config_text | string | yes | The config file content or JSON/YAML text to scan |
| source_label | string | – | Label for where this config came from (for audit trail) |
No output schema declared.
No examples provided.
store_secret ~105
Store an encrypted secret with optional rotation policy. Value is encrypted at rest with AES-256-GCM.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | Secret name (e.g. "openai_api_key", "stripe_live") |
| rotation_policy | string | – | Automatic rotation reminder policy |
| service | string | – | Service this secret belongs to (e.g. "openai", "stripe") |
| value | string | yes | The secret value to store — encrypted immediately, never stored in plaintext |
No output schema declared.
No examples provided.
What is the io.github.mdfifty50-boop/secure-vault MCP server?
io.github.mdfifty50-boop/secure-vault is an MCP server listed in the public MCP registry as io.github.mdfifty50-boop/secure-vault. Encrypted secrets and credential management for agents. This page covers its npm package (secure-vault-mcp).
Is the io.github.mdfifty50-boop/secure-vault MCP server safe to use?
io.github.mdfifty50-boop/secure-vault scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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 io.github.mdfifty50-boop/secure-vault MCP server expose?
io.github.mdfifty50-boop/secure-vault exposes 7 tools: health_check, store_secret, get_agent_token, rotate_secrets, audit_secret_access, and 2 more. Their descriptions and schemas cost roughly 579 tokens of context every time the server is loaded.
Is the io.github.mdfifty50-boop/secure-vault MCP server still maintained?
io.github.mdfifty50-boop/secure-vault is still listed as active in the MCP registry. We last reached this channel on 25 September 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 io.github.mdfifty50-boop/secure-vault MCP server under?
io.github.mdfifty50-boop/secure-vault declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.