KeyHalve — Verify Sealed Documents MCP Server

KeyHalve — Verify Sealed Documents MCP server exists for a simple reason — assistants are far more useful when they can act on KeyHalve — Verify Sealed Documents directly instead of describing what you should do. Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.

What you get

Free, public, no-account MCP server that lets any AI verify KeyHalve-sealed documents — from any platform on the rail (ValidPay, CheckBooks, …). Seal = the door (a platform's paid MCP). Verify = the room (this one, free forever).

Setting it up

Being a remote server, there is no local install. You register the endpoint with your client, authorise it once, and the tools appear.

What the assistant can call

Once KeyHalve — Verify Sealed Documents is connected, these are the calls the assistant has available:

• Endpoint — ** https://mcp.keyhalve.com/mcp (Streamable HTTP, stateless)
• Tools — ** keyhalve_verify · keyhalve_status · keyhalve_explain — all read-only, no auth
• Tenant — neutral.** Platforms come from the same manifest data as the web verifier
• llms-install.md — AI-agent install steps (Cline's AI-driven install; also the canonical per-client snippets)
• glama.json — Glama claim file (maintainers; their live schema is maintainers-only)
• Check — Meaning
• status — active / revoked (with reason) on the issuing platform

Configuration and credentials

You will need one environment variable: CLOUDFLARE_API_TOKEN. The server will not start without them, which is usually why the tools fail to appear on a first run. Keep credentials in your client's env block or a secrets manager rather than in a file you might commit.

Before you rely on it

• Your data travels to the provider's service, so the usual questions apply about what you send and what they retain.
• Missing credentials fail quietly in some clients — if no tools show up, check the environment block first.
• MCP clients confirm each tool call by default. Leave that on until you have watched what the keyhalve — verify sealed documents mcp server does with a few real requests.

Choosing this one

This sits in the developer tooling group, where several servers overlap in what they claim to do but differ sharply once you actually set them up. KeyHalve — Verify Sealed Documents's toolset — Endpoint, Tools, Tenant and 4 more — is a fair guide to whether it matches your workflow. It is maintained by com.keyhalve; worth a glance at recent repository activity before you build anything load-bearing on it.

This entry was verified against KeyHalve — Verify Sealed Documents's own documentation before publication; SyncDev keeps the directory reviewed rather than auto-generated.