SecureInput runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 3 Nov 2026.
Local API key input for AI agents, with command and .env delivery.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(process.execPath, args, {
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Alternatives to SecureInput
same job, measured the same wayLocal memory engine for AI agents with knowledge graphs, forgetting, and semantic recall
CVE lookups (NVD) and dependency-manifest audits (OSV) for AI agents. No API keys.
Secure durable memory and bounded context for AI agents, with hosted OAuth and local Lite support.
Zero-Trust PII & secrets sanitizer for AI agents with in-memory local redaction.
Local security scanner for AI agents: SAST, SCA, secrets, IaC; verifies exploit and fix.
Local AES-256-GCM vault for AI agents. Secrets stay local, LLMs never see real API keys.
Secure USDC payments for AI agents on Base blockchain with budget controls and instant settlement.
Secure encoding-aware local workspace runtime for AI agents
SecureInput — questions
Answers built from our own checks of this server.