A
licenseNot graded
qualityD
maintenanceZero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.
15 npm
1
MIT
Login Vault
Server Details
Scoped login vault: your bot signs in to sites without ever seeing the password.
If you are the author of this connector, you can claim ownership by verifying the domain or GitHub account it belongs to. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
- Status
- Healthy
- Uptime
- 100.0% over the last 24 hours
- Last Tested
- Transport
- Streamable HTTP · MCP 2025-11-25
- URL
- ChatGPT
- –
- Claude
- –
TDQS
A3.7/5.0
Scored across 11 tools
Disambiguation4/5
Tools separate cleanly into login CRUD (save/delete/list), session lifecycle (open/end/fetch), bot-key management (create/revoke), and observability (audit_log, weekly_report, usage_and_upgrade). The only mild overlap is between audit_log (raw recent events) and weekly_report (7-day summary), but their descriptions make the boundary clear enough.
Naming Consistency4/5
Everything is lowercase snake_case, which is consistent, and most names follow verb_noun (save_login, open_session, create_bot_key). A few deviations break the pattern—session_fetch is noun_verb, and audit_log/weekly_report are noun/adjective forms—but overall still predictable.
Tool Count5/5
11 tools is well-scoped for a credential vault, with each tool covering a distinct credential, session, key, or reporting operation. No redundancy or padding.
Completeness4/5
Login, session, bot-key, and reporting lifecycles are well covered with clear owner/bot scope handling. The main gap is the absence of an update_login (to rotate credentials or change scope/caps), which agents must currently emulate via delete + save.
Available Tools
11 toolsaudit_logAInspect
Owner only. The last uses of your vault: who (bot label), which login, which domain, what happened. Never contains secrets.
Inputs: limit.
create_bot_keyAInspect
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.
Inputs: label (required), logins (required).
delete_loginAInspect
Owner only. Delete a saved login, end its open sessions and remove it from every bot key.
Inputs: name (required).
end_sessionCInspect
End a session now and wipe its cookies.
Inputs: session (required).
list_loginsAInspect
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.
Inputs: no named parameters.
open_sessionAInspect
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.
Inputs: url (required), name (required), as, form, +2 more.
revoke_bot_keyAInspect
Owner only. Revoke a bot key right away and end every session it opened.
Inputs: bot_id (required).
save_loginAInspect
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.
Inputs: name (required), domain (required), password (required), username (required), +2 more.
session_fetchAInspect
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.
Inputs: url (required), session (required), body, method, +1 more.
usage_and_upgradeAInspect
Show today's usage for your key or IP and the $9/month upgrade link. Free tier: 500 calls/day. Not metered.
Inputs: no named parameters.
weekly_reportBInspect
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.
Inputs: no named parameters.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Related MCP Connectors
Password vault for AI agents with scoped, user-approved access
Logs your AI agent into websites, catches verification codes, and asks you before anything risky.
Let AI agents use any website you're logged in to. Sessions stay encrypted on your machine.
Your own browser in the cloud, logged in to your sites, shared by you and your AI.
Related MCP Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to request passwords, API keys, passkeys, and other secrets from a person through one-time links encrypted in the browser, then store them in a local vault the agent can use without ever seeing them. Secrets can be referenced in commands and outputs are redacted, so agents can sign in or call APIs without exposing credentials in chat.2,544 npmMIT
- AlicenseNot gradedqualityDmaintenanceEnables AI agents to securely fill web forms with credentials from SecureVault, keeping raw secrets hidden from the agent.8 npmMIT
- AlicenseBqualityBmaintenanceEnables AI agents to browse, click, type and read on any website the user is logged in to, using encrypted local sessions with multiple named accounts per site. It behaves like a human, asks for confirmation before risky actions, and hands control back for CAPTCHAs or 2FA.28MIT
Try in Browser
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd
Glama MCP Gateway
Add one secure layer between your agents and this server.