Remote MCP · Endpoint

Dropbox Sign MCP by usefulapi MCP server

No. Dropbox Sign MCP by usefulapi answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://dropbox-sign.usefulapi.io/mcp

The last check completed an MCP handshake.

Registry name
io.usefulapi/dropbox-sign
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
317 ms
Tools exposed
10 tools
Uptime, last 30 days
52.9% from 17 checks
Described by its publisher as
Hosted MCP server for Dropbox Sign — signature requests, templates, and account for AI agents.
Website
https://usefulapi.io/dropbox-sign/
Repository
https://github.com/m190/usefulapi-mcp
Listing
From the official MCP registry (active).
Recent checks of Dropbox Sign MCP by usefulapi
CheckedResultHandshake
9 hours agoHandshake completed317 ms
2 days agoHandshake completed218 ms
4 days agoHandshake completed206 ms
5 days agoHandshake completed176 ms
7 days agoFailed - the check failed for an unclassified reason—
8 days agoHandshake completed189 ms
9 days agoHandshake completed225 ms
12 days agoHandshake completed365 ms
13 days agoFailed - the check failed for an unclassified reason—
15 days agoHandshake completed207 ms
16 days agoFailed - the check failed for an unclassified reason—
17 days agoFailed - the check failed for an unclassified reason—
19 days agoFailed - the check failed for an unclassified reason—
19 days agoFailed - the check failed for an unclassified reason—
20 days agoHandshake completed216 ms
21 days agoFailed - the check failed for an unclassified reason—
23 days agoFailed - the check failed for an unclassified reason—

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 9 responding of 17.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Dropbox Sign MCP by usefulapi and makes no claim about it beyond what these checks measured.