A
licenseA
qualityB
maintenanceExposes the SumoSign signing API to AI agents, allowing document upload, envelope creation, and tracking, with signing always done by human recipients.
15
11 npm
MIT
zyta-sign-mcp
by blanck1945
Related Servers
Alternatives to zyta-sign-mcp
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to create and manage electronic signature documents via the ZapSign API, including sending from PDF, DOCX, URL, or template, tracking status, managing signers, templates, webhooks, background checks, and account settings.MIT
- AlicenseAqualityBmaintenanceEnables AI clients to create and manage e-signature sessions, envelopes, documents, and webhooks through the SignDocs Brasil API.2488 npmMIT
- 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
- AlicenseBqualityAmaintenanceEnables AI agents to interact with EAD Enterprise Suite for managing signatures, evidence, notifications, and dossiers.5292 npmMIT
- AlicenseAqualityDmaintenanceEnables 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.630 npmMIT
TDQS
C2.4/5.0
Scored across 49 tools
Disambiguation2/5
Several tools lack descriptions (e.g., kairo_create_sequential_sign, kairo_create_template, kairo_list_webhooks), making them indistinguishable. Tools like kairo_request_external_sign and kairo_get_sign_url overlap in purpose. With 49 tools, confusion is high.
Naming Consistency5/5
All tools follow the consistent pattern 'kairo_verb_noun' (e.g., kairo_add_studio_member, kairo_upload_document). No mixing of conventions; naming is uniform and predictable.
Tool Count2/5
49 tools is excessive for a single MCP server. Many tools could be consolidated (e.g., kairo_upload_document vs kairo_upload_documents). The scope seems overly broad, exceeding typical well-scoped server sizes.
Completeness4/5
The server covers CRUD for documents, studios, presets, webhooks, and signing workflows. Minor gaps exist due to missing tool descriptions (e.g., kairo_signature_anchor, kairo_create_template), but the overall lifecycle appears mostly covered.
Maintenance
ActivityInactive
ResponsivenessNo issues