mcpbeat

KeyHalve - verify sealed documents MCP Server

com.keyhalve/verify
answering

KeyHalve - verify sealed documents is answering right now. Last checked 15 min ago. 78 installs a week from npm. It exposes 3 tools. Last commit 3 Aug 2026.

Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.

Installs per day peak 78 · avg 2
a month agotoday
Uptime history 41 hours of history
41 hours agonow
100.0%
Uptime 24h
91 of 91 checks
3
Tools
read from the server
61 ms
Response time
average over 24h
78
Installs / week
npm and PyPI

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 15 min ago.

run in your terminal
claude mcp add verify --transport http https://mcp.keyhalve.com/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "verify": {
      "url": "https://mcp.keyhalve.com/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.verify]
url = "https://mcp.keyhalve.com/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://mcp.keyhalve.com/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "verify": {
      "url": "https://mcp.keyhalve.com/mcp"
    }
  }
}

Available tools 3

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

keyhalve
keyhalve_explain
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.
keyhalve_status
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?"
keyhalve_verify
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.

Endpoints

URLTransportStateLatencyChecked
https://mcp.keyhalve.com/mcp streamable-http answering 58 ms 15 min ago

KeyHalve - verify sealed documents — questions

Answers built from our own checks of this server.

What can KeyHalve - verify sealed documents do?
It exposes 3 tools, read directly from the server on our last check. Among them: keyhalve_explain, keyhalve_status, keyhalve_verify. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is KeyHalve - verify sealed documents working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 61 ms. The bar chart above shows every period we have measured.
How do I connect KeyHalve - verify sealed documents?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does KeyHalve - verify sealed documents need an API key?
No. KeyHalve - verify sealed documents completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 3 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is KeyHalve - verify sealed documents?
It answers our handshake in 61 ms on average, which is faster than 96% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.
How many people use KeyHalve - verify sealed documents?
The npm package @keyhalve/verify-mcp was installed 78 times in the last week. We show installs rather than GitHub stars on purpose: a star is a bookmark, an install is someone actually running it.
Is KeyHalve - verify sealed documents open source?
Yes — written in TypeScript and 0 stars on GitHub. The source link is on this page, so you can read exactly what it does with your data before you connect it.