qring vs LeakRank Guard
qring is no longer listed on any marketplace we read: these are its last known data, as of 2026‑10‑19.
qring is a plugin bundle for AI coding tools published by I4cTime. No marketplace we read lists it any more. LeakRank Guard is an MCP server published by ProtoTeemo. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-19. A plugin in this pair is no longer listed on any marketplace we read, so search engines are asked not to index the page.
Where each is published
| Marketplace | ||
|---|---|---|
| Community marketplace i4ctime/q-ring | Removed on 2026-10-19 Version: 0.18.0 Forks (GitHub): 1 Stars (GitHub): 4 Not marked · First seen |
Not listed |
| Official MCP Registry | Not listed | Listed Version: 0.2.3 Downloads/month (npm): 198 Downloads/week (npm): 43 Not marked · First seen |
Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.
The facts side by side
| Fact | qringno longer listed · | LeakRank Guard |
|---|---|---|
| Marketplaces that list it (differs) | 0 | 1 |
| Stars (GitHub) (differs) | 4 | No figure on GitHub |
| Forks (GitHub) (differs) | 1 | No figure on GitHub |
| Last release | Not published | Not published |
| Where it runs (differs) | Installs as a plugin bundle | On your machine (leakrank-guard) |
| Transport (differs) | Not stated | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 1 |
| Hooks it runs (differs) | 3 | Not published |
| Parts of the bundle (differs) | 20 | Not a bundle |
| Licence (differs) | AGPL-3.0 | Not stated |
| Repository (differs) | github.com/i4ctime/q-ring | Not stated |
| Changes in the last 7 days (differs) | 4 | 0 |
| First seen (differs) | 2026-10-13 | 2026-10-11 |
Lines where the two differ have a tinted background and bold values. No value is marked better or worse: a plugin no marketplace lists any more is shown with its last known data, which we do not rank against current figures.
What to use instead of qring
Plugins still listed whose own names, descriptions, tools and skills are closest in meaning to it. Comparable, not endorsed.
-
Encrypted local vault for API keys. Your AI fetches keys on demand and scans code for leaks.
-
secretcarousel io.github.jyswee/secretcarousel
Agent-first secrets vault. Store, rotate, and share credentials from chat. 20 tools.
-
Frictionless security, compliance, and threat detection for Claude Code and Co-Work. Advanced Behavioral detection patterns catch credential exfiltration, reverse shells, prompt…
-
securecode io.github.juanisidoro/securecode
Secrets vault for Claude Code with audit logs, access rules, and AES-256 encryption.
-
Local-first secret scanning, rotation, vault, and audit-log tools for AI agents.
-
envcp dev.fentz.envcp/envcp
Encrypted environment variable vault with AI access policies, keeping secrets safe from AI agents.
What each says it does
qring
OS keychain secrets for AI coding agents, over MCP — manage secrets, scan for leaks, rotate keys, and enforce policy directly from Claude Code.
LeakRank Guard
Scans code changes for leaked secrets and insecure config, with actionable fixes for AI agents.
How to run each
qring
No data for an automatic command: what its marketplaces declare does not say unambiguously how to connect it.
LeakRank Guard As a local MCP server: npm package
claude mcp add --env "LEAKRANK_API_KEY=<YOUR_LEAKRANK_API_KEY>" --transport stdio leakrank-guard -- npx -y leakrank-guard mcpRequires: LEAKRANK_API_KEY (secret)
Commands built only from what the marketplaces declare; the full set for every client is on each card.
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of qring publish no settings it asks for, so we do not compare settings.
What it can do: qring · What it can do: LeakRank Guard · Compare two other plugins
Data comes from public marketplace files in GitHub repositories of their authors. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.