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.

io.github.rclone-ui/rclone

NPM · RCLONE-MCP · SCANNED SEP 20

MCP server for the Rclone RC API, with selectable toolsets.

Available components

0 this week 82 Trust /100
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 Security98
  • 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
  • 37 of 121 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability76
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 6347 tokens (~109/item across 58 items; 58 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
  • Stability observed for 28 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 Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 9 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "operations_cleanup" implies "remove" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 58 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
Install

How do I install the io.github.rclone-ui/rclone MCP server?

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

npm · rclone-mcp

# add to Claude Code
claude mcp add rclone-ui-rclone -- npx -y rclone-mcp
// .cursor/mcp.json
{
  "mcpServers": {
    "rclone-ui-rclone": {
      "command": "npx",
      "args": [
        "-y",
        "rclone-mcp"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rclone-ui-rclone": {
      "command": "npx",
      "args": [
        "-y",
        "rclone-mcp"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rclone-ui-rclone -- npx -y rclone-mcp
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rclone-ui-rclone": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "rclone-mcp"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rclone-ui-rclone --command npx --arg -y --arg rclone-mcp
# ~/.hermes/config.yaml
mcp_servers:
  rclone-ui-rclone:
    command: "npx"
    args: ["-y", "rclone-mcp"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rclone-ui-rclone": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "rclone-mcp"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rclone-ui-rclone -t stdio -c npx -a -y rclone-mcp
// mcp.json
{
  "mcpServers": {
    "rclone-ui-rclone": {
      "command": "npx",
      "args": [
        "-y",
        "rclone-mcp"
      ]
    }
  }
}
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.

  • 20 Sept 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.

  • 18 Sept 26 +1

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

  • 16 Sept 26 −3
    • Security disclosure: unverified → fail functional
    • Stability: pass → 0.80 functional
  • 15 Sept 26 +1
    • Stability: 0.97 → pass security
    • Security disclosure: fail → unverified functional
  • 13 Sept 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 Sept 26 +1

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

  • 9 Sept 26 −3
    • Stability: pass → 0.80 functional
  • 8 Sept 26 +1
    • Stability: 0.97 → pass security
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 20 Sept 2026 · Analysed npm/rclone-mcp@1.0.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 121 packages
Packages resolved 121
Stale 35
No linked repository 2
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 58 exposed · ~6,347 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
rc_error ~58

Return a test error — Always returns an error response incorporating the supplied parameters, useful for testing error handling.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
paramsobjectAdditional arbitrary parameters allowed.

No output schema declared.

No examples provided.

rc_list ~60

List RC commands — Returns metadata about every available RC command, including whether authentication is required.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
_groupstringAssign the request to a custom stats group.

No output schema declared.

No examples provided.

rc_noop ~54

Echo request parameters — Returns all supplied parameters unchanged so you can verify RC connectivity.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
paramsobjectAdditional arbitrary parameters allowed.

No output schema declared.

No examples provided.

rc_noop_auth ~61

Echo parameters (auth required) — Same as `rc/noop`, but requires authentication to validate access control.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
paramsobjectAdditional arbitrary parameters allowed.

No output schema declared.

No examples provided.

sync_bisync ~459

Bidirectional sync — Performs a bidirectional synchronisation between two paths, supporting safety checks and recovery options.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
_configstringJSON encoded config overrides applied for this call only.
_filterstringJSON encoded filter overrides applied for this call only.
_groupstringAssign the request to a custom stats group.
backupdir1stringBackup directory on the first remote for changed files.
backupdir2stringBackup directory on the second remote for changed files.
checkAccessbooleanSet to true to abort if `RCLONE_TEST` files are missing on either side.
checkFilenamestringOverride the access-check sentinel filename; defaults to `RCLONE_TEST`.
checkSyncbooleanControls final listing comparison; leave true for normal verification or set false to skip.
createEmptySrcDirsbooleanSet to true to mirror empty directories between the two paths.
dryRunbooleanSet to true to simulate the bisync run without making changes.
filtersFilestringPath to an rclone filters file applied to both paths.
forcebooleanSet to true to bypass the `maxDelete` safety check.
ignoreListingChecksumbooleanSet to true to ignore checksum differences when comparing listings.
maxDeletenumberAbort the run if deletions exceed this percentage (default 50).
noCleanupbooleanSet to true to keep bisync working files after completion.
path1stringFirst remote directory, e.g. `drive:path1`.
path2stringSecond remote directory, e.g. `drive:path2`.
removeEmptyDirsbooleanSet to true to remove empty directories during cleanup.
resilientbooleanSet to true to allow retrying after certain recoverable errors.
resyncbooleanSet to true to perform a one-time resync, rebuilding bisync history.
workdirstringDirectory path used to store bisync working files.

No output schema declared.

No examples provided.

sync_copy ~145

Copy source to destination — Copies objects from a source remote to a destination remote without deleting destination files.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
_configstringJSON encoded config overrides applied for this call only.
_filterstringJSON encoded filter overrides applied for this call only.
_groupstringAssign the request to a custom stats group.
createEmptySrcDirsbooleanSet to true to replicate empty source directories on the destination.
dstFsstringDestination remote path to copy to.
srcFsstringSource remote path to copy from.

No output schema declared.

No examples provided.

sync_move ~175

Move source to destination — Moves objects from a source remote to a destination remote, optionally cleaning up empty directories.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
_configstringJSON encoded config overrides applied for this call only.
_filterstringJSON encoded filter overrides applied for this call only.
_groupstringAssign the request to a custom stats group.
createEmptySrcDirsbooleanSet to true to create empty source directories on the destination.
deleteEmptySrcDirsbooleanSet to true to delete empty directories from the source after the move completes.
dstFsstringDestination remote path that will receive moved files.
srcFsstringSource remote path whose contents will be moved.

No output schema declared.

No examples provided.

sync_sync ~163

Sync source to destination — Synchronises a source remote to a destination remote, making the destination match the source.

NameTypeReqDescription
_asyncbooleanRun the command asynchronously. Returns a job id immediately.
_configstringJSON encoded config overrides applied for this call only.
_filterstringJSON encoded filter overrides applied for this call only.
_groupstringAssign the request to a custom stats group.
createEmptySrcDirsbooleanSet to true to create empty source directories on the destination.
dstFsstringDestination remote path to sync to, e.g. `drive:dst`.
srcFsstringSource remote path to sync from, e.g. `drive:src`.

No output schema declared.

No examples provided.

Common questions

What is the io.github.rclone-ui/rclone MCP server?

io.github.rclone-ui/rclone is an MCP server listed in the public MCP registry as io.github.rclone-ui/rclone. MCP server for the Rclone RC API, with selectable toolsets. This page covers its npm package (rclone-mcp).

Is the io.github.rclone-ui/rclone MCP server safe to use?

io.github.rclone-ui/rclone scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. 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.github.rclone-ui/rclone MCP server expose?

io.github.rclone-ui/rclone exposes 58 tools: rc_noop, operations_cleanup, operations_copyfile, operations_copyurl, operations_delete, and 53 more. Their descriptions and schemas cost roughly 6,347 tokens of context every time the server is loaded.

Is the io.github.rclone-ui/rclone MCP server still maintained?

io.github.rclone-ui/rclone 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.

What licence is the io.github.rclone-ui/rclone MCP server under?

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