PenlyDoc MCP server
Related Servers
Alternatives to PenlyDoc MCP server
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityCmaintenanceEnables 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.1MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to create branded documents from templates and data, send them for acceptance or signature, and track their status and recipients.MIT
- 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
- AlicenseNot gradedqualityCmaintenanceEnables 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
- AlicenseAqualityDmaintenanceEnables AI assistants to manage document signing workflows via natural language, including creating envelopes, uploading documents, analyzing contracts, and verifying blockchain anchors.843 npm1MIT
- FlicenseNot gradedqualityCmaintenanceEnables AI assistants to manage eSignature workflows, including creating signing tasks, tracking document status, and managing templates via natural language.142-
TDQS
Scored across 13 tools
Most tools have clearly distinct resource/action targets, and the descriptions clarify the main overlapping area: creating documents from templates versus uploading local files. The send_* family (send_from_template, send_document, send_draft, send_reminder) is the only place where an agent might briefly pause, but each has a specific purpose.
All tool names use consistent snake_case and follow a predictable verb_noun pattern, such as get_organisation, list_documents, cancel_document, and verify_pdf. The minor variation in send_from_template is still readable and fits the same convention.
With 13 tools, the server stays within a well-scoped range for an e-signature document workflow. Each tool covers a meaningful step: organisation lookup, templates, sending, status tracking, reminders, cancellation, signing links, and PDF verification.
The surface covers the core document lifecycle from template/upload through sending, status checks, history, reminders, cancellation, signed PDF download, and verification. Minor gaps exist around template management beyond listing and document metadata updates, but the main workflow is well covered.