Vault MCP server

by Chill-AI-Space·io.github.Chill-AI-Space/vault·v0.2.1·2 stars

No reviews yet

MCP server for credential isolation — bots use passwords and API keys without seeing them

B72/100grade B

Write a review Install

What users say

No reviews yet

Be the first

Safety scan

B72/100

full report

Adoption

Growing

2 stars35 downloads/wk

Reviews

Write one

Nobody has reviewed Vault MCP yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vault MCP tools (10, 2 write)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

vault_add
Securely add a new credential to the vault. Opens a browser form where the user enters their password directly — the password NEVER passes through the AI agent. Supports templates for popular services (github, jira, stripe, etc.).
vault_api_request
Make an API request with stored credentials. The API key is injected automatically — the bot never sees it. Supports header, query param, and basic auth patterns.
vault_check
Verify a credential is valid and ready to use. Checks existence, active status, required fields, and expiration.
vault_import
Import API keys from a .env file. Each key is stored as an encrypted api_key credential. The .env values pass through memory only — never returned to the agent.
vault_list
List all available credentials in the vault. Returns only site IDs and types — no secrets.
vault_login
Log into a website using stored credentials. The bot never sees the password — Vault fills the login form via Chrome DevTools Protocol. Supports TOTP 2FA if configured.
vault_removewrite action
Remove a credential from the vault permanently.
vault_status
Check the status of a specific credential: active/inactive, last used, audit count.
vault_templates
List available credential templates for popular services. Templates auto-fill login URLs and CSS selectors.
vault_updatewrite action
Update an existing credential. Opens a browser form to enter new password/API key — the secret NEVER passes through the AI agent.

Public scan report

scanner v0.1.10 · 2026-09-28 · same rubric, same numbers if you re-run it

1 high

Code scan45 source files scanned13/25
–Live reliabilityno gateway calls yet and no remote to proben/a
–Tool poisoningtools not inspected (local package is not executed); not countedn/a
Auth qualitylocal package, no credentials required12/15
Maintenancelast push 22 days ago15/15
Maintainer identityregistry namespace matches repository owner7/10

Findings (1)

highShell command built from a string (injection risk)exec.shell-concat

dist/tools/vault-add.js: …'win32' ? 'start' : 'xdg-open'; exec(`${openCmd} "${url}"`); } // Wait for the user …

Overall 72/100. Components that don't apply are left out of the denominator. Any critical finding is an F.Rubric Appeal a finding JSON

How Vault MCP compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score: 72/100; higher than 38% of 48,255 servers
Tools: 10; the typical server has 7
Tools that change things: 20%; typical: 0%. Fewer write tools means less an agent can break
GitHub stars: 2; more than 75% of 28,688 servers
Downloads a week: 35; more than 25% of 12,191 servers with a package

What its tools let an agent do: 8 read · 2 change

Install Vault MCP in Claude Code, Cursor or VS Code

Runs npx -y chillai-vault-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vault -- npx -y chillai-vault-mcp

Add to Cursor

What the publisher says

From the Vault MCP repository's README, as published. We do not edit it. Read it on GitHub

zerocreds-mcp

MCP server for ZeroCreds — collect credentials from users without exposing them to the LLM.

How it works

Claude                    ZeroCreds Server            User
  │                            │                        │
  ├─zerocreds_create_session──►│                        │
  │◄─{ token, url }────────────┤                        │
  │                            │                        │
  │  "Please fill: <url>"──────────────────────────────►│
  │                            │◄──── form submit ───────┤
  │                            │  (credentials saved)    │
  │                            │                        │
  ├─zerocreds_check_status─────►│                        │
  │◄─{ status: "done" }────────┤                        │
  │                            │                        │
  │  (proceeds — never saw the credentials)

Setup

npm install -g zerocreds-mcp

Add to ~/.claude/mcp.json (Claude Code) or Claude Desktop config:

{
  "mcpServers": {
    "zerocreds": {
      "command": "zerocreds-mcp",
      "env": {
        "ZEROCREDS_URL": "https://zerocreds.ru",
        "ZEROCREDS_TOKEN": "your-admin-or-integrator-token",
        "ZEROCREDS_DEFAULT_DESTINATION": "local-dev",
        "ZEROCREDS_TG_BOT_TOKEN": "optional — sends link via Telegram",
        "ZEROCREDS_TG_CHAT_ID": "optional"
      }
    }
  }
}

Environment variables

Tools

zerocredscreatesession

Creates a one-time form session. Returns { token, url, expires_at }.

Claude shows url to the user, then polls zerocredscheckstatus every 5–10 seconds.

Parameters:

title (required) — form heading
fields (required) — array of { name, label, type?, placeholder?, required?, level? }
description — optional subtext
destination — named destination from server config; overrides env default
ttl_minutes — link expiry (default: 30)

Field types: text, password, email, tel, number, textarea, url

Field levels (optional, shown to user as privacy indicator): secret · pii · attribute · credential

zerocredscheckstatus

Polls session status. Returns { status: "pending" | "done" | "expired" }.

Example agent flow

User: "Log me into GitHub"

Claude: [zerocreds_create_session]
  title: "Connect GitHub"
  fields: [
    { name: "token", label: "Personal Access Token", type: "password" }
  ]
→ { token: "abc123", url: "https://zerocreds.ru/f/abc123" }

Claude: "Please fill in your token here: https://zerocreds.ru/f/abc123"

[polls zerocreds_check_status every 5s]
→ { status: "done" }

Claude: "GitHub connected! Proceeding..."
[reads token from secret store via configured destination]

Self-hosting

See zerocreds-server to run your own instance.

License

MIT

Nothing above is checked by us. What we check is on the safety report.

Vault MCP: common questions

Is Vault MCP server safe?: Mostly: it is graded B (72/100). Read the Vault MCP safety report
How do I install Vault MCP?: It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vault MCP need an API key?: Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vault MCP maintained?: The last commit was 59 days ago (2026-09-05). The latest release is v0.2.1.
How does Vault MCP compare with other MCP servers?: safety score 72/100 (higher than 38% of 48,255 servers); tools 10 (the typical server has 7); tools that change things 20% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.