oneguard-mcp
OfficialRelated Servers
Alternatives to oneguard-mcp
No user-submitted related servers found.
Related Servers
- 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.8 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.5 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.26MIT
- AlicenseAqualityFmaintenanceA GitHub-native secrets manager that allows AI assistants to securely manage, generate, and validate credentials without exposing sensitive values in conversation history. It supports secret scanning, environment diffing, and secure command execution by injecting masked variables directly into the runtime environment.85 npm2MIT
- AlicenseCqualityCmaintenanceEnables AI agents to securely store and manage encrypted secrets locally while using them indirectly through environment-variable injection or file writes, so plaintext values never enter the agent's context.8MIT
- AlicenseNot gradedqualityAmaintenanceEnables AI agents to scan projects for leaked secrets and manage security incidents using GitGuardian's comprehensive API. It supports automated secret detection, honeytoken creation, and remediation workflows to secure codebases without context switching.37MIT
TDQS
Scored across 21 tools
Most tools target distinct resources and actions clearly, but two pairs could be confused: oneguard_status vs oneguard_env_status (session vs environment status) and oneguard_generate vs oneguard_secrets_generate (returned vs stored values). The detailed descriptions help, but the names alone are ambiguous.
The dominant pattern is oneguard_<resource>_<action> (vault_list, secrets_add, env_sync, teams_invite), which is consistent. A few tools break the pattern: oneguard_init, oneguard_status, and oneguard_generate lack a resource segment, making them minor deviations rather than chaotic inconsistencies.
21 tools is slightly above the ideal 3-15 range but still reasonable for a secrets management server covering vaults, secrets, environment sync, teams, and audit logs. Each tool has a distinct job, so the count feels justified rather than bloated.
Core lifecycle coverage is strong: vaults can be listed/added/renamed, secrets can be listed/added/edited/archived/deleted/generated, env links can be synced/pushed/unlinked, and teams can be managed. Minor gaps exist—there is no unarchive operation and no vault deletion—but agents can work around these in most workflows.