KeyHalve - verify sealed documents MCP server
com.keyhalve/verifykeyhalve.comstreamable-httpv1.0.1Scanned
Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.
3 tools: 1 change things and 2 only read.
- Reads private data · 1
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the KeyHalve - verify sealed documents MCP server can do
The KeyHalve - verify sealed documents MCP server is published by keyhalve.com, a domain the MCP Registry verified. It has 3 tools. It can create or change data (1 tool: keyhalve_verify), but cannot delete data. 2 tools only read.
1 tool reads private data (keyhalve_status); 2 tools bring in text other people can write (keyhalve_verify and keyhalve_status).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 10, 2026, version 1.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
3 tools
Changes things 1Claude Code: ask
keyhalve_verifyVerify a KeyHalve-sealed document.Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- title: Verify a sealed document
- readOnlyHint: true
- openWorldHint: true
Only reads 2Show 2 read-only tools
keyhalve_explainPlain-language explanation of what a KeyHalve verification verdict means and why it can be trusted (blind rail, three-share custody, commitments, revocation).No findings
Why it is in this group
- The name "keyhalve_explain" says "explain": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Explain a KeyHalve verdict
- readOnlyHint: true
- openWorldHint: false
keyhalve_statusLive status of a KeyHalve-sealed document by id: active, revoked (with reason/time), or outside its validity window.Reads private dataReads text others writeNo findings
Why it is in this group
- The name "keyhalve_status" says "status": a word for reading.
What it can reach
- private-dataThe description's first sentence says "document": it reads documents.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote 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?"
Annotations the server declares
- title: Check live document status
- readOnlyHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:41 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.keyhalve.com/mcp: tools/list returned 3 tools to an anonymous client, including keyhalve_verify (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http verify https://mcp.keyhalve.com/mcpclaude mcp add --transport http verify https://mcp.keyhalve.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__verify__keyhalve_status",
"mcp__verify__keyhalve_explain"
],
"ask": [
"mcp__verify__keyhalve_verify"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as verify. Review it before you use it.
Capability tags behind 2 rules
- mcp__verify__keyhalve_verify untrusted-input
- mcp__verify__keyhalve_status private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.keyhalve/verify/verify?hash=2d1c402637a20baa2af801bad1953ad9cbd8ba503832d73ac0e52bf91e01261e" | jq -e '.changed == false'Pinned hash 2d1c402637a2, from Nov 10, 2026, 19:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.keyhalve/verify/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.keyhalve/verify)Source: MCP Registry · repository. Synced Oct 21, 2026, 17:57 UTC.
KeyHalve - verify sealed documents MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the KeyHalve - verify sealed documents MCP server safe?
- No scan can promise that. What its definitions show: 3 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the KeyHalve - verify sealed documents MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the KeyHalve - verify sealed documents MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the KeyHalve - verify sealed documents MCP server have?
- 3 tools: 1 write, 2 read. keyhalve_verify, keyhalve_status and keyhalve_explain.
Does the KeyHalve - verify sealed documents MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the KeyHalve - verify sealed documents MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the KeyHalve - verify sealed documents MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 10, 2026.