SecureInput
Related Servers
Alternatives to SecureInput
No user-submitted related servers found.
Related Servers
- AlicenseAqualityBmaintenanceEnables AI agents to ask users for credentials, secrets, and sensitive data through local browser forms that the model never sees, then resolve and use those values only at approved points of use. Also supports blind web capture, SSH key provisioning, and writes to .env files, SQL databases, and APIs, with the agent receiving only structural results.1339 npm1MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to securely inject API keys and secrets into environment files, configs, or commands without the agent ever seeing the secret values.1 npmMIT
- AlicenseAqualityBmaintenanceSecrets manager for AI coding agents. The model only sees secret names; values are injected into the child process at exec time, every command needs your approval in a native dialog, and output is redacted before it returns to the model.270 PyPI1Apache 2.0
- AlicenseNot gradedqualityCmaintenanceLets AI coding agents read project documentation and secret metadata, then use credentials by injecting them into child processes while redacting the values from all output. Agents can deploy, migrate databases, or SSH using real secrets without the values ever entering their context, transcripts, or logs.MIT
- AlicenseNot gradedqualityBmaintenanceEnables an agent to run commands with secrets and sudo passwords that the user supplies in a separate popup or dialog, keeping those values out of the agent's context and redacting them from output. It also lets users edit drafts and commit messages in their own editor and send the resulting text back to the agent.MIT
- AlicenseCqualityCmaintenanceEnables AI agents to securely store and manage encrypted secrets locally while using them indirectly through environment-variable injection or file writes, so plaintext values never enter the agent's context.8MIT
This server cannot be deployed
TDQS
Scored across 6 tools
The set has overlapping status tools: inline_request_status, check_secret_request, and secureinput_status all report/wait on status, and submit_inline_secret vs request_secret could be confused as initiation paths. Descriptions help somewhat, but the inline-versus-secret request boundaries are not fully clear.
Mostly snake_case, but the set mixes verb-first names (submit_inline_secret, check_secret_request, cancel_secret_request) with noun-status names (inline_request_status, secureinput_status). The 'secureinput' token also breaks the underscore pattern.
Six tools are reasonable for a focused secure-input workflow. The only concern is that three status-related tools feel somewhat redundant, making it slightly over-scoped but still well within range.
The surface covers the core lifecycle: request creation, inline submission, status checks, and cancellation. Minor gaps exist around historical/listing or cleanup operations, but no obvious blocking dead end for the stated secure-input purpose.