keyhalve_status — KeyHalve - verify sealed documents MCP Tool
keyhalve_status
(keyhalve status) is one of 3 tools on the
KeyHalve - verify sealed documents
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call keyhalve_status from your client
- Claude Code KeyHalve - verify sealed documents keyhalve_status run in your project directory
- Claude Desktop KeyHalve - verify sealed documents keyhalve_status ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor KeyHalve - verify sealed documents keyhalve_status ~/.cursor/mcp.json
- VS Code KeyHalve - verify sealed documents keyhalve_status .vscode/mcp.json
- Zed KeyHalve - verify sealed documents keyhalve_status ~/.config/zed/settings.json
- Windsurf KeyHalve - verify sealed documents keyhalve_status ~/.codeium/windsurf/mcp_config.json
- Cline KeyHalve - verify sealed documents keyhalve_status ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI KeyHalve - verify sealed documents keyhalve_status ~/.gemini/settings.json
- Grok KeyHalve - verify sealed documents keyhalve_status .mcp.json (in your project root)
- ChatGPT KeyHalve - verify sealed documents keyhalve_status Settings → Connectors → Advanced → Developer mode
- Claude.ai KeyHalve - verify sealed documents keyhalve_status Settings → Connectors → Add custom connector
- LangChain KeyHalve - verify sealed documents keyhalve_status pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http verify https://mcp.keyhalve.com/mcpOther tools on this server
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.