Login Vault
REMOTE · VAULT.CLOUDFORBOTS.COM
Scoped login vault: your bot signs in to sites without ever seeing the password.
Available components
Last scanned (16 hours ago)
Scores higher than 46% of remote servers
Reachable. Last reached 17 Oct 2026.
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. How we score → Why this is hard to score →
Endpoint Security63
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 990 tokens (~90/item across 11 items; 11 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 17 Oct 26 63
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Probed https://vault.cloudforbots.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vault.cloudforbots.com | CN=YR1,O=Let's Encrypt,C=US | 16 Oct 2026 | 14 Jan 2027 | RSA 2048 | SHA256-RSA | 6e20892d3a356101741bde8c68b4d01dc3b |
| SANs: vault.cloudforbots.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of vault.cloudforbots.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| cloudforbots.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://vault.cloudforbots.com/mcp | Verified | 200 | |
| http (plaintext) | http://vault.cloudforbots.com/mcp | HTTPS enforced | 308 | https://vault.cloudforbots.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
audit_log ~51
Owner only. The last uses of your vault: who (bot label), which login, which domain, what happened. Never contains secrets.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | 1-200, default 50. |
No output schema declared.
No examples provided.
create_bot_key ~87
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.
| Name | Type | Req | Description |
|---|---|---|---|
| label | string | yes | Which bot, e.g. "invoice-bot". |
| logins | array | yes | Names of saved logins this bot may use. |
No output schema declared.
No examples provided.
delete_login ~35
Owner only. Delete a saved login, end its open sessions and remove it from every bot key.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | – |
No output schema declared.
No examples provided.
end_session ~24
End a session now and wipe its cookies.
| Name | Type | Req | Description |
|---|---|---|---|
| session | string | yes | – |
No output schema declared.
No examples provided.
list_logins ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
open_session ~227
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Saved login name. |
| prefetch | boolean | – | GET the url first to pick up CSRF cookies. Default true. |
| url | string | yes | The sign-in endpoint, e.g. https://example.com/session. |
No output schema declared.
No examples provided.
revoke_bot_key ~34
Owner only. Revoke a bot key right away and end every session it opened.
| Name | Type | Req | Description |
|---|---|---|---|
| bot_id | string | yes | – |
No output schema declared.
No examples provided.
save_login ~187
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.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Site the login belongs to, e.g. github.com. |
| name | string | yes | Short id, e.g. "github-bot" (letters, digits, . _ - @). |
| password | string | yes | – |
| 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 | yes | – |
No output schema declared.
No examples provided.
session_fetch ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | String or JSON. |
| headers | object | – | – |
| method | string | – | – |
| session | string | yes | – |
| url | string | yes | – |
No output schema declared.
No examples provided.
usage_and_upgrade ~37
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
weekly_report ~45
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · vault.cloudforbots.com
claude mcp add --transport http com-botrecipe-vault 'https://vault.cloudforbots.com/mcp'
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.