Home / MCP registry index / io.usefulapi/dropbox-sign
Dropbox Sign MCP by usefulapi
io.usefulapi/dropbox-sign in the official MCP registry.
Endpoint https://dropbox-sign.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.
The registry describes it as: Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
We read its 10 tools on 2026-10-25. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
dropbox_sign_get_account dropbox_sign_get_team dropbox_sign_list_signature_requests dropbox_sign_get_signature_request dropbox_sign_get_signed_files_url dropbox_sign_list_templates dropbox_sign_get_template dropbox_sign_send_with_template dropbox_sign_cancel_signature_request dropbox_sign_remind_signature_request
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/io-usefulapi-dropbox-sign)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.