Skip to main content
Glama
mikeysrecipes

eSignatures MCP Server

by mikeysrecipes
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to eSignatures MCP Server

No user-submitted related servers found.

    Related Servers

    • MCP Server for eSignatures.

      esignaturescom
      A
      license
      B
      quality
      B
      maintenance
      eSignatures.com MCP: full control of contract content from your AI. Read and rewrite contracts and templates as Markdown, before and after sending. Send for signature, manage signers, create public signing links and track status. Hosted with OAuth, no install. Pay-per-use, no subscription.
      13
      163 PyPI
      40
      MIT

    • 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

    • 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
      42 npm
      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
    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

    A3.6/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct resource-action combination: contracts, templates, or template collaborators. Contract lifecycle tools are clearly separated from template tools, and collaborator tools are unambiguous.

    Naming Consistency5/5

    Tool names consistently follow a verb_noun pattern (create_contract, query_template, delete_contract). Minor variants like list_recent_contracts and add_template_collaborator still fit the overall convention cleanly.

    Tool Count5/5

    13 tools is well-scoped for an e-signature server covering contracts, templates, and template collaboration. Each tool has a clear purpose without excessive overlap or bloat.

    Completeness4/5

    The server covers contract creation, retrieval, listing, deletion, and withdrawal, plus full template CRUD and collaborator management. Minor gaps exist, such as no explicit update/send contract endpoint or resend/remind capability, but core workflows are supported.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources