Skip to main content
Glama
rmindgh

addsign-mcp

by rmindgh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to addsign-mcp

No user-submitted related servers found.

    Related Servers

    • online.econtract/mcp

      contractlayer
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and developers to create, send, and follow up on contracts for e-signature, manage signers and templates, retrieve signed PDFs and audit trails, and verify PDF signatures. It keeps signing and declining in the hands of each signer through personal links.
      1
      MIT

    • Sign Harness MCP Server

      reina20xx
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to create e-signature contracts, issue signing URLs, check pending signature statuses, and verify document SHA-256 hashes and signature seals through natural language.
      MIT
    • SignaTrust MCP Server by SignaTrustDev

      SignaTrust MCP Serverofficial

      SignaTrustDev
      A
      license
      A
      quality
      D
      maintenance
      Enables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.
      8
      22 npm
      1
      MIT
    • Formify MCP by formify-e-sign

      Formify MCPofficial

      formify-e-sign
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.
      5
      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/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct action: checking status, downloading signed documents, listing documents, listing templates, sending reminders, and sending for signature. No overlap in purpose.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with underscores, e.g., check_status, download_signed, list_documents. Even 'remind' is a verb alone but fits the pattern of single-action tools.

    Tool Count5/5

    With 6 tools, the set is well-scoped for a document signing server. It covers listing, sending, and managing documents without being overly sparse or bloated.

    Completeness4/5

    The tool set covers the core workflow: list templates, send for signature, check status, remind, and download. Minor gaps exist, such as no tool to create templates or void documents (must be done via dashboard), but these are acceptable for the focused scope.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources