handshake-mcp
Related Servers
Alternatives to handshake-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to resolve stored API tokens and credentials from a locally encrypted vault through an inject_secret tool, writing them to env-file handles the agent consumes outside the conversation so secret values never appear in chat transcripts. Provides listing and metadata access while requiring a human unlock gate before any decryption.MIT
- AlicenseNot gradedqualityBmaintenanceProvides a zero-knowledge credential vault for AI agents, allowing secure storage, retrieval, and management of secrets with cross-agent delegation and tamper-evident audit.MIT
- AlicenseAqualityBmaintenanceEnables AI agents to look up stored logins by URL, name, or alias and use them without seeing the secrets, injecting authentication into HTTP requests, running commands with credentials in the environment and scrubbed output, and fetching 2FA codes, subject to per-credential policies and user approval.23MIT
- AlicenseNot gradedqualityBmaintenanceEnables 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.68 PyPIMIT
- AlicenseNot gradedqualityAmaintenanceProvides AI agents with a secure, OpenBao-backed secrets vault supporting vault and secret management, per-vault SSH certificate authorities, just-in-time SSH access, and granular token policies. Enables agents to store, retrieve, and generate typed secrets and issue ephemeral SSH certificates with fail-close access control.Apache 2.0
- AlicenseBqualityCmaintenanceEnables AI agents to use vault-stored credentials without ever exposing plaintext secrets to model context, transcripts, or telemetry. It decrypts AES-256-GCM envelopes locally via WebCrypto, resolves opaque secret handles into subprocess environments and outbound HTTP requests, issues auto-zeroizing time-bounded leases, and scrubs echoed credentials from output.19MIT
TDQS
Scored across 5 tools
Each tool has a clearly distinct purpose: session status, listing names, reading a single credential, writing a credential, and viewing the audit log. There is no meaningful overlap or ambiguity between them.
All tools share the handshake_ prefix and use lowercase snake_case, which is predictable. However, status and log are nouns while list, get, and put are verbs, so the naming pattern is not perfectly uniform.
Five tools is a well-scoped set for a credential vault with auditing. Each tool serves an essential function without redundancy or bloat.
The set covers status checking, listing, reading, writing, and audit logging, which handles the core workflow. However, there is no delete/remove operation for credentials, which is a notable lifecycle gap for a secrets vault.