io.usefulapi/documenso
REMOTE · DOCUMENSO.USEFULAPI.IO · SCANNED OCT 4
Read and send documents for signature — templates, recipients, fields and folders.
Available components
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 Security89
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1256 tokens (~78/item across 16 items; 16 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.usefulapi/documenso MCP server?
io.usefulapi/documenso 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'
{
"mcpServers": {
"io-usefulapi-documenso": {
"url": "https://documenso.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-documenso": {
"type": "http",
"url": "https://documenso.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-documenso] url = "https://documenso.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-documenso": {
"type": "remote",
"url": "https://documenso.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-documenso --url 'https://documenso.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-documenso:
url: "https://documenso.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-documenso": {
"Transport": "http",
"Url": "https://documenso.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-documenso -t streamable-http -u 'https://documenso.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-documenso": {
"type": "http",
"url": "https://documenso.usefulapi.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 4 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Oct 26 +1
- Server version: 1.3.0 → 1.5.1 functional
- 1 Oct 26 +5
- HTTPS: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Server version: 1.0.0 → 1.3.0 functional
- 30 Sept 26 +53
- Authorization: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 29 Sept 26 18
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 4 Oct 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 | 13 Sept 2026 | 12 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | d9be3287b0fde9630e825ba1f79bff3f |
| 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. | present | 57355 | 8 | Verified |
| usefulapi.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer realm="OAuth", resource_metadata="https://documenso.usefulapi.io/.well-known/oauth-protected-resource/mcp"
Bearer realm="OAuth", resource_metadata="https://documenso.usefulapi.io/.well-known/oauth-protected-resource/mcp"Protected resource metadata
| Document | https://documenso.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://documenso.usefulapi.io/mcp |
| Authorisation server | https://documenso.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://documenso.usefulapi.io/mcp | HTTPS enforced | 301 | https://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.
What is the io.usefulapi/documenso MCP server?
io.usefulapi/documenso is an MCP server 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 io.usefulapi/documenso MCP server safe to use?
io.usefulapi/documenso scores 78 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 io.usefulapi/documenso MCP server expose?
io.usefulapi/documenso 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 io.usefulapi/documenso MCP server require authentication?
Yes. io.usefulapi/documenso asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the io.usefulapi/documenso MCP server still maintained?
io.usefulapi/documenso is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.