agent-vault-mcp
Related Servers
Alternatives to agent-vault-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables secure delivery of Bitwarden Secrets Manager secrets to approved local files without exposing secret values to the MCP client or model. It provides metadata-only secret discovery and atomic file writes for single secrets or raw env files.MIT
- AlicenseBqualityBmaintenanceEnables self-hosted local file, terminal, document, and named-device tools for MCP clients, with an isolated document mode and a full-access mode.11MIT
- AlicenseNot gradedqualityBmaintenanceEnables self-hosted remote access to a user-controlled device's approved filesystem roots, allowing clients to list directories, read and search files, inspect metadata, ping the agent, and list devices through an MCP tunnel.AGPL 3.0
- AlicenseNot gradedqualityBmaintenanceEnables teams to securely store and retrieve credentials, view decrypted secrets or live OAuth tokens, and connect to third-party MCP servers through a unified MCP endpoint.MIT
- AlicenseNot gradedqualityAmaintenanceEnables agents to access remote and local MCP servers plus HTTP APIs through a single MCP endpoint, with per-consumer scoped tokens, tool-level permissions, and encrypted secret management.5PolyForm Noncommercial 1.0.0
- AlicenseNot gradedqualityBmaintenanceA local stdio MCP server that lets agents use temporary secrets through a private browser form and approved API requests without receiving secret values in tool output. Install the binary for your platform and run secrethandoff mcp; secrets remain in process memory until forgotten or the process exits.MIT
TDQS
Scored across 14 tools
Most tools target distinct resources and lifecycle steps (list vs find metadata, begin_enrollment vs result vs decline, prepare_request vs execute_operation). The main ambiguity is between vault_status and get_connection_status, and the trio vault_list / list_connections / list_operations could be momentarily confused since all are read-only metadata listings. Descriptions mostly disambiguate these, but the 'status' pair overlaps in spirit.
Names are broadly snake_case verb_noun, but split into two families: a vault_-prefixed group and a bare verb group (list_operations, prepare_request, execute_operation). Within the vault family the convention is also mixed, with verbs (vault_list, vault_find, vault_decline) alongside noun-style names (vault_status, vault_result). Readable, but not a single predictable pattern.
Fourteen tools sits comfortably in the sensible 3-15 range and each tool maps to a real step: target selection, enrollment lifecycle, metadata reads, and the operation ticket flow. It is slightly heavy given the enrollment flow spreads over three tools, but nothing feels redundant at scale.
The surface covers connection, discovery, enrollment, operation ticketing, execution, and credential export, but there are notable gaps: no way to update, rotate, revoke, or delete a stored credential or connection. An agent that enrolls a credential has no matching lifecycle tool to retire it, which could cause dead ends.