SecureInput
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| SECUREINPUT_HOME | No | Override the SecureInput config directory. Defaults to ~/.secureinput/. | |
| SECUREINPUT_NO_OPEN | No | Set to 1 to prevent automatic browser opening. | |
| SECUREINPUT_WEB_DIR | No | Override the built web UI directory. |
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
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| submit_inline_secretC | Submit an encrypted input envelope. |
| inline_request_statusC | Wait for inline delivery status. |
| request_secretB | Collect secret input. Use {{fieldId}} in execute stdin/env, or map fields to write_env keys. Never put secrets in args. Returns requestId and status. |
| check_secret_requestC | Wait for request status. Use waitSeconds=45 to avoid repeated polling. |
| cancel_secret_requestC | Cancel pending input. |
| secureinput_statusB | Get input mode and pending request IDs. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| SecureInput |
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.