Skip to main content
Glama
SignaTrustDev

SignaTrust MCP Server

Official
by SignaTrustDev
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to SignaTrust MCP Server

No user-submitted related servers found.

    Related Servers

    • DottedSign MCP by DottedSign-Official

      DottedSign MCPofficial

      DottedSign-Official
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.
      142
      -
    • kysigned-mcp by kychee-com

      kysigned-mcpofficial

      kychee-com
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables management of e-signature envelopes — create, check status, list, send reminders, and void — through natural language.
      62 npm
      37
      Apache 2.0

    • addsign-mcp

      rmindgh
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to send documents for e-signature, track signing status, remind pending signers, and download signed PDFs with audit-trail hashes via the AddSign API.
      6
      42 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 8 tools

    Disambiguation5/5

    Each tool targets a distinct action and resource: envelope CRUD (list, get, create, void), document upload, template listing, AI analysis, and blockchain verification. There is no overlap or ambiguity in tool purposes, making misselection unlikely.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern using lowercase with underscores, such as list_envelopes, create_envelope, upload_document, and verify_blockchain. The naming convention is uniform and predictable across the entire set.

    Tool Count5/5

    Eight tools cover the core envelope lifecycle and supporting features without bloat. The count is well-scoped for a document signing server, with each tool serving a clear and necessary function.

    Completeness4/5

    The tool set covers the primary workflow: upload documents, create/list/get envelopes, void in-progress envelopes, analyze completed ones, and verify blockchain anchors. Minor gaps like an in-MCP update or delete tool are absent, but those are secondary and can be handled via dashboard or API as noted.

    Maintenance

    ActivityInactive
    ResponsivenessUnresponsive

    Resources