SignNow MCP Serverofficial
A
licenseA
qualityF
maintenancehttps://github.com/signnow/sn-mcp-server
MCP server for SignNow e-signature: templates, invites, embedded signing/editor, status & downloads.
25
8
MIT
digisign-mcp
by davidsimoes
Related Servers
Alternatives to digisign-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceMCP server for the Dropbox Sign API supporting signature requests, templates, teams, accounts, events, documents, signers, reports, bulk operations, and workflows.MIT
- AlicenseNot gradedqualityAmaintenanceMCP server that exposes GroupDocs.Signature as AI-callable tools for signing, verifying, and searching signatures in documents, enabling natural language interaction with document signature operations.MIT
- AlicenseCqualityDmaintenanceMCP server for the EZD PUW electronic document management system of Polish public administration, providing 91 tools covering the full API for documents, cases, correspondence, ePUAP, eDelivery, blockchain, and more.91MIT
- AlicenseNot gradedqualityBmaintenanceMCP server for accessing Czech datové schránky (ISDS) with legal semantics. Enables AI agents to safely read, send, and archive messages while respecting delivery triggers and deadlines.1MIT
- FlicenseAqualityCmaintenanceMCP server for creating, listing, and signing Turkish e-invoices, e-producer receipts, and e-self-employment receipts on the GİB e-Arşiv portal.24-
TDQS
A3.7/5.0
Scored across 15 tools
Disambiguation5/5
Every tool has a clearly distinct purpose with no ambiguity. For example, 'add_recipient' and 'list_recipients' are complementary but non-overlapping, while 'delete_envelope' and 'discard_envelope' are explicitly differentiated by permissions and state handling. The descriptions clearly delineate each tool's specific function within the envelope lifecycle.
Naming Consistency5/5
All tools follow a consistent verb_noun naming pattern throughout, such as 'create_envelope', 'list_envelopes', and 'upload_and_attach_document'. The naming is uniform, predictable, and enhances readability, making it easy for agents to understand and select the appropriate tool for each operation.
Tool Count5/5
With 15 tools, the server is well-scoped for digital signature management, covering the full envelope lifecycle from creation to completion. Each tool earns its place by addressing specific needs like recipient management, document handling, and status tracking, without being overly sparse or bloated.
Completeness5/5
The tool set provides complete CRUD/lifecycle coverage for the digital signature domain. It includes envelope creation, management (send, cancel, delete/discard), recipient and document handling, status retrieval, and download capabilities, with no obvious gaps that would cause agent failures in typical workflows.
Maintenance
ActivityInactive
ResponsivenessNo issues