Login Vault

Ingested from the official MCP Registry

FastDrop pulled this entry from the official MCP Registry as com.botrecipe/vault and probed the endpoint. The maker did not submit it, so the outbound link is not endorsed and the description is not theirs.

If this is your server, claim the listing to edit it and take ownership. The registry index lists everything else still awaiting a probe.

Tools this endpoint exposes

Read directly from the endpoint on 16 Oct 2026. Not supplied by the maker.

• save_login

  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, no

• list_logins

  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

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

• create_bot_key

  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.

• revoke_bot_key

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

• open_session

  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 encr

• session_fetch

  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 rep

• end_session

  End a session now and wipe its cookies.

Is this tool yours?

Claim this listing and we’ll verify ownership before handing it over.