# SecureInput (npm · secureinput)

Type API keys into a native inline input instead of the chat; delivered to a local command or .env.

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- mcpb · `secureinput-release-0.1.1.mcpb`: 46/100, [markdown](https://verifymcp.io/servers/r69shabh-secureinput/secureinput-release.md), [page](https://verifymcp.io/servers/r69shabh-secureinput/secureinput-release)
- npm · `secureinput`: 66/100 (this document), [markdown](https://verifymcp.io/servers/r69shabh-secureinput/secureinput.md), [page](https://verifymcp.io/servers/r69shabh-secureinput/secureinput)

## Channel facts

- Registry: `npm`
- Package: `secureinput`
- Version: `0.1.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 33 of 106 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 48/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 11 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 31/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 298 tokens (~42/item across 7 items; 6 tools + 1 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 67/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.
  - Supports UI / widget rendering.

## Install

### How do I install the SecureInput MCP server?

SecureInput runs locally as an npm package, launched with npx -y secureinput mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add r69shabh-secureinput -- npx -y secureinput mcp
```

### Cursor

```json
{
  "mcpServers": {
    "r69shabh-secureinput": {
      "command": "npx",
      "args": [
        "-y",
        "secureinput",
        "mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "r69shabh-secureinput": {
      "command": "npx",
      "args": [
        "-y",
        "secureinput",
        "mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add r69shabh-secureinput -- npx -y secureinput mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "r69shabh-secureinput": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "secureinput",
        "mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add r69shabh-secureinput --command npx --arg -y --arg secureinput --arg mcp
```

### Hermes

```yaml
mcp_servers:
  r69shabh-secureinput:
    command: "npx"
    args: ["-y", "secureinput", "mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "r69shabh-secureinput": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "secureinput",
        "mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add r69shabh-secureinput -t stdio -c npx -a -y secureinput mcp
```

### Other

```json
{
  "mcpServers": {
    "r69shabh-secureinput": {
      "command": "npx",
      "args": [
        "-y",
        "secureinput",
        "mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-17 (score 64, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-15 (score 63, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-13 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-11 (score 61, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-09 (score 60)

First indexed and scored.

## MCP tools (6)

### `submit_inline_secret` (~51 tokens)

Submit encrypted secure input

Submit an encrypted input envelope.

Input parameters:

- `ciphertext` (string, required)
- `iv` (string, required)
- `key` (string, required)
- `requestId` (string, required)
- `version` (number, required)

### `inline_request_status` (~31 tokens)

Wait for inline delivery status.

Input parameters:

- `requestId` (string, required)
- `waitSeconds` (integer)

### `request_secret` (~91 tokens)

Request a secret from the user

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.

Input parameters:

- `cwd` (string)
- `delivery` (required)
- `description` (string, required)
- `fields` (array, required)
- `timeoutSeconds` (integer)
- `title` (string, required)
- `waitSeconds` (integer)

### `check_secret_request` (~40 tokens)

Check a pending secure input request

Wait for request status. Use waitSeconds=45 to avoid repeated polling.

Input parameters:

- `requestId` (string, required)
- `waitSeconds` (integer)

### `cancel_secret_request` (~21 tokens)

Cancel a pending secure input request

Cancel pending input.

Input parameters:

- `requestId` (string, required)

### `secureinput_status` (~17 tokens)

SecureInput status

Get input mode and pending request IDs.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/r69shabh-secureinput/secureinput#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 65
- 2026-11-19: 65
- 2026-11-18: 64
- 2026-11-17: 64
- 2026-11-16: 63
- 2026-11-15: 63
- 2026-11-14: 62
- 2026-11-13: 62
- 2026-11-12: 61
- 2026-11-11: 61
- 2026-11-10: 60
- 2026-11-09: 60

## Common questions

### What is the SecureInput MCP server?

SecureInput is an MCP server listed in the public MCP registry as io.github.r69shabh/secureinput. Type API keys into a native inline input instead of the chat; delivered to a local command or .env. This page covers its npm package (secureinput).

### Is the SecureInput MCP server safe to use?

SecureInput scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the SecureInput MCP server expose?

SecureInput exposes 6 tools: submit_inline_secret, inline_request_status, request_secret, check_secret_request, cancel_secret_request, secureinput_status. Their descriptions and schemas cost roughly 251 tokens of context every time the server is loaded.

### Is the SecureInput MCP server still maintained?

SecureInput is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the SecureInput MCP server under?

SecureInput declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the SecureInput MCP server?

VerifyMCP ran 17 checks on SecureInput, covering Malware scan, Known CVEs, Install scripts, Dependency health and 13 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/secureinput
- Socket report: https://socket.dev/npm/package/secureinput
- Repository: https://github.com/r69shabh/secureinput
- Changelog RSS feed: https://verifymcp.io/servers/r69shabh-secureinput/secureinput.xml
- Changelog JSON feed: https://verifymcp.io/servers/r69shabh-secureinput/secureinput/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/r69shabh-secureinput/secureinput.json
- HTML version of this page: https://verifymcp.io/servers/r69shabh-secureinput/secureinput
