Back to Browse

Secure Vault MCP Server

SecurityUse Caution3.5MCP RegistryLocal
Free

Server data from the Official MCP Registry

Encrypted secrets and credential management for agents

About

Encrypted secrets and credential management for agents

Security Report

3.5
Use Caution3.5High Risk

secure-vault-mcp is a well-intentioned secrets management server with a sound encryption model (AES-256-GCM) and token-based access control. However, the security implementation has significant gaps: the server lacks any authentication/authorization mechanism to control who can store, retrieve, or rotate secrets; no input validation is evident from the documentation; and critical security operations (like token issuance and secret injection) are exposed without access controls. The in-memory-only storage means secrets are lost on restart, and the inability to verify implementation details from the provided files leaves core security claims unvalidated. Users should be aware these architectural weaknesses undermine the threat model despite good cryptographic intentions. Supply chain analysis found 4 known vulnerabilities in dependencies (0 critical, 3 high severity). Package verification found 1 issue.

4 files analyzed · 16 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

env_vars

Check that this permission is expected for this type of plugin.

file_system

Check that this permission is expected for this type of plugin.

database

Check that this permission is expected for this type of plugin.

process_spawn

Check that this permission is expected for this type of plugin.

Unverified package source

We couldn't verify that the installable package matches the reviewed source code. Proceed with caution.

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "io-github-mdfifty50-boop-secure-vault": {
      "args": [
        "-y",
        "secure-vault-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

secure-vault-mcp

MCP server for agent-native secrets management. 24,008 secrets have been found in MCP config files on public GitHub. This server solves that.

Agents need secrets to call APIs, but they shouldn't see raw values. secure-vault-mcp stores secrets encrypted with AES-256-GCM, issues short-lived scoped tokens, and injects secrets into requests server-side so the agent never handles plaintext credentials.

Install

npx secure-vault-mcp

Claude Desktop

Add to claude_desktop_config.json:

{
  "mcpServers": {
    "secure-vault": {
      "command": "npx",
      "args": ["secure-vault-mcp"]
    }
  }
}

From source

git clone https://github.com/mdfifty50-boop/secure-vault-mcp.git
cd secure-vault-mcp
npm install
node src/index.js

Tools

store_secret

Store an encrypted secret with optional rotation policy.

ParamTypeDefaultDescription
namestringrequiredSecret name (e.g. "openai_api_key")
valuestringrequiredSecret value — encrypted immediately
servicestring"default"Service this secret belongs to
rotation_policystring"none""none", "daily", "weekly", "monthly"

get_agent_token

Issue a short-lived, scoped token. The agent receives an opaque token ID, never the raw secret.

ParamTypeDefaultDescription
agent_idstringrequiredRequesting agent identifier
servicestringrequiredService to get a token for
scopestring"read""read", "write", "admin"
ttl_secondsnumber300Token TTL (10s to 86400s)

rotate_secrets

Rotate all secrets for a service. Old tokens are invalidated.

ParamTypeDescription
servicestringService whose secrets to rotate
new_valuestringNew secret value

audit_secret_access

View who accessed what secrets over a time range.

ParamTypeDefaultDescription
time_rangestring"24h""1h", "6h", "24h", "7d", "all"
agent_idstringoptionalFilter by agent
secret_namestringoptionalFilter by secret

scan_config_for_leaks

Scan config text for exposed secrets. Detects AWS keys, GitHub tokens, OpenAI/Anthropic keys, Slack tokens, Stripe keys, private key blocks, bearer tokens, and generic credentials using 12 regex patterns.

ParamTypeDefaultDescription
config_textstringrequiredConfig content to scan
source_labelstring"unknown"Label for audit trail

inject_secret_to_request

Return a request with the secret injected server-side. The agent provides a template with {{SECRET}} placeholder and a valid token ID.

ParamTypeDescription
token_idstringToken from get_agent_token
request_templatestringTemplate with {{SECRET}} placeholder

Resources

URIDescription
secure-vault://secretsAll stored secret names with metadata (no raw values)

Usage Pattern

1. store_secret — store credentials at setup time
2. get_agent_token — agent requests a scoped, time-limited token
3. inject_secret_to_request — inject secret into API call template
4. rotate_secrets — rotate when needed, old tokens auto-invalidate
5. scan_config_for_leaks — check config files before committing
6. audit_secret_access — review access trail

Security Model

  • Secrets encrypted at rest with AES-256-GCM using a server-generated key
  • Agents receive opaque token IDs, never raw secret values
  • Tokens are scoped (read/write/admin) and time-limited (default 5 minutes)
  • Token rotation invalidates all outstanding tokens for the rotated secret
  • Full audit trail of every store, token issuance, and injection
  • In-memory storage — secrets exist only for the server session lifetime

Tests

npm test

License

MIT

Reviews

No reviews yet

Be the first to review this server!

Secure Vault MCP Server - Encrypted secrets and credential management for agents | MCP Marketplace