# Login Vault (remote · vault.cloudforbots.com)

Scoped login vault: your bot signs in to sites without ever seeing the password.

- Trust score: 63/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-17

## Components

- remote · `vault.cloudforbots.com`: 63/100 (this document), [markdown](https://verifymcp.io/servers/com-botrecipe-vault/vault.md), [page](https://verifymcp.io/servers/com-botrecipe-vault/vault)

## Channel facts

- Endpoint: `https://vault.cloudforbots.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-10-17.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 990 tokens (~90/item across 11 items; 11 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% 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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_login" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 12 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.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Login Vault MCP server?

Login Vault is a hosted endpoint at https://vault.cloudforbots.com/mcp, so there is nothing to install locally. 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 --transport http com-botrecipe-vault 'https://vault.cloudforbots.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-botrecipe-vault": {
      "url": "https://vault.cloudforbots.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-botrecipe-vault": {
      "type": "http",
      "url": "https://vault.cloudforbots.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-botrecipe-vault]
url = "https://vault.cloudforbots.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-botrecipe-vault": {
      "type": "remote",
      "url": "https://vault.cloudforbots.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-botrecipe-vault --url 'https://vault.cloudforbots.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-botrecipe-vault:
    url: "https://vault.cloudforbots.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-botrecipe-vault": {
      "Transport": "http",
      "Url": "https://vault.cloudforbots.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-botrecipe-vault -t streamable-http -u 'https://vault.cloudforbots.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-botrecipe-vault": {
      "type": "http",
      "url": "https://vault.cloudforbots.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-10-17 (score 63)

First indexed and scored.

## MCP tools (11)

### `save_login` (~187 tokens)

Owner only (your Pro key, never a bot key). Store one login sealed with AES-256-GCM, with a scope: allowed hosts, allowed methods, a daily session cap and session TTL. Run it from your own machine, not inside the bot. The password and TOTP secret are never returned by any tool. Free watch-only stores nothing and logs would_use_vault.

Input parameters:

- `domain` (string, required): Site the login belongs to, e.g. github.com.
- `name` (string, required): Short id, e.g. "github-bot" (letters, digits, . _ - @).
- `password` (string, required)
- `scope` (object): Where and how this login may be used.
- `totp_secret` (string): Optional base32 TOTP secret, so {{totp}} can fill 2FA codes.
- `username` (string, required)

### `list_logins` (~48 tokens)

List saved logins (name, domain, scope, sessions today; never secrets). With your owner key it also lists bot keys. A bot key only sees the logins it was granted.

### `delete_login` (~35 tokens)

Owner only. Delete a saved login, end its open sessions and remove it from every bot key.

Input parameters:

- `name` (string, required)

### `create_bot_key` (~87 tokens)

Owner only. Make a per-bot key (vk_...) that can only open sessions on the logins you name. Shown once; we store only its hash. Revoke any time with revoke_bot_key.

Input parameters:

- `label` (string, required): Which bot, e.g. "invoice-bot".
- `logins` (array, required): Names of saved logins this bot may use.

### `revoke_bot_key` (~34 tokens)

Owner only. Revoke a bot key right away and end every session it opened.

Input parameters:

- `bot_id` (string, required)

### `open_session` (~227 tokens)

Sign in with a saved login without seeing it. The server fills {{username}}, {{password}} and {{totp}} into your form, posts it to url (https, inside the login's allowed hosts), keeps the cookies encrypted, and returns an opaque session id. Checked against the login's scope and daily cap; logged to the audit log. If the site shows a CAPTCHA or new-device check, the reply suggests next_step request_human (Human Handoff relay). Free watch-only logs would_use_vault and signs in nowhere.

Input parameters:

- `as` (string): Body encoding. Default form.
- `form` (object): Fields to send, values may use {{username}}, {{password}}, {{totp}}. Default {"username":"{{username}}","password":"{{password}}"}.
- `method` (string): Default POST.
- `name` (string, required): Saved login name.
- `prefetch` (boolean): GET the url first to pick up CSRF cookies. Default true.
- `url` (string, required): The sign-in endpoint, e.g. https://example.com/session.

### `session_fetch` (~93 tokens)

Make one request inside an open session. url must be https inside the login's allowed hosts and the method must be in its allowed methods. The password, TOTP secret and codes are redacted from the reply; cookies never leave the vault.

Input parameters:

- `body`: String or JSON.
- `headers` (object)
- `method` (string)
- `session` (string, required)
- `url` (string, required)

### `end_session` (~24 tokens)

End a session now and wipe its cookies.

Input parameters:

- `session` (string, required)

### `audit_log` (~51 tokens)

Owner only. The last uses of your vault: who (bot label), which login, which domain, what happened. Never contains secrets.

Input parameters:

- `limit` (integer): 1-200, default 50.

### `weekly_report` (~45 tokens)

Plain-English summary of the last 7 days: where your bots needed to sign in (by domain), sessions opened, blocked attempts, by bot. Read-only. Needs a key.

### `usage_and_upgrade` (~37 tokens)

Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-botrecipe-vault/vault#diagnostics

## Score history

- 2026-10-17: 63

## Common questions

### What is the Login Vault MCP server?

Login Vault is an MCP server listed in the public MCP registry as com.botrecipe/vault. Scoped login vault: your bot signs in to sites without ever seeing the password. This page covers its hosted endpoint (https://vault.cloudforbots.com/mcp).

### Is the Login Vault MCP server safe to use?

Login Vault scores 63 out of 100 on VerifyMCP. 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 Login Vault MCP server expose?

Login Vault exposes 11 tools: save_login, list_logins, delete_login, create_bot_key, revoke_bot_key, and 6 more. Their descriptions and schemas cost roughly 868 tokens of context every time the server is loaded.

### Does the Login Vault MCP server require authentication?

No. We connected to Login Vault without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Login Vault MCP server still maintained?

Login Vault is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://vault.cloudforbots.com/mcp
- Website: https://vault.cloudforbots.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-botrecipe-vault/vault.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-botrecipe-vault/vault.json
- HTML version of this page: https://verifymcp.io/servers/com-botrecipe-vault/vault