Skip to main content
Glama
I4cTime

q-ring

by I4cTime
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to q-ring

  • secrets-mcp

    sealca
    A
    license
    A
    quality
    C
    maintenance
    Provides Claude Code with access to personal secrets and notes stored in a local Markdown file. It enables users to list, search, retrieve, and update secret sections through natural language commands.
    5
    11 npm
    MIT

Related Servers

  • enigmagent-mcp

    Agnuxo1
    A
    license
    A
    quality
    B
    maintenance
    Local AES-256-GCM encrypted vault for AI agents. Resolve {{PLACEHOLDER}} secrets in prompts at runtime — LLMs never see real API keys. Argon2id key derivation, zero cloud.
    2
    61 npm
    3
    MIT

  • aarifmms/keyblind

    aarifmms
    A
    license
    A
    quality
    D
    maintenance
    Encrypted secrets vault that blinds AI agents to API keys. Stores secrets in AES-256-GCM encrypted SQLite vault, resolves them at runtime via MCP values never appear in LLM conversation transcripts. Sandbox .env files with deterministic fakes.
    7
    95 npm
    3
    MIT

  • envguard

    1nc0gn30
    A
    license
    Not graded
    quality
    B
    maintenance
    Enables AI agents to scan and audit environment files for leaked secrets, sanitize them, encrypt/decrypt vaults, and run processes with zero-disk secret injection.
    MIT

  • keyvault

    ylz201
    A
    license
    Not graded
    quality
    D
    maintenance
    Enables AI agents to securely manage API keys and secrets via the MCP protocol, with encrypted storage at rest and a simple CLI and Python SDK.
    1
    MIT
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

A4.2/5.0

Scored across 46 tools

Disambiguation3/5

Descriptions are detailed and cross-reference alternatives, but several tools occupy the same conceptual niche (export_secrets vs env_generate vs teleport_pack; health_check vs check_project vs agent_scan; validate_secret vs ci_validate_secrets). An agent has to read carefully to avoid picking the wrong one, so the set is not clearly distinct despite good documentation.

Naming Consistency4/5

All names use snake_case and most follow a verb-first pattern (set_secret, list_secrets, register_hook), with only minor deviations from the domain-prefixed groups (tunnel_create, agent_remember, teleport_pack) and a few noun-style names (health_check, status_dashboard). The pattern is predictable enough for an agent to navigate.

Tool Count2/5

46 tools is well past the 25+ threshold and feels bloated for an MCP surface. Many are near-duplicates in different modes (single vs batch, manifest vs scope-wide), which inflates the count without adding proportional capability.

Completeness5/5

The surface covers the full secret lifecycle—create, read, update, delete, rotate, validate, export, entangle, promote, audit with tamper verification, hooks, policies, scanning, and health reporting. There are no obvious dead ends for the declared domain.

Maintenance

ActivityActive
ResponsivenessNo issues

Resources