Skip to main content
Glama
Prismer-AI
by Prismer-AI

Related Servers

Alternatives to signet

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflow tools that runs on your infrastructure with Ed25519 signing, enabling autonomous agents to discover and invoke tools securely.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Local MCP server that signs and records agent actions into a tamper-evident log using Ed25519 keys for frictionless integration with Touchstone.
      33 npm
      Apache 2.0
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to construct SHA-256 Merkle trees and generate/verify inclusion proofs, validate JWT HMAC-SHA256 claims, run Schnorr zero-knowledge identification, and enforce constant-time secret comparison with nonce replay protection for tamper-evident state attestation. It runs as a zero-dependency, stdlib-only MCP stdio server for clients such as Claude Desktop, Cursor, and Windsurf.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.
      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
      F
      maintenance
      A thin MCP server that wraps provenance-receipts and quality-gate services as tools, enabling AI agents to certify content origin and score quality via Ed25519-signed receipts.
      5
      55 npm
      MIT

    TDQS

    A4.2/5.0

    Scored across 4 tools

    Disambiguation5/5

    Each tool performs a distinct cryptographic operation: hashing, key generation, signing, and verification. No overlap in purpose reduces ambiguity.

    Naming Consistency4/5

    Tools follow a 'signet_' prefix pattern. Most use verb_noun (generate_keypair, sign, verify), but 'content_hash' is noun_noun. Minor inconsistency but still clear.

    Tool Count5/5

    Four tools is well-scoped for a cryptographic signing server. Each tool is essential, covering the core workflow without bloat.

    Completeness5/5

    The tool set covers the full signing lifecycle: input representation (hash), key generation, signing, and verification. No obvious gaps for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessWithin a week