Documenso MCP by usefulapi
REMOTE · DOCUMENSO.USEFULAPI.IO
Read and send documents for signature — templates, recipients, fields and folders.
Available components
Last scanned (23 hours ago)
Scores higher than 3% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Documents and Files
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but the endpoint redirected instead of responding directly. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
Checks we ran (4)
- TLS certificate
- HSTS header
- DNSSEC
- Transport
Checks we could not complete (7)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not yet verified: we couldn't confirm whether this endpoint requires it.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port redirected somewhere other than https, so enforcement is unproven.
- Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
- Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- Capabilities in Capabilities (scores 0 for this)Capabilities not yet verified: we couldn't read the endpoint's capabilities.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 2 Nov 26 −62
- Endpoint reachability: reachable → not serving MCP ▼ security
- Stability: pass → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Authorization: pass → unverified ▼ security
- Schema quality: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- 31 Oct 26 +3
- Authorization: partial → pass ▲ security
- MCP protocol: fail → pass ▲ functional
- New prompt “add_a_signer_to_a_draft_and_send_it” functional
- New prompt “check_who_has_signed_a_document_and_who_has_not” functional
- New prompt “create_a_document_from_a_template_and_send_it” functional
- New prompt “find_documents_that_still_wait_for_a_signature” functional
- New prompt “get_the_pdf_link_and_attachments_of_a_document” functional
- New prompt “resend_the_signing_invitation_to_recipients” functional
- MCP protocol version: 2025-06-18 → 2025-11-25 functional
- Server version: 1.31.0 → 1.33.0 functional
- Server version: 1.30.0 → 1.31.0 functional
- Server version: 1.29.2 → 1.30.0 functional
- 30 Oct 26 +1
- Stability: 0.97 → pass security
- Server version: 1.29.1 → 1.29.2 functional
- Server version: 1.29.0 → 1.29.1 functional
- 29 Oct 26 0
- Server version: 1.28.0 → 1.29.0 functional
- Server version: 1.27.0 → 1.28.0 functional
- 28 Oct 26 0
- Server version: 1.25.0 → 1.27.0 functional
- 27 Oct 26 +1
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 +1
- Server version: 1.23.0 → 1.24.0 functional
- Server version: 1.22.0 → 1.23.0 functional
- Server version: 1.21.3 → 1.22.0 functional
- Server version: 1.21.0 → 1.21.3 functional
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 21 Nov 2026 · Probed https://documenso.usefulapi.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=usefulapi.io | CN=WE1,O=Google Trust Services,C=US | 11 Nov 2026 | 9 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | 93e2fea3bbc31354138c8a47c5e87592 |
| SANs: usefulapi.io, *.usefulapi.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of documenso.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| usefulapi.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|---|
| HTTP status | 302 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://documenso.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/documenso/ |
| http (plaintext) | http://documenso.usefulapi.io/mcp | Inconclusive | 302 | http://documenso.usefulapi.io/mcp |
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 →
documenso_add_recipient Add a recipient to a document ~110
Add a signer, approver, viewer or CC to a draft document. Documenso v2: POST /document/recipient/create.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document's numeric id. Must still be a draft. |
| string | yes | The recipient's email address. | |
| name | string | yes | The recipient's name. |
| role | string | yes | What this recipient does with the document. |
| signingOrder | integer | – | Position in a sequential signing order. |
No output schema declared.
No examples provided.
documenso_create_document_from_template Create a document from a template ~142
Create a new document from an existing template, filling in the real recipients. Set distribute_document to true to send it for signature immediately. Call documenso_get_template first to read the placeholder recipient ids. Documenso v2: POST /template/use.
| Name | Type | Req | Description |
|---|---|---|---|
| distribute_document | boolean | – | Send the document for signature immediately. Defaults to false (creates a draft). |
| externalId | string | – | Your own reference id for the new document. |
| folderId | string | – | Create the document inside this folder. |
| recipients | array | yes | One entry per template recipient placeholder. |
| templateId | integer | yes | The template to instantiate. |
No output schema declared.
No examples provided.
documenso_create_folder Create a folder ~66
Create a folder for organising documents or templates. Documenso v2: POST /folder/create.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | yes | The folder name. |
| parentId | string | – | Nest it inside this parent folder. |
| type | string | – | What the folder holds. |
No output schema declared.
No examples provided.
documenso_distribute_document Send a document for signature ~76
Send a draft document to its recipients for signature. This emails real people. Documenso v2: POST /document/distribute.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The draft document to send. |
| message | string | – | Override the invitation email body. |
| subject | string | – | Override the invitation email subject. |
No output schema declared.
No examples provided.
documenso_duplicate_document Duplicate a document ~48
Copy an existing document into a new draft, keeping its fields. Documenso v2: POST /document/duplicate.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document to copy. |
No output schema declared.
No examples provided.
documenso_get_document Get one document ~50
Fetch a single document with its recipients, fields and current status. Documenso v2: GET /document/{documentId}.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document's numeric id. |
No output schema declared.
No examples provided.
documenso_get_document_download_url Get a document download link ~81
Get a download URL for a document's PDF. Returns a link, not the file bytes. Documenso v2: GET /document/{documentId}/download.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document's numeric id. |
| version | string | – | Which PDF to link to. Defaults to the signed version when one exists. |
No output schema declared.
No examples provided.
documenso_get_documents_by_ids Get several documents by id ~61
Fetch several documents in one call. Read-only despite being a POST — the v2 API is action-shaped. Documenso v2: POST /document/get-many.
| Name | Type | Req | Description |
|---|---|---|---|
| documentIds | array | yes | The numeric document ids to fetch. |
No output schema declared.
No examples provided.
documenso_get_field Get one field ~55
Fetch a single document field — its type, page, position and inserted value. Documenso v2: GET /document/field/{fieldId}.
| Name | Type | Req | Description |
|---|---|---|---|
| fieldId | integer | yes | The field's numeric id. |
No output schema declared.
No examples provided.
documenso_get_recipient Get one recipient ~58
Fetch a single recipient — their email, role, signing order and whether they have signed. Documenso v2: GET /document/recipient/{recipientId}.
| Name | Type | Req | Description |
|---|---|---|---|
| recipientId | integer | yes | The recipient's numeric id. |
No output schema declared.
No examples provided.
documenso_get_template Get one template ~66
Fetch a single template with its recipient placeholders and fields — read this before calling documenso_create_document_from_template so you know the recipient ids. Documenso v2: GET /template/{templateId}.
| Name | Type | Req | Description |
|---|---|---|---|
| templateId | integer | yes | The template's numeric id. |
No output schema declared.
No examples provided.
documenso_list_document_attachments List document attachments ~45
List the attachments on one document. Documenso v2: GET /document/attachment.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document's numeric id. |
No output schema declared.
No examples provided.
documenso_list_documents List documents ~147
List documents, optionally filtered by status, folder, source template or a text query. Documenso v2: GET /document.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | string | – | Only documents in this folder. |
| orderByDirection | string | – | Sort by creation time. Defaults to desc. |
| page | integer | – | 1-based page number. |
| perPage | integer | – | Results per page, 1-100. |
| query | string | – | Free-text search over document titles. |
| source | string | – | How the document was created. |
| status | string | – | Only documents in this state. |
| templateId | integer | – | Only documents created from this template. |
No output schema declared.
No examples provided.
documenso_list_folders List folders ~86
List folders used to organise documents and templates. Documenso v2: GET /folder.
| Name | Type | Req | Description |
|---|---|---|---|
| page | integer | – | 1-based page number. |
| parentId | string | – | Only folders inside this parent folder. |
| perPage | integer | – | Results per page, 1-100. |
| query | string | – | Free-text search over folder names. |
No output schema declared.
No examples provided.
documenso_list_templates List templates ~93
List reusable document templates. Templates are how you create a new document without uploading a PDF. Documenso v2: GET /template.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | string | – | Only templates in this folder. |
| page | integer | – | 1-based page number. |
| perPage | integer | – | Results per page, 1-100. |
| query | string | – | Free-text search over template titles. |
No output schema declared.
No examples provided.
documenso_redistribute_document Resend a document to recipients ~72
Resend the signing invitation to named recipients of an already-sent document. This emails real people. Documenso v2: POST /document/redistribute.
| Name | Type | Req | Description |
|---|---|---|---|
| documentId | integer | yes | The document to resend. |
| recipients | array | yes | The numeric recipient ids to email again. |
No output schema declared.
No examples provided.
How do I install the Documenso MCP by usefulapi server?
Documenso MCP by usefulapi is a hosted endpoint at https://documenso.usefulapi.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · documenso.usefulapi.io
claude mcp add --transport http io-usefulapi-documenso 'https://documenso.usefulapi.io/mcp'
What is the Documenso MCP by usefulapi server?
Documenso MCP by usefulapi is listed in the public MCP registry as io.usefulapi/documenso. Read and send documents for signature, templates, recipients, fields and folders. This page covers its hosted endpoint (https://documenso.usefulapi.io/mcp).
Is the Documenso MCP by usefulapi server safe to use?
Documenso MCP by usefulapi scores 18 out of 100 on VerifyMCP. 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 Documenso MCP by usefulapi server expose?
Documenso MCP by usefulapi exposes 16 tools: documenso_list_documents, documenso_get_document, documenso_get_documents_by_ids, documenso_get_recipient, documenso_get_field, and 11 more. Their descriptions and schemas cost roughly 1,256 tokens of context every time the server is loaded.
Does the Documenso MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Documenso MCP by usefulapi. We have not been able to confirm that against the live endpoint, and a server can require authorisation without declaring it here.
Is the Documenso MCP by usefulapi server still maintained?
Documenso MCP by usefulapi is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Documenso MCP by usefulapi server?
VerifyMCP ran 4 checks on Documenso MCP by usefulapi, covering TLS certificate, HSTS header, DNSSEC and Transport. 7 items could not be completed, a gap on our side rather than a finding about Documenso MCP by usefulapi: Authorization, HTTPS, Schema quality, Stability and 3 more. 5 categories score 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.