PenlyDoc
NPM · PENLYDOC-MCP
Send documents for e-signature, track who signed and save sealed PDFs with PenlyDoc.
Available components
Last scanned (9 hours ago)
Scores higher than 34% of npm servers
Category Documents and Files
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. How we score → Why this is hard to score →
Supply Chain Security81
- No malware found by supply-chain analysis.Pass
- CVE check failed: a known high-severity CVE affects @modelcontextprotocol/sdk 1.30.1, a direct dependency. A fixed version is available. View diagnostics → Fail
- No install/post-install scripts declared.Pass
- 30 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 10 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 992 tokens (~76/item across 13 items; 13 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
- Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage75
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 24% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 4 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 5 Nov 26 +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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 25 Oct 26 61
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/penlydoc-mcp@0.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Vulnerabilities 6 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-22jm-h49p-29qw | CVE-2026-111767 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:L/A:L | yes |
| GHSA-46jr-4wx8-v453 | CVE-2026-111768 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
| GHSA-6prh-2h8m-c8cw | CVE-2026-111769 | medium | CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:L/A:N | yes |
| GHSA-6qxp-vccf-f47h | CVE-2026-104850 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:N/A:N | yes |
| GHSA-rvq5-wwqv-78pq | CVE-2026-111771 | medium | CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:N | yes |
| GHSA-mrhx-c7xc-m3w5 | CVE-2023-54404 | high | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
cancel_document Cancel a document ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| reason | string | yes | – |
No output schema declared.
No examples provided.
create_signing_link Signing link for an embedded signer ~77
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.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| recipientId | string | yes | – |
| returnUrl | string | – | – |
No output schema declared.
No examples provided.
download_signed_pdf Download the signed PDF ~64
Saves the sealed, signed PDF (with the certificate of completion as last page) of a COMPLETED document to a local file.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
| saveTo | string | yes | Local path for the PDF, e.g. ./signed/contract.pdf |
No output schema declared.
No examples provided.
get_document Document status ~39
Full status of one document: each person, whether they opened, signed or declined (with the reason), and when.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_history Document history ~41
The hash-chained history of a document: every step with time, who and IP address, and whether the chain is intact.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_organisation Organisation ~29
Shows which PenlyDoc organisation the API key belongs to, its default language and its sending limit.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_documents List documents ~53
Lists documents sent for signature, newest first, with who has signed. Filter by status or by your externalRef.
| Name | Type | Req | Description |
|---|---|---|---|
| externalRef | string | – | – |
| limit | integer | – | – |
| status | string | – | – |
No output schema declared.
No examples provided.
list_templates List templates ~48
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
send_document Send a document ~193
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).
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Values for {{data:Key}} tags in the PDF |
| expiresInDays | integer | – | – |
| externalRef | string | – | – |
| fields | array | – | – |
| files | array | yes | Local file paths |
| message | string | – | – |
| recipients | array | yes | – |
| send | boolean | yes | – |
| signingOrder | string | – | – |
| title | string | yes | – |
No output schema declared.
No examples provided.
send_draft Send a draft ~39
Sends a DRAFT document: PenlyDoc e-mails the first people to sign. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
send_from_template Send from a template ~210
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Keyed by role key from list_templates, e.g. {"tenant": {"name": "Mia Novak", "email": "mia@example.com"}} |
| send | boolean | yes | true = e-mail people now; false = draft |
| templateId | string | yes | – |
| title | string | – | – |
No output schema declared.
No examples provided.
send_reminder Remind ~37
E-mails a reminder now to everyone whose turn it is on this document. Confirm with the user first.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
verify_pdf Check a signed PDF ~53
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.
| Name | Type | Req | Description |
|---|---|---|---|
| file | string | yes | Local path of the PDF |
No output schema declared.
No examples provided.
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.
npm · penlydoc-mcp
claude mcp add orestklymko-penlydoc-mcp -- npx -y penlydoc-mcp
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.