Vault MCP

io.github.Chill-AI-SpacePublished by GitHub account Chill-AI-Spacev0.2.1Updated Nov 10, 2026

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

VerifiedSTDIODesktop onlyDeveloper ToolsSecurity & Monitoring

Overview

AI-generated overview

A local MCP server that lets an assistant collect passwords and API keys from a user through a one-time web form, without the assistant ever seeing them.

What you can do
Create one-time credential request forms with a title, description, field definitions, destination and expiry time, receiving back a link and token to show the user. Poll a session's status to see whether the form is still pending, completed or expired. Field types cover text, password, email, telephone, number, long text and URL, with optional privacy labels such as secret, PII, attribute or credential. Optionally send the form link to a user through a Telegram bot.
When to use it
Useful when an assistant needs a user's credentials or personal data for a later step but should not read them itself, for example connecting an account or filling in a token. Suited to setups that already run or self-host a ZeroCreds server.
Requirements
Runs locally as an npm package (chillai-vault-mcp) over stdio, desktop only. Needs a ZeroCreds server, by default the public hosted one, and a required admin or integrator token in ZEROCREDS_TOKEN. Optional settings: ZEROCREDS_URL, ZEROCREDS_DEFAULT_DESTINATION, and ZEROCREDS_TG_BOT_TOKEN with ZEROCREDS_TG_CHAT_ID for Telegram delivery. Network access to the server is required.
Before you install
The assistant holds an admin or integrator token in ZEROCREDS_TOKEN, which grants access to the credential service. Submitted secrets are stored on the ZeroCreds server, by default a third-party hosted instance, so self-host if that matters. The optional Telegram bot token and chat ID send form links through Telegram. The README's example flow has the assistant read the collected token from the secret store afterwards, so check how credentials are retrieved.

Installation

In SourceWeft

  1. Open Vault MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

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

bash
npm install -g zerocreds-mcp

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

json
{  "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

VariableRequiredDescription
ZEROCREDS_URLnoServer URL (default: https://zerocreds.ru)
ZEROCREDS_TOKENyesAdmin or integrator token
ZEROCREDS_DEFAULT_DESTINATIONnoDefault destination name (default: local-dev)
ZEROCREDS_TG_BOT_TOKENnoTelegram bot token — auto-sends the link
ZEROCREDS_TG_CHAT_IDnoTelegram chat ID

Tools

zerocreds_ensure_server

Ensures the ZeroCreds MCP server is running. If it is not already running, this tool starts it in the background and waits for it to become ready.

Parameters: None.

Returns:

json
{  "status": "already_running | started | error | timeout",  "pid": 12345,  "message": "ZeroCreds MCP server is already running."}

Use case: Call this before zerocreds_create_session if you are unsure the server is running. It is idempotent — calling it multiple times is safe.

zerocreds_create_session

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

Claude shows url to the user, then polls zerocreds_check_status 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

zerocreds_check_status

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.

Scripts

ScriptDescription
scripts/ensure-server.shStarts the ZeroCreds MCP server if it is not already running. Idempotent.
scripts/health-check.shVerifies the server process is alive and the admin token file exists.

Run them from the repository root:

bash
./scripts/ensure-server.sh./scripts/health-check.sh

Or use the npm scripts:

bash
npm run ensure-startnpm run health-check

License

MIT

Source: README.md at commit 3c10156

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.1LatestSep 16, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.