oneguard-mcp
OfficialRelated Servers
Alternatives to oneguard-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables 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
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to list entries and metadata, run commands with secrets injected as environment variables while scrubbing every value from the output, copy secrets straight to the clipboard, and generate or store new secrets without their plaintext ever entering the conversation. Obvious dumpers are refused and destructive edits require explicit confirmation, closing off accidental exposure paths.MIT
- AlicenseNot gradedqualityDmaintenanceProvides AI coding agents with direct access to secrets management (get, set, list, delete secrets, and list environments) through the Model Context Protocol, enabling secure secret operations during development.13 npmMIT
- AlicenseNot gradedqualityCmaintenanceEnables AI coding agents to securely inject API keys and secrets into environment files, configs, or commands without the agent ever seeing the secret values.13 npmMIT
- AlicenseAqualityBmaintenanceEnables AI agents to make authenticated API calls and run commands with secrets injected, while keeping credentials completely hidden from the model, with policy enforcement, grants, and audit logging.6MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to securely use secrets from an Obsidian vault by injecting them into command environments without exposing the values, with auditing and approval controls.45 npmMIT
TDQS
Scored across 21 tools
Each tool targets a distinct resource+action, and descriptions explicitly cross-reference near-neighbors (e.g. oneguard_generate vs oneguard_secrets_generate, secrets_edit vs secrets_generate, env_sync vs env_push vs env_unlink). Boundaries between session tools (init vs status) and vault/secret operations are also spelled out, so misselection is unlikely.
The dominant pattern is oneguard_<domain>_<verb> in consistent snake_case (oneguard_vault_list, oneguard_secrets_generate, oneguard_env_sync). Only oneguard_init, oneguard_status, and oneguard_generate omit the domain segment, a minor but noticeable deviation.
At 21 tools the set sits at the heavy end of the comfortable range, but the domain (vaults, secrets, teams, env linking, audit logs, session) genuinely spans that many operations. Each tool maps to a real workflow step rather than padding.
Core lifecycle coverage is strong: vault create/list/rename, full secret CRUD plus archive and generate, env sync/push/status/unlink, and team management. Gaps remain — no vault delete and, more importantly, no way to unarchive a secret once archived, creating a dead end for that state.