All servers · Utilities
KeyHalve - verify sealed documents
com.keyhalve/verify · v1.0.1
Measured by MCP Station
| Last check | Reachable |
|---|---|
| Checked at | — |
| Check success 7 / 30 days | — |
| First-try success 30 days | — |
| Median response | — |
| Lookups 30 days | — |
| Authentication | No auth |
| MCP version | 2025-06-18 |
| Rank score | — |
| Declared risk | Read-only (all tools declare readOnlyHint) |
| Capabilities declared | tools |
| Tool definitions | 3 tools · with description 100% · input schema is an object 100% · read/destructive hints 100% |
Description written by the publisher, not verified
Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.
Connect
streamable-http · https://mcp.keyhalve.com/mcp
claude mcp add --transport http verify https://mcp.keyhalve.com/mcp{
"mcpServers": {
"verify": {
"url": "https://mcp.keyhalve.com/mcp"
}
}
}Tools as reported by the server
keyhalve_verifyVerify 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 rkeyhalve_statusLive 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?"keyhalve_explainPlain-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.
Repository · JSON · Text for agents · Registry updated 2026-08-03