qring-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| NODE_ENV | No | Standard environment variable used as a fallback for environment detection if QRING_ENV is not specified. | |
| QRING_ENV | No | Sets the current environment context for secret resolution (e.g., dev, staging, prod). This determines which value is returned when a secret exists in multiple states (Superposition). |
Capabilities
Features and capabilities supported by this server
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_secret | Retrieve a secret by key. Collapses superposition if the secret has multiple environment states. Records access in audit log (observer effect). |
| list_secrets | List all secret keys with quantum metadata (scope, decay status, superposition states, entanglement, access count). Values are never exposed. Supports filtering by tag, expiry state, and key pattern. |
| set_secret | Store a secret with optional quantum metadata: TTL (decay), environment state (superposition), description, tags. |
| delete_secret | Remove a secret from the keyring. |
| has_secret | Check if a secret exists. Returns boolean. Never reveals the value. Respects decay — expired secrets return false. |
| export_secrets | Export secrets as .env or JSON format. Collapses superposition. Supports filtering by specific keys or tags. |
| import_dotenv | Import secrets from .env file content. Parses standard dotenv syntax (comments, quotes, multiline escapes) and stores each key/value pair in q-ring. |
| check_project | Validate project secrets against the .q-ring.json manifest. Returns which required secrets are present, missing, expired, or stale. Use this to verify project readiness. |
| env_generate | Generate .env file content from the project manifest (.q-ring.json). Resolves each declared secret from q-ring, collapses superposition, and returns .env formatted output. Warns about missing or expired secrets. |
| inspect_secret | Show full quantum state of a secret: superposition states, decay status, entanglement links, access history. Never reveals the actual value. |
| detect_environment | Detect the current environment context (wavefunction collapse). Returns the detected environment and its source (NODE_ENV, git branch, project config, etc.). |
| generate_secret | Generate a cryptographic secret (quantum noise). Formats: hex, base64, alphanumeric, uuid, api-key, token, password. Optionally save directly to the keyring. |
| entangle_secrets | Create a quantum entanglement between two secrets. When the source is rotated/updated, the target automatically receives the same value. |
| disentangle_secrets | Remove a quantum entanglement between two secrets. They will no longer synchronize on rotation. |
| tunnel_create | Create an ephemeral secret that exists only in memory (quantum tunneling). Never persisted to disk. Optional TTL and max-reads for self-destruction. |
| tunnel_read | Read an ephemeral tunneled secret by ID. May self-destruct if max-reads is reached. |
| tunnel_list | List active tunneled secrets (IDs and metadata only, never values). |
| tunnel_destroy | Immediately destroy a tunneled secret. |
| teleport_pack | Pack secrets into an AES-256-GCM encrypted bundle for sharing between machines (quantum teleportation). |
| teleport_unpack | Decrypt and import secrets from a teleport bundle. |
| audit_log | Query the audit log for secret access history (observer effect). Shows who accessed what and when. |
| detect_anomalies | Scan for anomalous secret access patterns: burst reads, unusual-hour access. Returns findings and recommendations. |
| health_check | Run a comprehensive health check on all secrets: decay status, staleness, anomalies, entropy assessment. |
| validate_secret | Test if a secret is actually valid with its target service (e.g., OpenAI, Stripe, GitHub). Uses provider auto-detection based on key prefixes, or accepts an explicit provider name. Never logs the secret value. |
| list_providers | List all available validation providers for secret liveness testing. |
| register_hook | Register a webhook/callback that fires when a secret is updated, deleted, or rotated. Supports shell commands, HTTP webhooks, and process signals. |
| list_hooks | List all registered secret change hooks with their match criteria, type, and status. |
| remove_hook | Remove a registered hook by ID. |
| status_dashboard | Launch the quantum status dashboard — a local web page showing live health, decay timers, superposition states, entanglement graph, tunnels, audit log, and anomaly alerts. Returns the URL to open in a browser. |
| agent_scan | Run an autonomous agent health scan: checks decay, staleness, anomalies, and optionally auto-rotates expired secrets. Returns a structured report. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
Latest Blog Posts
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/I4cTime/quantum_ring'
If you have feedback or need assistance with the MCP directory API, please join our Discord server