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.

io.github.mdfifty50-boop/secure-vault

NPM · SECURE-VAULT-MCP

Encrypted secrets and credential management for agents

Available components

0 this week 73 Trust /100

Last scanned (23 hours ago)

Scores higher than 46% 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 Security81
  • No malware found by supply-chain analysis.Pass
  • CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available. View diagnostics → Fail
  • No install/post-install scripts declared.Pass
  • 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
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
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 0
    • Stability: 0.97 → pass security
  • 19 Nov 26 0
    • Stability: pass → 0.97 functional
  • 13 Nov 26 0
    • Stability: 0.97 → pass security
  • 12 Nov 26 +1

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

  • 11 Nov 26 −1
    • Stability: pass → 0.93 functional
  • 7 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 6 Nov 26 0
    • Security disclosure: fail → unverified ▼ functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
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/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 →

Vulnerabilities 1 finding
ID CVE Severity Vector Fix available
GHSA-mrhx-c7xc-m3w5 CVE-2023-54404 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 93 packages
Packages resolved 93
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 7 exposed · ~579 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
audit_secret_access ~70

View an audit trail of who accessed which secrets over a time range.

NameTypeReqDescription
agent_idstring–Filter by specific agent (omit for all agents)
secret_namestring–Filter by specific secret name (omit for all secrets)
time_rangestring–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.

NameTypeReqDescription
agent_idstringyesIdentifier of the requesting agent
scopestring–Permission scope for this token
servicestringyesService name to get a token for (must match a stored secret's service)
ttl_secondsinteger–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.

NameTypeReqDescription
request_templatestringyesRequest template with {{SECRET}} placeholder (e.g. JSON body, header string, URL)
token_idstringyesToken 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.

NameTypeReqDescription
new_valuestringyesThe new secret value to replace the old one
servicestringyesService 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.

NameTypeReqDescription
config_textstringyesThe config file content or JSON/YAML text to scan
source_labelstring–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.

NameTypeReqDescription
namestringyesSecret name (e.g. "openai_api_key", "stripe_live")
rotation_policystring–Automatic rotation reminder policy
servicestring–Service this secret belongs to (e.g. "openai", "stripe")
valuestringyesThe secret value to store — encrypted immediately, never stored in plaintext

No output schema declared.

No examples provided.

Install

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

# add to Claude Code
claude mcp add mdfifty50-boop-secure-vault -- npx -y secure-vault-mcp
Common questions

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 73 out of 100 on VerifyMCP. We recorded 1 known advisory against 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 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 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 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.

What did VerifyMCP test on the io.github.mdfifty50-boop/secure-vault MCP server?

VerifyMCP ran 16 checks on io.github.mdfifty50-boop/secure-vault, 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.