Skip to main content
Glama

Related Servers

Alternatives to gage

No user-submitted related servers found.

    Related Servers

    • A
      license
      C
      quality
      A
      maintenance
      Cryptographic identity and trust protocol for AI agents. 38 MCP tools across 8 protocol layers: Ed25519 identity, delegation chains, values compliance, signed communication, policy engine, task coordination, cross-layer integration, and agentic commerce. 264 tests passing.
      154
      342 npm
      4
      Apache 2.0
    • A
      license
      Not graded
      quality
      A
      maintenance
      MCP server enabling AI coding agents to seal work into cryptographically signed ProofPackets and verify them, catching forged completion claims and enforcing spec-bound acceptance criteria.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      MIT
    • A
      license
      A
      quality
      C
      maintenance
      WaxSeal MCP gives AI agents cryptographic identity — verify any WaxSeal fingerprint, check Ed25519 signatures, and gate irreversible actions with human-signed approval tokens before execution. It connects Claude Desktop, Cursor, and Windsurf to the WaxSeal trust network so agents can prove who authorized an action and reject tampered credentials in under a second.
      6
      8 npm
      2
      MIT

    TDQS

    A4/5.0

    Scored across 9 tools

    Disambiguation5/5

    Each tool targets a distinct step in the secure messaging workflow: identity, buddy listing, pairing (start/confirm), building a bundle, listing inbox, opening a bundle, pulling from relay, and pushing off-machine. Descriptions explicitly differentiate similar-sounding tools like gage_send vs gage_push and gage_inbox vs gage_open, leaving no ambiguity.

    Naming Consistency4/5

    All tools share a consistent 'gage_' prefix and snake_case formatting. The suffix varies between noun-based (identity, buddies, inbox) and verb-based (send, open, pull, push) forms, but this mix is predictable and readable within the domain.

    Tool Count5/5

    Nine tools neatly cover the core operations of a secure messaging system without redundancy. The count is well within the typical 3–15 range, and each tool serves a clear purpose.

    Completeness4/5

    The surface covers identity, contact management (add/list), message building, sending/receiving, and trust verification. Minor gaps exist, such as no tool for removing or updating a buddy, and no way to list sent bundles, but these are not critical for core workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues