Q Ring logo

Q Ring

Unclaimed

by I4cTime

Quantum-inspired keyring for AI coding agents. Secure secrets with superposition, entanglement, tunneling, and teleportation — CLI + 44 MCP tools.

Install

$docker run --rm -p 8080:8080 qring-mcp

Set up this server

This server needs project-specific setup. Follow the project instructions; no reusable public launch command is available yet.

Project instructions
ai-agentsclaude-codecursorkeyringmcpmcp-serversecrets-managementsecurity

More in Security

Browse the full directory

Unclaimed listing

Is this your MCP server?

This listing was auto-indexed from the public record. Claim it to edit the page, set compatibility and unlock growth tools. Takes under two minutes.

Claim this server

Security profile

Claimed and verified servers get a weekly static scan that shows what the code can reach: external services, environment variables, shell commands, agent configuration folders, plus any dependencies with known advisories. Claim this listing to get one. How the security profile works

40 of 40 tools

Documented tools (40)

From project documentation. A server handshake does not verify each tool’s description or behavior.

agent_forget

Permanently delete a key from agent memory

agent_recall

Read a memory value, or list every stored key when no key is supplied

agent_remember

Persist a non-secret note in encrypted agent memory across sessions

agent_scan

Multi-project health pass with optional autoRotate for expired secrets

analyze_secrets

Usage profile: most-accessed, stale, never-accessed, no-rotation candidates

audit_log

Query the tamper-evident audit log filtered by key, action, and limit

check_project

Compare .q-ring.json manifest against the keyring for missing/expired/stale keys

delete_secret

Permanently remove a secret value (not undoable from q-ring)

detect_anomalies

Surface burst-read and off-hours findings from audit history

detect_environment

Resolve which env slug should drive superposition collapse for the current context

disentangle_secrets

Break the sync link between two keys (does not delete values)

entangle_secrets

Link two keys so future writes/rotations propagate the same value

env_generate

Render a complete .env body from the project manifest, with warnings for gaps

exec_with_secrets

Run a child command with secrets injected as env vars and any leaked values redacted from output

export_audit

Export audit events as jsonl, json, or csv for archival/SIEM

export_secrets

Render multiple secrets as .env or JSON for one-off export (skips approval-protected keys without a grant)

generate_secret

Generate a CSPRNG-backed value in a chosen format and optionally store it

get_project_context

Single redacted snapshot of secrets, env, manifest, hooks, and recent audit activity

get_secret

Read a secret value (collapses superposition, audits the read)

has_secret

Boolean existence check that respects decay (no audit read)

health_check

Read-only scope sweep: decay/stale/expired counts plus current anomalies

import_dotenv

Parse .env text and bulk-store every key/value pair (accepts raw content only — never reads files)

inspect_secret

Show metadata for one key (states, decay, entanglement, access count) without revealing the value

lint_files

Inspect a specific file list for hardcoded secrets with optional auto-fix to process.env.KEY

list_hooks

Show every registered hook with match criteria, type, and enabled flag

list_providers

Enumerate built-in validation providers and their auto-detect prefixes

list_secrets

List keys + metadata in scope (values never exposed); filter by tag, expiry, glob

register_hook

Register a shell/HTTP/signal side-effect that fires on write/delete/rotate

remove_hook

Detach a single hook by ID without touching any secrets

scan_codebase_for_secrets

Walk a directory tree and flag hardcoded secrets via regex + entropy heuristics

set_secret

Create or overwrite a single secret with optional TTL, per-env state, tags, rotation format

status_dashboard

Start a local SSE dashboard with live KPIs, secrets, hooks, and audit feed (returns a token-gated 127.0.0.1 URL)

teleport_pack

Encrypt selected secrets into a passphrase-protected AES-256-GCM bundle

teleport_unpack

Decrypt a teleport bundle and import each secret (with optional dry-run)

tunnel_create

Stash a value in process memory and return an opaque ID (never touches disk)

tunnel_destroy

Immediately remove a tunnel from memory before its TTL/reads run out

tunnel_list

Enumerate active tunnels with remaining read budget and TTL (IDs only)

tunnel_read

Fetch a tunneled value by ID — may self-destruct on read

validate_secret

Hit the upstream service (OpenAI/Stripe/GitHub/AWS/HTTP) to confirm a single key is still live

verify_audit_chain

Recompute the audit hash chain and report the first break point if tampered

Tool change history

Compared across complete checks of the same configuration. Tools were listed, not invoked. Input-schema changes are not measured here.

No complete tool checks yet.

FAQ

Questions about Q Ring MCP Server

How do I connect Q Ring MCP Server to Claude?
The listing records `docker run --rm -p 8080:8080 qring-mcp` as its setup step. Run it, then follow the repository's instructions for the client configuration; the listing names Claude Desktop, Claude Code, Cursor as compatible clients.
Is Q Ring MCP Server free?
The listed licence is AGPL-3.0. Check the upstream terms for permitted use and commercial requirements; a public repository does not by itself mean the software is free or open source. Connected APIs and hosted services may have separate charges.
What can Q Ring MCP Server do?
Q Ring MCP Server documents 40 tools to the agent, including agent_forget, agent_recall, agent_remember. The descriptions above come from project documentation. A live handshake does not test individual tool behavior.