# vault-ask (npm · @erseni/vault-ask)

Request and send secrets for AI agents, end-to-end encrypted and never shown in the chat.

- Trust score: 85/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@erseni/vault-ask`: 85/100 (this document), [markdown](https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask.md), [page](https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask)

## Channel facts

- Registry: `npm`
- Package: `@erseni/vault-ask`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to Erseni/secrets-component).
  - Clear OSI-approved license (AGPL-3.0-or-later).
  - Actively maintained (last published 16 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 58/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1147 tokens (~382/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 57/100
  - Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 97/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 90% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "send_secret" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the vault-ask MCP server?

vault-ask runs locally as an npm package, launched with npx -y @erseni/vault-ask mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add com-erseni-vault-ask -- npx -y @erseni/vault-ask mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-erseni-vault-ask": {
      "command": "npx",
      "args": [
        "-y",
        "@erseni/vault-ask",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-erseni-vault-ask": {
      "command": "npx",
      "args": [
        "-y",
        "@erseni/vault-ask",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-erseni-vault-ask -- npx -y @erseni/vault-ask mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-erseni-vault-ask": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@erseni/vault-ask",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-erseni-vault-ask --command npx --arg -y --arg @erseni/vault-ask --arg mcp
```

### Hermes

```yaml
mcp_servers:
  com-erseni-vault-ask:
    command: "npx"
    args: ["-y", "@erseni/vault-ask", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-erseni-vault-ask": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@erseni/vault-ask",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-erseni-vault-ask -t stdio -c npx -a -y @erseni/vault-ask mcp
```

### Other

```json
{
  "mcpServers": {
    "com-erseni-vault-ask": {
      "command": "npx",
      "args": [
        "-y",
        "@erseni/vault-ask",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 85, +1)

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

### 2026-11-03 (score 84, +1)

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

### 2026-11-01 (score 83, +1)

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

### 2026-10-30 (score 82, +1)

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

### 2026-10-28 (score 81, +1)

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

### 2026-10-25 (score 80, +1)

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

### 2026-10-23 (score 79, +1)

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

### 2026-10-21 (score 78, +16)

- [security improvement] Malware scan: unverified → pass

## MCP tools (3)

### `request_secret` (~219 tokens)

Use this whenever you need a password, token, API key or other secret from the user, for example "I will give you my database password" or "you need my API key for X". Never ask the user to type or paste a secret into the chat. Asks the user for one or more secrets and writes them into a .env file or a file, without the values ever passing through this conversation. First call without request_id: returns a link. Show it to the user, then call again with the returned request_id; that call waits for the answer and writes the file with permissions 600. The result only contains names and lengths, never a value.

Input parameters:

- `env_file` (string): Write NAME=value lines into this .env file
- `file` (string): Write the single requested value into this file
- `names` (array): Names of the values to ask for, for example ["DB_PASSWORD"]
- `request_id` (string): The id returned by the first call
- `ttl_seconds` (integer)

### `run_with_secret` (~230 tokens)

Use this whenever a single command needs a password, token, API key or other secret from the user, for example "connect to the database with my password" or "deploy with my API token". Never ask the user to type or paste a secret into the chat. Asks the user for one or more secrets and runs exactly one command with them as environment variables. The user sees the command before entering anything, and only this command can receive the values. First call without request_id: returns a link. Show it to the user, then call again with the returned request_id; that call waits for the answer, runs the command and returns its exit code and its output with every value masked.

Input parameters:

- `command` (array): The command and its arguments, for example ["psql", "-h", "db.example.com"]
- `cwd` (string): Working directory for the command
- `names` (array): Names of the values to ask for, for example ["DB_PASSWORD"]
- `request_id` (string): The id returned by the first call
- `ttl_seconds` (integer)

### `send_secret` (~421 tokens)

Use this whenever the user asks you to generate, create or send them a password, token, API key or other secret, for example "generate a password for my database", "generier mir ein Passwort" or "send me the key". Do not generate a secret any other way and never write one into the chat. Generates the value locally (32 letters and digits unless length or charset say otherwise) or takes it from from_file or from_env, encrypts it on this machine and returns only a one-time link that shows the value once in the browser. Give the user that link. With env_file, file or command the same value also goes to that destination (needs name except for file), so the system and the link hold the same value. The result contains the link, its expiry and the length, never the value.

Input parameters:

- `charset` (string): Characters of the generated value, default alnum
- `command` (array): Also run this command with the value in the environment variable NAME, for example ["./scripts/set-db-password"]. Its output comes back with the value masked
- `cwd` (string): Working directory for relative paths and the command
- `env_file` (string): Also write NAME=value into this .env file (permissions 600)
- `file` (string): Also write the value into this file (permissions 600)
- `from_env` (string): Send the value of this environment variable of the server process instead of a generated value
- `from_file` (string): Send the content of this file instead of a generated value
- `label` (string): Label shown above the value on the page, for example "Database password for app@db.example.com"
- `length` (integer): Length of the generated value, default 32
- `name` (string): Name of the value, for example "DB_PASSWORD". Default label on the page, and the variable name for env_file and command
- `ttl_seconds` (integer): How long the link stays valid, default 86400

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask#diagnostics

## Score history

- 2026-11-05: 85
- 2026-11-04: 84
- 2026-11-03: 84
- 2026-11-02: 83
- 2026-11-01: 83
- 2026-10-31: 82
- 2026-10-30: 82
- 2026-10-29: 81
- 2026-10-28: 81
- 2026-10-27: 80
- 2026-10-26: 80
- 2026-10-25: 80
- 2026-10-24: 79
- 2026-10-23: 79
- 2026-10-22: 78
- 2026-10-21: 78
- 2026-10-20: 62
- 2026-10-19: 66

## Common questions

### What is the vault-ask MCP server?

vault-ask is an MCP server listed in the public MCP registry as com.erseni/vault-ask. Request and send secrets for AI agents, end-to-end encrypted and never shown in the chat. This page covers its npm package (@erseni/vault-ask).

### Is the vault-ask MCP server safe to use?

vault-ask scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 vault-ask MCP server expose?

vault-ask exposes 3 tools: request_secret, run_with_secret, send_secret. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.

### Is the vault-ask MCP server still maintained?

vault-ask is still listed as active in the MCP registry. We last reached this channel on 5 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 vault-ask MCP server under?

vault-ask declares the AGPL-3.0-or-later 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 vault-ask MCP server?

VerifyMCP ran 16 checks on vault-ask, 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.

## Links

- npm package: https://www.npmjs.com/package/@erseni/vault-ask
- Socket report: https://socket.dev/npm/package/@erseni/vault-ask
- Repository: https://github.com/Erseni/secrets-component
- Website: https://vault.erseni.com/ai-agents
- Changelog RSS feed: https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask.json
- HTML version of this page: https://verifymcp.io/servers/com-erseni-vault-ask/erseni-vault-ask