# PenlyDoc (npm · penlydoc-mcp) Send documents for e-signature, track who signed and save sealed PDFs with PenlyDoc. - Trust score: 67/100 (medium) - Change this week: +4 - Registry status: active - Liveness: live - Owner verified: no - Last scored: 2026-11-05 ## Components - npm · `penlydoc-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp.md), [page](https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp) ## Channel facts - Registry: `npm` - Package: `penlydoc-mcp` - Version: `0.1.1` - Transport: `stdio` ## Trust breakdown How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog) Scored 2026-11-05. - **Supply Chain Security**: 81/100 - No malware found by supply-chain analysis. - CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.1, a direct dependency. A fixed version is available. - No install/post-install scripts declared. - 30 of 93 dependencies flagged as unhealthy. - **Provenance & Transparency**: 45/100 - Source repository is publicly reachable at the declared URL. - Provenance check failed: no build-provenance attestation is published. - Clear OSI-approved license (MIT). - Actively maintained (last published 10 days ago). - Disclosure check failed: no security disclosure policy was found in the source repository. - **Schema Quality & AI Usability**: 67/100 - AI-judged instruction clarity (good). - Tool/resource definitions use about 992 tokens (~76/item across 13 items; 13 tools + 0 resources), lean. - Usage-examples check failed: none of the tools include examples. - **Stability & Change Management**: 37/100 - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses. - **Tool Coverage**: 75/100 - 100% of tools have a non-trivial description (not blank, and not just the tool's name). - 24% of tool parameters carry a description. - **Tool Safety**: 100/100 - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured. - All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation. - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it. - **Capabilities**: 100/100 - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28. ## Install ### How do I install the PenlyDoc MCP server? PenlyDoc runs locally as an npm package, launched with npx -y penlydoc-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation. ### Claude ```bash claude mcp add orestklymko-penlydoc-mcp -- npx -y penlydoc-mcp ``` ### Cursor ```json { "mcpServers": { "orestklymko-penlydoc-mcp": { "command": "npx", "args": [ "-y", "penlydoc-mcp" ] } } } ``` ### VS Code ```json { "servers": { "orestklymko-penlydoc-mcp": { "command": "npx", "args": [ "-y", "penlydoc-mcp" ] } } } ``` ### Codex ```bash codex mcp add orestklymko-penlydoc-mcp -- npx -y penlydoc-mcp ``` ### opencode ```json { "$schema": "https://opencode.ai/config.json", "mcp": { "orestklymko-penlydoc-mcp": { "type": "local", "command": [ "npx", "-y", "penlydoc-mcp" ], "enabled": true } } } ``` ### OpenClaw ```bash openclaw mcp add orestklymko-penlydoc-mcp --command npx --arg -y --arg penlydoc-mcp ``` ### Hermes ```yaml mcp_servers: orestklymko-penlydoc-mcp: command: "npx" args: ["-y", "penlydoc-mcp"] ``` ### Netclaw ```json { "McpServers": { "orestklymko-penlydoc-mcp": { "Transport": "stdio", "Command": "npx", "Arguments": [ "-y", "penlydoc-mcp" ] } } } ``` ### Vellum ```bash assistant mcp add orestklymko-penlydoc-mcp -t stdio -c npx -a -y penlydoc-mcp ``` ### Other ```json { "mcpServers": { "orestklymko-penlydoc-mcp": { "command": "npx", "args": [ "-y", "penlydoc-mcp" ] } } } ``` ## Changelog Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims. ### 2026-11-05 (score 67, +1) No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-03 (score 66, +1) No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-11-01 (score 65, +1) No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-30 (score 64, +1) No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-28 (score 63, +1) No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-26 (score 62, +1) No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes. ### 2026-10-25 (score 61) First indexed and scored. ## MCP tools (13) ### `get_organisation` (~29 tokens) Organisation Shows which PenlyDoc organisation the API key belongs to, its default language and its sending limit. ### `list_templates` (~48 tokens) List templates Lists the organisation's templates: id, name, the roles to fill (e.g. "tenant", "landlord"), the data keys to fill, and whether the template is ready to send. ### `send_from_template` (~210 tokens) Send from a template Creates a document from a template: one person per role, values for its data keys. With send=true PenlyDoc immediately e-mails the people with delivery EMAIL; confirm the people and values with the user first. With send=false it creates a draft the user can review in the console. Use the same externalRef/idempotencyKey to safely retry. Input parameters: - `data` (object): Values for the template data keys, e.g. {"Rent": "950 EUR"} - `externalRef` (string): Your own reference, e.g. an order or contract number - `idempotencyKey` (string) - `message` (string) - `roles` (object, required): Keyed by role key from list_templates, e.g. {"tenant": {"name": "Mia Novak", "email": "mia@example.com"}} - `send` (boolean, required): true = e-mail people now; false = draft - `templateId` (string, required) - `title` (string) ### `send_document` (~193 tokens) Send a document Uploads local files (PDF, or PNG/JPEG photos of pages, joined in order) and creates a document for signature. Signature boxes come from {{sig:1}}-style tags in the PDF or from the fields argument (points, top-left origin). With send=true PenlyDoc e-mails the people right away; confirm with the user first. Without tags or fields, use send=false and let the user place the boxes in the console (the result has a link). Input parameters: - `data` (object): Values for {{data:Key}} tags in the PDF - `expiresInDays` (integer) - `externalRef` (string) - `fields` (array) - `files` (array, required): Local file paths - `message` (string) - `recipients` (array, required) - `send` (boolean, required) - `signingOrder` (string) - `title` (string, required) ### `list_documents` (~53 tokens) List documents Lists documents sent for signature, newest first, with who has signed. Filter by status or by your externalRef. Input parameters: - `externalRef` (string) - `limit` (integer) - `status` (string) ### `get_document` (~39 tokens) Document status Full status of one document: each person, whether they opened, signed or declined (with the reason), and when. Input parameters: - `id` (string, required) ### `get_history` (~41 tokens) Document history The hash-chained history of a document: every step with time, who and IP address, and whether the chain is intact. Input parameters: - `id` (string, required) ### `send_draft` (~39 tokens) Send a draft Sends a DRAFT document: PenlyDoc e-mails the first people to sign. Confirm with the user first. Input parameters: - `id` (string, required) ### `send_reminder` (~37 tokens) Remind E-mails a reminder now to everyone whose turn it is on this document. Confirm with the user first. Input parameters: - `id` (string, required) ### `cancel_document` (~63 tokens) Cancel a document Cancels (voids) a document that is still being signed. Signing links stop working and the people still to act are told by e-mail. This cannot be undone; confirm with the user first. Input parameters: - `id` (string, required) - `reason` (string, required) ### `create_signing_link` (~77 tokens) Signing link for an embedded signer Creates a one-hour signing link for a person with delivery EMBEDDED, to open in your own app or hand to that person. The link lets whoever has it sign as that person: share it only with them. Input parameters: - `id` (string, required) - `recipientId` (string, required) - `returnUrl` (string) ### `download_signed_pdf` (~64 tokens) Download the signed PDF Saves the sealed, signed PDF (with the certificate of completion as last page) of a COMPLETED document to a local file. Input parameters: - `id` (string, required) - `saveTo` (string, required): Local path for the PDF, e.g. ./signed/contract.pdf ### `verify_pdf` (~53 tokens) Check a signed PDF Checks a local signed PDF: is the seal intact, when was it sealed, who signed. Works for any PDF; nothing is stored. No API key needed. Input parameters: - `file` (string, required): Local path of the PDF ## Diagnostics Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp#diagnostics ## Score history - 2026-11-05: 67 - 2026-11-04: 66 - 2026-11-03: 66 - 2026-11-02: 65 - 2026-11-01: 65 - 2026-10-31: 64 - 2026-10-30: 64 - 2026-10-29: 63 - 2026-10-28: 63 - 2026-10-27: 62 - 2026-10-26: 62 - 2026-10-25: 61 ## Common questions ### What is the PenlyDoc MCP server? PenlyDoc is an MCP server listed in the public MCP registry as io.github.OrestKlymko/penlydoc-mcp. Send documents for e-signature, track who signed and save sealed PDFs with PenlyDoc. This page covers its npm package (penlydoc-mcp). ### Is the PenlyDoc MCP server safe to use? PenlyDoc scores 67 out of 100 on VerifyMCP. We recorded 6 known advisories against it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm. ### What tools does the PenlyDoc MCP server expose? PenlyDoc exposes 13 tools: get_organisation, list_templates, send_from_template, send_document, list_documents, and 8 more. Their descriptions and schemas cost roughly 946 tokens of context every time the server is loaded. ### Is the PenlyDoc MCP server still maintained? PenlyDoc is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced. ### What licence is the PenlyDoc MCP server under? PenlyDoc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls. ## Links - npm package: https://www.npmjs.com/package/penlydoc-mcp - Socket report: https://socket.dev/npm/package/penlydoc-mcp - Repository: https://github.com/OrestKlymko/penlydoc-mcp - Website: https://penlydoc.com/?utm_source=mcp-registry&utm_medium=listing - Changelog RSS feed: https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp.xml - Changelog JSON feed: https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp.json - HTML version of this page: https://verifymcp.io/servers/orestklymko-penlydoc-mcp/penlydoc-mcp