SecureInput
MCPB · SECUREINPUT-RELEASE-0.1.0.MCPB
Local API key input for AI agents, with command and .env delivery.
Available components
Last scanned (19 hours ago)
Scores higher than 71% of MCPB servers
Category Security
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. How we score → Why this is hard to score →
Supply Chain Security23
- No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
- Known CVEs were checked across the 105 of 105 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
- No install/post-install scripts declared.Pass
- 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability31
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (fair).Partial
- Tool/resource definitions use about 298 tokens (~42/item across 7 items; 6 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
- Supports UI / widget rendering.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 2 Nov 26 37
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Analysed mcpb/https://github.com/r69shabh/secureinput/releases/download/v0.1.0/secureinput-release-0.1.0.mcpb
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | mcpb |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_secret_request Cancel a pending secure input request ~21
Cancel pending input.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
No output schema declared.
No examples provided.
check_secret_request Check a pending secure input request ~40
Wait for request status. Use waitSeconds=45 to avoid repeated polling.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
| waitSeconds | integer | – | – |
No output schema declared.
No examples provided.
inline_request_status ~31
Wait for inline delivery status.
| Name | Type | Req | Description |
|---|---|---|---|
| requestId | string | yes | – |
| waitSeconds | integer | – | – |
No output schema declared.
No examples provided.
request_secret Request a secret from the user ~91
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.
| Name | Type | Req | Description |
|---|---|---|---|
| cwd | string | – | – |
| delivery | – | yes | – |
| description | string | yes | – |
| fields | array | yes | – |
| timeoutSeconds | integer | – | – |
| title | string | yes | – |
| waitSeconds | integer | – | – |
No output schema declared.
No examples provided.
secureinput_status SecureInput status ~17
Get input mode and pending request IDs.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_inline_secret Submit encrypted secure input ~51
Submit an encrypted input envelope.
| Name | Type | Req | Description |
|---|---|---|---|
| ciphertext | string | yes | – |
| iv | string | yes | – |
| key | string | yes | – |
| requestId | string | yes | – |
| version | number | yes | – |
No output schema declared.
No examples provided.
How do I install the SecureInput MCP server?
SecureInput ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 22d6c9e65453f0c3940e8868605ba0e2395538a538d8ee53ca444247ad7f3a98; the commands to do that are on this page. If it does not match, do not open it.
mcpb · secureinput-release-0.1.0.mcpb
Download bundleCheck the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.
SHA-256
22d6c9e65453f0c3940e8868605ba0e2395538a538d8ee53ca444247ad7f3a98
macOS / Linux
echo "22d6c9e65453f0c3940e8868605ba0e2395538a538d8ee53ca444247ad7f3a98 secureinput-release-0.1.0.mcpb" | shasum -a 256 -c
Windows (PowerShell)
(Get-FileHash -Algorithm SHA256 .\secureinput-release-0.1.0.mcpb).Hash -eq "22d6c9e65453f0c3940e8868605ba0e2395538a538d8ee53ca444247ad7f3a98"
Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.
What is the SecureInput MCP server?
SecureInput is an MCP server listed in the public MCP registry as io.github.r69shabh/secureinput. Local API key input for AI agents, with command and .env delivery. This page covers its MCPB bundle (https://github.com/r69shabh/secureinput/releases/download/v0.1.0/secureinput-release-0.1.0.mcpb).
Is the SecureInput MCP server safe to use?
SecureInput scores 37 out of 100 on VerifyMCP. 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.
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.