q-ring runs on your own machine — the client starts it, so there is no endpoint to ping. 278 installs a week from npm. Last commit 31 Oct 2026.
OS keychain secrets for AI coding agents, over MCP.
We read the source, 1 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(opts.command, opts.args, {
const lastUpdate = snap ? "updated " + fmtRelative(snap.timestamp) : "—";
for (const [k, v] of Object.entries(process.env)) {
RUN apt-get update && apt-get install -y --no-install-recommends ca-certificates curl git && curl -fsSL https://deb.nodesource.com/setup_24.x | bash - && apt-get install -y --no-install-recommends nodejs && npm install -g [email protected] [email protected] && node --version && curl -Ls…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add q-ring -- npx -y @i4ctime/q-ring
{
"mcpServers": {
"q-ring": {
"command": "npx",
"args": [
"-y",
"@i4ctime/q-ring"
]
}
}
}
[mcp_servers.q-ring]
command = "npx"
args = ["-y", "@i4ctime/q-ring"]
{
"mcpServers": {
"q-ring": {
"command": "npx",
"args": [
"-y",
"@i4ctime/q-ring"
]
}
}
}
{
"servers": {
"q-ring": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@i4ctime/q-ring"
]
}
}
}
Optional settings from the registry entry, left out of the block above:
QRING_BACKEND (Secret storage backend. Defaults to the OS keychain; set to "file" for headless hosts with no Secret Service (CI, containers)), QRING_FILE_PASSPHRASE (Passphrase for the encrypted file backend (AES-256-GCM). Required only when QRING_BACKEND=file — without it the file backend fails closed), QRING_FILE_BACKEND_PATH (Custom path for the encrypted file store (default: ~/.config/q-ring/file-backend.enc)), QRING_CONFIG_DIR (Directory for q-ring's registries — hooks, entanglement, approvals, canary webhooks, agent memory (default: ~/.config/q-ring)).
One firewall and password manager for all your AI coding agents' MCP servers and secrets.
BridgeGuard MCP Server - Cross-chain bridge security audit tools for AI coding agents. Scan bri...
Zero-install security baseline for AI coding agents — OWASP/CWE-cited rules over MCP.
Autonomous log surgery & secret redaction MCP server for AI coding agents.
Real-time semantic security for AI coding agents and MCP tools
Secure secrets proxy for AI agents — manages API keys so agents never see raw credentials.
Secure Linux sandboxes for AI agents, as MCP tools.
Security firewall for AI agents — scans MCP calls for injection, secrets, and risks.
Answers built from our own checks of this server.