Skip to main content
Glama
io.github.pmaxx2023/handoff-kit

io.github.pmaxx2023/handoff-kit

by pmaxx2023

Related Servers

Alternatives to io.github.pmaxx2023/handoff-kit

No user-submitted related servers found.

    Related Servers

    • A
      license
      A
      quality
      C
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      94 npm
      Apache 2.0
    • F
      license
      Not graded
      quality
      C
      maintenance
      Enables 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
      -
    • A
      license
      A
      quality
      B
      maintenance
      Append-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.
      5
      69 npm
      1
      MIT
    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to validate deliverables (JSON, ZIP, PDF, DOCX) against signed contracts, generating verifiable receipts with Ed25519 signatures.
      -

    TDQS

    B3.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    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.

    Naming Consistency5/5

    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.

    Tool Count5/5

    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.

    Completeness4/5

    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.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues