Remote MCP · Endpoint

Dropbox MCP server

No. Dropbox answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/dropbox/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/dropbox
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
151 ms
Tools exposed
49 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
Dropbox MCP Pack — wraps the Dropbox API v2
Listing
From the official MCP registry (active).
Recent checks of Dropbox
CheckedResultHandshake
1 hour agoHandshake completed151 ms
1 day agoHandshake completed304 ms
2 days agoHandshake completed175 ms
3 days agoHandshake completed110 ms
4 days agoHandshake completed58 ms
5 days agoHandshake completed61 ms
6 days agoHandshake completed91 ms
8 days agoHandshake completed403 ms
11 days agoHandshake completed87 ms
13 days agoHandshake completed115 ms
16 days agoHandshake completed136 ms
18 days agoHandshake completed1.59 s
20 days agoHandshake completed2.51 s
22 days agoHandshake completed79 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed61 ms
27 days agoHandshake completed80 ms
29 days agoHandshake completed45 ms

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

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.

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