Productivity · Remote MCP server
KeyHalve - verify sealed documents
Free, no-account verification of KeyHalve-sealed documents. Read-only; never receives keys.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
com.keyhalve/verify- Version
- 1.0.1
- Status
- Active
- Category
- productivity
- Transport
- Streamable HTTP, stdio (local process)
- Package
- npm
- Published
- 2026-08-03
- Updated
- 2026-08-03
- Publisher
- com.keyhalve
- Namespace
- Namespace verified by the MCP Registry via the domain keyhalve.com · how
- Repository
- github.com/keyhalve/keyhalve-mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.keyhalve.com/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Reachable
- Yes (HTTP 200)
- Handshake
- keyhalve-verify 1.0.0 · protocol 2025-06-18
- Tools discovered
- 3:
keyhalve_verify,keyhalve_status,keyhalve_explain - Checked on
- 2026-10-05
Packages
| Registry | Package | Version | Transport |
|---|---|---|---|
| npm | @keyhalve/verify-mcp | 0.1.0 | stdio |
How to connect KeyHalve - verify sealed documents
KeyHalve - verify sealed documents is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.keyhalve.com/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
It can also run locally from a Node.js package published to the npm registry: @keyhalve/verify-mcp version 0.1.0. It speaks MCP over stdio, so the client starts it as a program and talks to it through standard input and output. It needs Node.js; clients usually start it with npx - the usual command is npx -y @keyhalve/verify-mcp@0.1.0.
In the mcpServers JSON format that many desktop and editor MCP clients read, the entry looks like this (placeholders in angle brackets):
{
"mcpServers": {
"verify": {
"command": "npx",
"args": [
"-y",
"@keyhalve/verify-mcp@0.1.0"
]
}
}
}Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More productivity servers
| Server | Runs |
|---|---|
| Kenotex MCPLet your coding agent manage real todos, events, and check-in habits in Kenotex on your Mac. | Local · stdio |
| KenvaPersonal CRM for Claude. Contacts live as plain-text files in your own Google Drive. | Remote · HTTPLive check: ✗ no handshake |
| Kepler CRMSearch recruiting CRM records, manage candidates, jobs, pipelines, notes and tasks with OAuth. | Remote · HTTPLive check: sign-in required |
| Kesslerio Attio MCP ServerConnect AI to your Attio CRM. Manage contacts, companies, deals, and sales pipelines. Create tasks… | Remote · HTTPLive check: ✗ no handshake |
| KeyIDSignup sessions, browser continuity, email, SMS, and OTP/TOTP infrastructure for AI agents. | Remote & Local · HTTP, stdioLive check: sign-in required |
| KeywordiseAuto-apply to jobs: matches your CV, tailors a fresh CV per posting, and applies for you. | Remote · HTTPLive check: ✓ handshake |
| KGLD Reserve AttestationKGLD gold-token reserve proof: custody vs supply, auditor report hash, human verification by email. | Remote · HTTPLive check: ✓ handshake |
| KIAgentYour mail, chats and documents indexed into a local SQLite corpus, served to AI clients over MCP. | Remote · HTTP |