Dropbox Sign MCP by usefulapi
REMOTE · DROPBOX-SIGN.USEFULAPI.IO
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
Available components
Last scanned (57 minutes ago)
Scores higher than 4% of remote servers
Reachable. Last reached 5 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.
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.
- 1 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 “get_the_signed_files_of_a_finished_request” functional
- New prompt “remind_a_signer_or_cancel_a_pending_request” functional
- New prompt “review_your_templates_their_roles_and_fields” functional
- New prompt “see_which_signature_requests_are_still_waiting” functional
- New prompt “send_a_contract_from_a_template_to_signers” 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 0
- 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 0
- Server version: 1.24.0 → 1.25.0 functional
- 25 Oct 26 0
- 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.2 → 1.21.3 functional
- Server version: 1.21.0 → 1.21.2 functional
- 24 Oct 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Server version: 1.20.0 → 1.21.0 functional
- Server version: 1.19.0 → 1.20.0 functional
- Server version: 1.17.0 → 1.19.0 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 5 Nov 2026 · Probed https://dropbox-sign.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 dropbox-sign.usefulapi.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 38690 | 8 | Verified |
| usefulapi.io. | absent | 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://dropbox-sign.usefulapi.io/mcp | Redirected | 302 | https://usefulapi.io/dropbox-sign/ |
| http (plaintext) | http://dropbox-sign.usefulapi.io/mcp | Inconclusive | 302 | http://dropbox-sign.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 →
dropbox_sign_cancel_signature_request Cancel signature request ~60
Cancels an incomplete signature request. Destructive — signers can no longer sign. API: POST /signature_request/cancel/{signature_request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| signature_request_id | string | yes | The id of the incomplete signature request to cancel. |
No output schema declared.
No examples provided.
dropbox_sign_get_account Get account ~36
Get info about the API-key owner's Dropbox Sign account (id, email, quotas, plan). API: GET /account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dropbox_sign_get_signature_request Get signature request ~53
Get the status and details of a single signature request by id. API: GET /signature_request/{signature_request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| signature_request_id | string | yes | The id of the signature request to retrieve. |
No output schema declared.
No examples provided.
dropbox_sign_get_signed_files_url Get signed files URL ~63
Get a temporary URL to download the signed document(s) for a signature request. API: GET /signature_request/files_as_file_url/{signature_request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| signature_request_id | string | yes | The id of the signature request whose files to fetch. |
No output schema declared.
No examples provided.
dropbox_sign_get_team Get team ~30
Get the caller's team, including its members and invited members. API: GET /team.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
dropbox_sign_get_template Get template ~49
Get a single template's fields, roles, and metadata by id. API: GET /template/{template_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| template_id | string | yes | The id of the template to retrieve. |
No output schema declared.
No examples provided.
dropbox_sign_list_signature_requests List signature requests ~107
List signature requests the account can access, newest first. Paginated. API: GET /signature_request/list.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Account id whose requests to list (defaults to the caller). |
| page | integer | – | Page number to return. Default 1. |
| page_size | integer | – | Results per page (max 100). Default 20. |
| query | string | – | Search string to filter requests (e.g. title, signer email). |
No output schema declared.
No examples provided.
dropbox_sign_list_templates List templates ~99
List reusable templates the account can access. Paginated. API: GET /template/list.
| Name | Type | Req | Description |
|---|---|---|---|
| account_id | string | – | Account id whose templates to list (defaults to the caller). |
| page | integer | – | Page number to return. Default 1. |
| page_size | integer | – | Results per page (max 100). Default 20. |
| query | string | – | Search string to filter templates (e.g. title). |
No output schema declared.
No examples provided.
dropbox_sign_remind_signature_request Remind signature request ~71
Sends a reminder email to a signer for a pending signature request. API: POST /signature_request/remind/{signature_request_id}.
| Name | Type | Req | Description |
|---|---|---|---|
| email_address | string | yes | The email address of the signer to remind. |
| signature_request_id | string | yes | The id of the pending signature request. |
No output schema declared.
No examples provided.
dropbox_sign_send_with_template Send signature request from template ~168
Sends a signature request built from template(s) to the given signers. When test_mode is true (default) it does NOT send real emails; set test_mode=false to send a REAL, legally-binding signature request. API: POST /signature_request/send_with_template.
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | Message body for the signature-request email. |
| signers | array | yes | Signers to send to. Each { role, email_address, name }; role must match a template role. |
| subject | string | – | Subject line for the signature-request email. |
| template_ids | array | yes | Template id(s) to build the request from. |
| test_mode | boolean | – | Test mode. Default TRUE — no real emails sent. Set false to send a REAL legally-binding request. |
No output schema declared.
No examples provided.
How do I install the Dropbox Sign MCP by usefulapi server?
Dropbox Sign MCP by usefulapi is a hosted endpoint at https://dropbox-sign.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 · dropbox-sign.usefulapi.io
claude mcp add --transport http io-usefulapi-dropbox-sign 'https://dropbox-sign.usefulapi.io/mcp'
What is the Dropbox Sign MCP by usefulapi server?
Dropbox Sign MCP by usefulapi is listed in the public MCP registry as io.usefulapi/dropbox-sign. Hosted MCP server for Dropbox Sign, signature requests, templates, and account for AI agents. This page covers its hosted endpoint (https://dropbox-sign.usefulapi.io/mcp).
Is the Dropbox Sign MCP by usefulapi server safe to use?
Dropbox Sign 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 Dropbox Sign MCP by usefulapi server expose?
Dropbox Sign MCP by usefulapi exposes 10 tools: dropbox_sign_get_account, dropbox_sign_get_team, dropbox_sign_list_signature_requests, dropbox_sign_get_signature_request, dropbox_sign_get_signed_files_url, and 5 more. Their descriptions and schemas cost roughly 736 tokens of context every time the server is loaded.
Does the Dropbox Sign MCP by usefulapi server require authentication?
Its publisher declares no required credentials for Dropbox Sign 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 Dropbox Sign MCP by usefulapi server still maintained?
Dropbox Sign MCP by usefulapi 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.