KeyHalve MCP server

• Registry namecom.keyhalve/verifyverified in the MCP registry

The registry name sits under keyhalve.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-24
• Tools3
• Server calls itselfkeyhalve-verify
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-24 the server answered initialize and tools/list without a sign-in. First answer in 80 ms.

• Its tools do none of the product's use cases we checked: enforce security headers at the CloudFront edge; block framing and inline scripts on verifier pages; keep HSTS headers from being dropped by meta tags.
• Checked on 3 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 3 so far
• What an agent can do with it0 of 3 use cases
• Use14 npm downloads a week
• Answeredmeasuring3 of the 7 daily checks it takes to print a share
• Median first answer77 ms
• Space in an agent's context≈ 416 tokensthe definitions of all its tools (3), which an agent carries on every turn
• Tool definitionsA · 100 of 100
• Typed results0 of 3 toolsdeclared outputSchema: results come typed, read once

• Every tool passes all six checks.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• 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)…

• 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_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.