English Français العربية

io.github.mdfifty50-boop/secure-vault

Registre officiel Sécurité

Encrypted secrets and credential management for agents

Code source Documentation

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package secure-vault-mcp
Claude Code 
claude mcp add secure-vault -- npx -y secure-vault-mcp@0.1.1
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "secure-vault": {
            "command": "npx",
            "args": [
                "-y",
                "secure-vault-mcp@0.1.1"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. secure-vault-mcp
  2. Install
  3. Tools
  4. Resources
  5. Usage Pattern
  6. Security Model
  7. Tests
  8. License

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

Questions fréquentes

Qu'est-ce que io.github.mdfifty50-boop/secure-vault ?

Encrypted secrets and credential management for agents

Comment installer io.github.mdfifty50-boop/secure-vault ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add secure-vault -- npx -y secure-vault-mcp@0.1.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.mdfifty50-boop/secure-vault ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.mdfifty50-boop/secure-vault est-il open source ?

Son code est public sur GitHub, mais le dépôt ne déclare pas de licence standard.

Qui maintient io.github.mdfifty50-boop/secure-vault ?

Il est publié par mdfifty50-boop. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.