io.github.pmaxx2023/handoff-kit
Related Servers
Alternatives to io.github.pmaxx2023/handoff-kit
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.1194 npmApache 2.0

evermint-mcpofficial
AlicenseNot gradedqualityDmaintenanceTamper-evident receipts for AI agent actions. The notary layer for agent-to-agent transactions.40 npm1MIT- AlicenseBqualityDmaintenanceVerifiable agent-to-agent task handoff with signed provenance chain.557 PyPIMIT
- FlicenseNot gradedqualityCmaintenanceEnables AI agents to keep append-only, hash-chained audit ledgers of their work — starting a ledger, appending steps, verifying each link and reporting the first broken line, and replaying entries in order — so users can confirm what an agent claims it did was never edited. Also replays game recordings through versioned deterministic kernels and reports whether their chain head is reproduced, not reproduced, or broken.67 npm-
- AlicenseAqualityBmaintenanceAppend-only evidence receipts for AI records: seal, verify, cite, chain-check, anchor status. A seal proves a record existed at a time, not that its contents are true. Five tools over stdio with npx -y apex-psi-mcp — no account, no key, verification free forever.569 npm1MIT
- FlicenseNot gradedqualityBmaintenanceEnables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.-
TDQS
Scored across 3 tools
The three verbs—create, validate, merge—map to mostly distinct operations on handoff records. There is slight overlap because create and merge both produce sealed records, and validate also issues a fresh receipt, but the primary actions remain clear.
All tools follow the same snake_case verb_handoff pattern: create_handoff, validate_handoff, merge_handoff. The noun and imperative verb style are fully consistent.
Three tools are well-scoped for a narrow handoff-record workflow. Each tool covers a distinct stage—creation, validation, and merging—without redundant surface area.
The surface covers the core handoff lifecycle: create, validate, and merge with receipt handling. It lacks an explicit read/list/retrieval tool for existing handoffs, but the likely stateless design makes this a minor gap rather than a blocker.