Schema | handshake-mcp

handshake-mcp

Describes the environment variables required to run the server.

Name	Required	Description	Default
`HANDSHAKE_SESSION`	Yes	A session token printed by `handshake unlock`. Used by the MCP server to access the vault. Without this token, the MCP server cannot authenticate.

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{}

Functions exposed to the LLM to take actions

Name	Description
handshake_statusA	Is the vault open? Shows whether a session is live, how long is left, and how many secrets exist. Needs no token — call this first when a credential is needed.
handshake_listA	List the NAMES of stored credentials (never values). Requires an open session token.
handshake_getA	Read ONE credential by name. Requires an open session token. Every read is written to an append-only audit log with the reason given, so always pass a truthful reason.
handshake_putB	Store or update one credential. Requires an open session token.
handshake_logC	Recent access log — who read which credential, when, from where.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/zeroai-tech/handshake'

If you have feedback or need assistance with the MCP directory API, please join our Discord server