io.usefulapi/dropbox-sign
REMOTE · DROPBOX-SIGN.USEFULAPI.IO · SCANNED SEP 20
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
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 Security78
- 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 enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. 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
- 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 Usability82
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 736 tokens (~73/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 10 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/dropbox-sign MCP server?
io.usefulapi/dropbox-sign 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'
{
"mcpServers": {
"io-usefulapi-dropbox-sign": {
"url": "https://dropbox-sign.usefulapi.io/mcp"
}
}
} {
"servers": {
"io-usefulapi-dropbox-sign": {
"type": "http",
"url": "https://dropbox-sign.usefulapi.io/mcp"
}
}
} [mcp_servers.io-usefulapi-dropbox-sign] url = "https://dropbox-sign.usefulapi.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-usefulapi-dropbox-sign": {
"type": "remote",
"url": "https://dropbox-sign.usefulapi.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-usefulapi-dropbox-sign --url 'https://dropbox-sign.usefulapi.io/mcp' --transport streamable-http
mcp_servers:
io-usefulapi-dropbox-sign:
url: "https://dropbox-sign.usefulapi.io/mcp" {
"McpServers": {
"io-usefulapi-dropbox-sign": {
"Transport": "http",
"Url": "https://dropbox-sign.usefulapi.io/mcp"
}
}
} assistant mcp add io-usefulapi-dropbox-sign -t streamable-http -u 'https://dropbox-sign.usefulapi.io/mcp'
{
"mcpServers": {
"io-usefulapi-dropbox-sign": {
"type": "http",
"url": "https://dropbox-sign.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.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 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
- 31 Jul 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
- 30 Jul 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
- 28 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
- 27 Jul 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
- 26 Jul 26 0
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 20 Sept 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 | 14 Sept 2026 | 13 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 95c88f1b2ea3abeb13712643a843282e |
| SANs: usefulapi.io, dropbox-sign.usefulapi.io, *.dropbox-sign.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 | 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://dropbox-sign.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"
Bearer realm="OAuth", resource_metadata="https://dropbox-sign.usefulapi.io/.well-known/oauth-protected-resource/mcp", error="invalid_token", error_description="Missing or invalid access token"Protected resource metadata
| Document | https://dropbox-sign.usefulapi.io/.well-known/oauth-protected-resource/mcp |
|---|---|
| Retrieved | Yes |
| Resource | https://dropbox-sign.usefulapi.io/mcp |
| Authorisation server | https://dropbox-sign.usefulapi.io |
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 | Verified | 200 | |
| http (plaintext) | http://dropbox-sign.usefulapi.io/mcp | Inconclusive | 401 |
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.
What is the io.usefulapi/dropbox-sign MCP server?
io.usefulapi/dropbox-sign is an MCP server 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 io.usefulapi/dropbox-sign MCP server safe to use?
io.usefulapi/dropbox-sign scores 86 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/dropbox-sign MCP server expose?
io.usefulapi/dropbox-sign 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 io.usefulapi/dropbox-sign MCP server require authentication?
Yes. io.usefulapi/dropbox-sign 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/dropbox-sign MCP server still maintained?
io.usefulapi/dropbox-sign is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.