A
licenseA
qualityB
maintenanceIntegrates the HEU Legal API to manage native HEU documents and PDFs, enabling creation, sharing for e-signature, prompting signers, and downloading PDFs through conversation with Claude.
18
85 PyPI
1
MIT
CanUSign MCP Server
by devin-lemcke
Related Servers
Alternatives to CanUSign MCP Server
No user-submitted related servers found.
Related Servers
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 gradedqualityBmaintenanceEnables AI assistants to create fillable PDF forms, send contracts for electronic signature, verify signer identity via BankID or ID scan, and track document status after sending.MIT
- AlicenseBqualityCmaintenanceFacilitates contract and template management for eSignatures, enabling users to create, send, update, and manage contracts and templates with customizable options through a user-friendly interface.1340MIT
- AlicenseAqualityDmaintenanceEnables managing electronic signatures and contracts through the eSignatures API, including creating, sending, and withdrawing contracts, as well as managing templates and collaborators.13MIT
- AlicenseAqualityCmaintenanceDocument signing for AI agents. Send markdown or PDF for two-party e-signing with a single tool call — handles PDF generation, email verification, and SHA-256 certified delivery.27 npmMIT
TDQS
A4/5.0
Scored across 6 tools
Disambiguation4/5
The tools are mostly distinct: create/update/list/get/delete cover contract lifecycle, and list_attachment_types is clearly a supporting lookup. Minor ambiguity exists between get_contract and list_contracts, but their descriptions (specific vs. list) make the boundary clear.
Naming Consistency5/5
All tool names follow a consistent verb_noun pattern: create_contract, update_contract, list_contracts, get_contract, delete_contract, list_attachment_types. The pattern is uniform and predictable.
Tool Count5/5
Six tools is well-scoped for a contract-signing server: full CRUD plus a supporting lookup for attachment types. Each tool earns its place without redundancy or bloat.
Completeness4/5
The contract lifecycle is well covered: create, update, list, get, delete, plus attachment-type lookup. A minor gap is the lack of a dedicated tool to view signing status/activity beyond what update_contract returns, but the core workflows are complete.
Maintenance
ActivityMaintained
ResponsivenessNo issues