Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Dropbox

NPM · @PIPEWORX/MCP-DROPBOX · 2 COMPONENTS

Dropbox MCP Pack — wraps the Dropbox API v2

+3 this week 89 Trust /100

Last scanned (8 hours ago)

Scores higher than 88% of npm servers

Category Documents and Files

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-dropbox). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 14 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 383 tokens (~76/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
  • Stability observed for 17 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

  • 9 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

  • 3 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 2 Nov 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 1 Nov 26 +2
    • Stability: unverified → 0.10 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
Diagnostics

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 15 Nov 2026 · Analysed npm/@pipeworx/mcp-dropbox@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-dropbox
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-dropbox/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3617567094
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:cc3b10b07d6ad40ebdc7c1deaeb65222ff205fb93c9b9a233425e9b2349c1a8eb96ad537d1594dae8a63c4037c1d966561c307bdd07c9c016c5657dda

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~331 tokens

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 →

Tool Tokens
dropbox_create_folder ~77

Create a new folder in Dropbox at a specified path. Returns folder metadata. Use to organize files or set up directory structures.

NameTypeReqDescription
autorenameboolean–Auto-rename if a folder with the same name exists (default false)
pathstringyesPath of the folder to create (e.g., "/New Folder")

No output schema declared.

No examples provided.

dropbox_download ~51

Download a file from Dropbox and return its content as text plus metadata (size, type, modified date). Use to retrieve file contents for processing or inspection.

NameTypeReqDescription
pathstringyesFile path to download

No output schema declared.

No examples provided.

dropbox_get_metadata ~53

Get detailed metadata for a file or folder: size, modified date, ID, sharing status, and revision info. Use before downloading or modifying to inspect properties.

NameTypeReqDescription
pathstringyesFile or folder path

No output schema declared.

No examples provided.

dropbox_list_folder ~80

List files and folders in a Dropbox directory. Returns names, types, sizes, and modification dates. Use when browsing folder contents or checking what's stored at a path.

NameTypeReqDescription
limitnumber–Max entries to return (default 100)
pathstringyesFolder path — "" for the account root, otherwise e.g. "/Documents"

No output schema declared.

No examples provided.

dropbox_search ~70

Search Dropbox for files and folders by name or content. Returns matching paths, file types, and metadata. Use when you need to find a file without knowing its exact location.

NameTypeReqDescription
max_resultsnumber–Maximum results to return (default 20)
querystringyesSearch query string

No output schema declared.

No examples provided.

Install

How do I install the Dropbox MCP server?

Dropbox runs locally as an npm package, launched with npx -y @pipeworx/mcp-dropbox. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @pipeworx/mcp-dropbox

# add to Claude Code
claude mcp add pipeworx-io-dropbox -- npx -y @pipeworx/mcp-dropbox
Common questions

What is the Dropbox MCP server?

Dropbox is an MCP server listed in the public MCP registry as io.github.pipeworx-io/dropbox. Dropbox MCP Pack, wraps the Dropbox API v2. This page covers its npm package (@pipeworx/mcp-dropbox).

Is the Dropbox MCP server safe to use?

Dropbox scores 89 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 15 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 MCP server expose?

Dropbox exposes 5 tools: dropbox_list_folder, dropbox_search, dropbox_get_metadata, dropbox_download, dropbox_create_folder. Their descriptions and schemas cost roughly 331 tokens of context every time the server is loaded.

Is the Dropbox MCP server still maintained?

Dropbox is still listed as active in the MCP registry. We last reached this channel on 15 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the Dropbox MCP server under?

Dropbox declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the Dropbox MCP server?

VerifyMCP ran 16 checks on Dropbox, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.