Skip to main content
Glama
signdocsbrasil

SignDocs Brasil MCP Server

Official
by signdocsbrasil
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to SignDocs Brasil MCP Server

No user-submitted related servers found.

    Related Servers

    • SignaTrust MCP Server by SignaTrustDev

      SignaTrust MCP Serverofficial

      SignaTrustDev
      A
      license
      A
      quality
      C
      maintenance
      Enables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.
      8
      23 npm
      1
      MIT

    • 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
      15 npm
      MIT

    • BoldSign MCP Server

      Synctest-hub
      A
      license
      A
      quality
      D
      maintenance
      Enables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.
      14
      31 npm
      MIT

    • zyta-sign-mcp

      blanck1945
      A
      license
      C
      quality
      D
      maintenance
      Enables AI agents to manage Zyta Sign documents, signatures, and studies with secure authentication and permission-respecting operations.
      49
      5 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/5.0

    Scored across 24 tools

    Disambiguation4/5

    Most tools have distinct purposes, but there is potential confusion between create_signing_session (single-signer express) and add_session_to_envelope (adds to envelope). Descriptions are clear enough to differentiate.

    Naming Consistency5/5

    All tools follow a consistent verb_noun pattern (e.g., create_envelope, list_transactions, cancel_signing_session). No mixed conventions or inconsistent styles.

    Tool Count4/5

    24 tools is on the higher side but justified for a comprehensive electronic signature service covering envelopes, sessions, transactions, documents, webhooks, and verification. Each tool addresses a specific need.

    Completeness4/5

    The surface covers most lifecycle operations: create, read, cancel, list for envelopes and sessions; upload/download documents; webhook management; verification. Minor gaps like updating envelope details or removing a session are not critical.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources