A
licenseA
qualityD
maintenanceEnables managing electronic signatures and contracts through the eSignatures API, including creating, sending, and withdrawing contracts, as well as managing templates and collaborators.
13
MIT
MCP Server for eSignatures
Related Servers
Alternatives to MCP Server for eSignatures
No user-submitted related servers found.
Related Servers
- AlicenseAqualityCmaintenanceEnables Claude to create and manage e-signature contracts, including generating PDFs, sending signing links, and checking contract status.60MIT
- FlicenseNot gradedqualityDmaintenanceEnables users to create, manage, and track electronic signing requests and templates through Claude Desktop and other MCP-compatible clients. Provides multi-tenant authentication with customer API keys for secure document workflow operations.66 npm-
Formify MCPofficial
AlicenseNot gradedqualityAmaintenanceEnables AI agents to create fillable PDFs, send contracts for e-signature, verify signers via BankID or ID scans, and track post-send document workflows.5MIT- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create branded documents from templates and data, send them for acceptance or signature, and track their status and recipients.MIT
- AlicenseAqualityDmaintenanceEnables interaction with the BoldSign e-signature platform through its API. Supports managing documents, templates, contacts, users, and teams for electronic signature workflows.1471 npmMIT
TDQS
B3.4/5.0
Scored across 13 tools
Disambiguation5/5
Each tool has a clearly distinct purpose targeting specific resources and actions, such as create_contract vs. withdraw_contract for contracts, and create_template vs. update_template for templates. There is no overlap or ambiguity in functionality, making tool selection straightforward for an agent.
Naming Consistency5/5
All tools follow a consistent verb_noun naming pattern, such as create_contract, delete_template, and list_recent_contracts. The naming is uniform throughout, with no deviations in style or convention, enhancing readability and predictability.
Tool Count5/5
With 13 tools, the server is well-scoped for eSignatures, covering core operations like contract and template management, collaboration, and querying. Each tool serves a distinct and necessary function without being excessive or insufficient for the domain.
Completeness4/5
The tool set provides comprehensive CRUD and lifecycle coverage for contracts and templates, including collaboration features. Minor gaps exist, such as no direct tool for updating contract details or handling signer-specific actions beyond querying, but agents can likely work around these with the available tools.
Maintenance
ActivityStale
ResponsivenessNo issues