veilform
Related Servers
Alternatives to veilform
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceLocal MCP server for entering API keys outside chat. Deliver secrets to commands or .env files using an inline MCP App or a paired localhost browser.6MIT
- 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,904 npmMIT

secure-browser-mcpofficial
AlicenseNot gradedqualityBmaintenanceEnables secure browser automation by letting agents fill Turnkey-stored secrets into web forms without the secret values ever appearing in the conversation, transcript, or model context.5 npm6MIT- AlicenseNot gradedqualityDmaintenanceZero-knowledge credential injection for AI agents. Your agent authenticates to websites and APIs without ever seeing a password, TOTP code, or API key.15 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to securely control a user's existing Chrome profile locally, providing typed browser actions, form and editor support, WordPress workflows, terminal automation, and Figma inspection with policy-based authorization and redacted auditing.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI assistants to securely control a real, logged-in browser with per-site permissions, per-action approvals, secret redaction, and a tamper-evident audit log, all locally without a cloud relay.377,314 npm1MIT
TDQS
Scored across 13 tools
Each tool has a genuinely distinct purpose grouped around secrets, blind input, SSH, and web capture. Minor potential confusion between secret_request and blind_input (both open an intake page) and between blind_input and blind_input_preview, but descriptions clearly differentiate (preview validates only, no values).
Tools are consistently grouped by domain prefix (secret_*, ssh_*, web_*, blind_input_*) with predictable suffixes. Slight inconsistency in that some read as resource_verb (secret_list) while others are verb_noun (ssh_key_provision), but readability is high throughout.
13 tools is a well-scoped count for a security-focused server covering multiple sub-domains (secrets lifecycle, SSH, web automation, blind input). Each tool earns its place with no obvious redundancy.
Covers a full secret lifecycle (request, list, rotate, delete, use, write) plus SSH key provisioning/exec and web login/capture, with preview and wait support. Reading secret values is deliberately omitted by design, so coverage is strong for the stated purpose.