KeyHalve - verify sealed documents is an MCP server published by com.keyhalve, hosted at mcp.keyhalve.com. When last checked on 2026-11-22 it was working: it answers and lists its tools. It declares 3 tools, including keyhalve_verify, keyhalve_status, keyhalve_explain.
Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.
Nothing else in the archive shares these values.
Verify a KeyHalve-sealed document. Accepts a verify URL, the raw text of a KeyHalve QR code, or a document id (vp_…, kh_…, cb_…). Returns the cryptographic verdict: whether the seal exists, its live status (active/revoked/expired), ciphertext integrity against the issuance commitment, the KeyHalve rail's independent attestation, the validity window, and the issuer's trust context. This tool NEVER decrypts sealed contents — any decryption key in the URL fragment is discarded unread; contents are only readable by opening the verify URL in a browser.
| Parameter | Type | Description |
|---|---|---|
| input * | string | A KeyHalve verify URL, QR-code text, or bare document id. |
{
"name": "keyhalve_verify",
"description": "Verify a KeyHalve-sealed document. Accepts a verify URL, the raw text of a KeyHalve QR code, or a document id (vp_…, kh_…, cb_…). Returns the cryptographic verdict: whether the seal exists, its live status (active/revoked/expired), ciphertext integrity against the issuance commitment, the KeyHalve rail's independent attestation, the validity window, and the issuer's trust context. This tool NEVER decrypts sealed contents — any decryption key in the URL fragment is discarded unread; contents are only readable by opening the verify URL in a browser.",
"inputSchema": {
"type": "object",
"required": [
"input"
],
"properties": {
"input": {
"type": "string",
"description": "A KeyHalve verify URL, QR-code text, or bare document id."
}
}
},
"annotations": {
"title": "Verify a sealed document",
"readOnlyHint": true,
"openWorldHint": true
}
}None yet. Changes appear after a server's second daily check.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Live status of a KeyHalve-sealed document by id: active, revoked (with reason/time), or outside its validity window. Lighter than keyhalve_verify — status only, no integrity or rail checks. Use for "is this still good right now?"
| Parameter | Type | Description |
|---|---|---|
| document_id * | string | The document id, e.g. vp_…, kh_…, cb_…. |
{
"name": "keyhalve_status",
"description": "Live status of a KeyHalve-sealed document by id: active, revoked (with reason/time), or outside its validity window. Lighter than keyhalve_verify — status only, no integrity or rail checks. Use for \"is this still good right now?\"",
"inputSchema": {
"type": "object",
"required": [
"document_id"
],
"properties": {
"document_id": {
"type": "string",
"description": "The document id, e.g. vp_…, kh_…, cb_…."
}
}
},
"annotations": {
"title": "Check live document status",
"readOnlyHint": true,
"openWorldHint": true
}
}Plain-language explanation of what a KeyHalve verification verdict means and why it can be trusted (blind rail, three-share custody, commitments, revocation). Optionally focused on one topic.
| Parameter | Type | Description |
|---|---|---|
| topic | string | Optional single topic; omit for the overview. |
{
"name": "keyhalve_explain",
"description": "Plain-language explanation of what a KeyHalve verification verdict means and why it can be trusted (blind rail, three-share custody, commitments, revocation). Optionally focused on one topic.",
"inputSchema": {
"type": "object",
"properties": {
"topic": {
"enum": [
"verdict",
"blindness",
"rail",
"revocation",
"integrity",
"issuer_trust",
"limits"
],
"type": "string",
"description": "Optional single topic; omit for the overview."
}
}
},
"annotations": {
"title": "Explain a KeyHalve verdict",
"readOnlyHint": true,
"openWorldHint": false
}
}Free, public verification of KeyHalve-sealed documents (from any platform on the rail: ValidPay, CheckBooks, …). Use keyhalve_verify with a verify URL or QR text. This server never receives decryption keys — sealed contents remain readable only in the holder's browser.
Names, descriptions and schemas were written by the server and are shown as data.