KeyHalve — Claude Code MCP server for document checks
Checks KeyHalve-sealed documents for status, ciphertext integrity and rail attestation. Use it to verify a document while keeping its contents in the holder’s browser.
claude mcp add --transport http verify https://mcp.keyhalve.com/mcpWhat KeyHalve - verify sealed documents does
The server exposes keyhalve_verify, keyhalve_status and keyhalve_explain. Checks cover the document’s status with its issuing platform, a SHA-256 comparison for the ciphertext, the rail signature and the validity window. A failed check makes the overall verdict FAILED — DO NOT TRUST.
No login is needed, and the server does not receive decryption keys. It removes the URL fragment before processing; the sealed contents are read only in the holder’s browser. Connect over HTTP at https://mcp.keyhalve.com/mcp. The document must be sealed by KeyHalve. An unreachable rail or malformed input results in a failed verification, not a passing verdict.
What it helps with
- check whether a document remains active or was revoked
- compare served ciphertext with its issuance commitment
- verify the platform’s rail attestation
- check whether a document falls within its validity window
Example prompts for the agent
- Verify this KeyHalve document and explain the result.
- Check the document status and report any revocation reason.
- Verify the attestation and ciphertext integrity for this sealed document.
How to install KeyHalve - verify sealed documents
1Platform CLI: remote server
claude mcp add --transport http verify https://mcp.keyhalve.com/mcp2Platform CLI
claude mcp add keyhalve-verify-sealed-documents -- npx -y @keyhalve/verify-mcp1Platform CLI: remote server
codex mcp add keyhalve-verify-sealed-documents --url https://mcp.keyhalve.com/mcp2Platform CLI
codex mcp add keyhalve-verify-sealed-documents -- npx -y @keyhalve/verify-mcpConfig file
{
"mcpServers": {
"keyhalve-verify-sealed-documents": {
"url": "https://mcp.keyhalve.com/mcp"
}
}
}{
"mcpServers": {
"keyhalve-verify-sealed-documents": {
"command": "npx",
"args": [
"-y",
"@keyhalve/verify-mcp"
]
}
}
}Config file
{
"servers": {
"keyhalve-verify-sealed-documents": {
"type": "http",
"url": "https://mcp.keyhalve.com/mcp"
}
}
}{
"servers": {
"keyhalve-verify-sealed-documents": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@keyhalve/verify-mcp"
]
}
}
}1Platform CLI: remote server
gemini mcp add -t http keyhalve-verify-sealed-documents https://mcp.keyhalve.com/mcp2Platform CLI
gemini mcp add keyhalve-verify-sealed-documents npx -y @keyhalve/verify-mcpStep by step, with commands for each platform: How to add an MCP server to Claude Code, Codex, Cursor, VS Code, Gemini CLI and more
Questions about KeyHalve - verify sealed documents
How do I install KeyHalve in Claude Code?
Run claude mcp add --transport http verify https://mcp.keyhalve.com/mcp. This registers the HTTP server as verify.
What does KeyHalve — verify sealed documents do?
It checks the status and ciphertext integrity of KeyHalve-sealed documents, along with their attestation and validity window. It does not decrypt their contents.
Does the MCP server receive the key from a document URL?
No. It strips the URL fragment before processing and checks only facts that can be verified without the key.
