auth-vault
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| LOG_LEVEL | No | Logging level: debug, info, warn, error | info |
| VAULT_ROOT | No | Storage directory for encrypted vault files | ./vault |
| AUTH_SSE_PORT | No | Enable SSE mode on given port (empty = STDIO mode) | |
| BROWSER_TIMEOUT | No | Browser operation timeout (ms) | 30000 |
| BROWSER_HEADLESS | No | Run Playwright in headless mode | true |
| AUTH_BIND_ADDRESS | No | Explicit bind address for SSE mode | auto (Tailscale) |
| VAULT_ENCRYPTION_KEY | No | AES-256 key (64 hex chars, persist for data survival) | auto-generated |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| store_credentialsB | Store login credentials for a service securely with AES-256-GCM encryption |
| get_credentialsC | Retrieve stored credentials by ID. Returns decrypted username and password. |
| list_credentialsC | List stored credentials, optionally filtered by service |
| delete_credentialsB | Permanently delete stored credentials by ID |
| get_credentials_for_serviceB | Get all credentials for a specific service |
| generate_qrA | Generate a Google Authenticator QR code for a stored credential's TOTP secret |
| list_servicesA | List all supported services with their login templates |
| get_service_templateB | Get detailed login template for a specific service |
| add_serviceB | Register a custom service login template at runtime |
| browser_launchC | Launch a new browser session for logging into a service |
| browser_navigateB | Navigate the browser to a URL within an active session |
| browser_closeA | Close a browser session |
| list_sessionsA | List all active browser sessions |
| login_serviceC | Automate login to a service using stored credentials. Launches browser, fills form, handles captcha. |
| detect_captchaC | Check the current page for captcha challenges |
| solve_captchaB | Solve a detected captcha on the current page using configured captcha service |
| click_submitC | Click the submit button on the login form (useful after captcha solving) |
| detect_2faB | Check the current page for a 2FA code challenge |
| solve_2faA | Generate a TOTP code from the stored secret and fill it into the 2FA input field |
| check_sessionA | Check if a browser session is still active and optionally verify login status |
| store_secretB | Store an API key, access token, or other secret encrypted with AES-256-GCM |
| get_secretA | Retrieve a stored secret by ID (returns decrypted value) |
| list_secretsB | List stored secrets, optionally filtered by service or kind |
| delete_secretB | Permanently delete a stored secret by ID |
| vault_healthB | Comprehensive health check of the auth-vault system — encryption, storage, services, sessions |
| test_credentialB | Test if credentials exist in vault and validate their structure (returns non-sensitive info only) |
| test_session_integrityC | Check if browser sessions are alive and can interact with pages |
| test_totpC | Verify TOTP secret by generating a current code and optionally checking against expected value |
| test_service_selectorB | Test if a CSS selector works on a service's login page (launches browser, checks selector matches) |
| test_secret_expiryA | Check all secrets for expiration — identifies expired, expiring soon, or valid secrets |
| test_browser_cdpB | Test Chrome DevTools Protocol connectivity — verify CDP endpoint is reachable |
| test_all_servicesA | Test all registered service templates — check if login pages are reachable |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/borysttk/auth-vault-template'
If you have feedback or need assistance with the MCP directory API, please join our Discord server