Skip to main content
Glama
zeroai-tech

handshake-mcp

by zeroai-tech

Related Servers

Alternatives to handshake-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      A
      maintenance
      Provides 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
    • F
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to search, create, and update password vault entries, manage folders and sharing permissions, while delivering secrets to a configured server-side handler.
      1
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables Claude Code to use locally encrypted, multi-tenant credentials by running commands with injected secrets, writing .env files, materializing files, and making HTTP requests, while scrubbing values from all output so they never enter the chat. Also supports sealed retrieval and saving through native dialogs or an auto-clearing clipboard, role-based credential selection, versioning, rollback, archiving, and a full audit log.
      7 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Encrypted credential vault with a 21-tool MCP server. Store and manage LLM API keys, service API keys, and OAuth credentials — then let your AI agent list, reveal, rotate, rename, pause, and proxy calls through them.
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Agent Vault is a local credential vault for AI agents. It enables agents to use secrets by name without ever seeing their values, with host allowlists, output scrubbing, and audit logging.
      4
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to securely manage local credentials, obtain short-lived tokens for authenticated API access, and audit every use by purpose.
      9
      MIT

    TDQS

    A3.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    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.

    Naming Consistency4/5

    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.

    Tool Count5/5

    Five tools is a well-scoped set for a credential vault with auditing. Each tool serves an essential function without redundancy or bloat.

    Completeness3/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues