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.ExpertVagabond/mega

NPM · MEGA-MCP-SERVER

MEGA cloud storage CLI MCP server

Available components

0 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 53% 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 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
  • 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency18
Schema Quality & AI Usability71
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 825 tokens (~41/item across 20 items; 20 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "mega_rm" implies "rm" 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 20 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.

  • 19 Nov 26 0
    • Stability: 0.97 → pass security
  • 18 Nov 26 0
    • Stability: pass → 0.97 functional
  • 12 Nov 26 0
    • Stability: 0.97 → pass security
  • 11 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 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 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

  • 7 Nov 26 −2
    • Stability: pass → 0.83 functional
  • 1 Nov 26 0
    • Stability: 0.97 → pass security
  • 31 Oct 26 0
    • Stability: pass → 0.97 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 21 Nov 2026 · Analysed npm/mega-mcp-server@1.0.1

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 92 packages
Packages resolved 92
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 20 exposed · ~825 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
mega_cat ~27

Display contents of a remote file

NameTypeReqDescription
pathstringyesRemote file path to display

No output schema declared.

No examples provided.

mega_cd ~29

Change current working directory in MEGA cloud

NameTypeReqDescription
pathstringyesRemote path to change to

No output schema declared.

No examples provided.

mega_cp ~38

Copy files/folders within MEGA cloud storage

NameTypeReqDescription
destinationstringyesDestination remote path
sourcestringyesSource remote path

No output schema declared.

No examples provided.

mega_df ~29

Show MEGA cloud storage space usage

NameTypeReqDescription
humanboolean–Show sizes in human-readable format

No output schema declared.

No examples provided.

mega_du ~39

Show disk usage of remote path

NameTypeReqDescription
humanboolean–Show sizes in human-readable format
pathstring–Remote path to check

No output schema declared.

No examples provided.

mega_export ~65

Create a public link for a file/folder

NameTypeReqDescription
expirestring–Expiration time (e.g., '1d', '1w', '1m')
passwordstring–Password protect the link
pathstringyesRemote path to export

No output schema declared.

No examples provided.

mega_find ~47

Search for files/folders in MEGA cloud storage

NameTypeReqDescription
pathstring–Path to search in (default: /)
patternstringyesSearch pattern (supports wildcards)

No output schema declared.

No examples provided.

mega_get ~49

Download files from MEGA cloud to local filesystem

NameTypeReqDescription
local_pathstring–Local destination path (default: current directory)
remote_pathstringyesRemote path in MEGA to download

No output schema declared.

No examples provided.

mega_import ~45

Import a public MEGA link to your account

NameTypeReqDescription
linkstringyesMEGA public link to import
remote_pathstring–Destination path in your MEGA

No output schema declared.

No examples provided.

mega_ls ~57

List files and folders in MEGA cloud storage

NameTypeReqDescription
longboolean–Show detailed listing with sizes and dates
pathstring–Remote path to list (default: current directory)
recursiveboolean–List recursively

No output schema declared.

No examples provided.

mega_mkdir ~42

Create a directory in MEGA cloud storage

NameTypeReqDescription
parentsboolean–Create parent directories as needed
pathstringyesRemote path for new directory

No output schema declared.

No examples provided.

mega_mv ~40

Move or rename files/folders in MEGA cloud storage

NameTypeReqDescription
destinationstringyesDestination remote path
sourcestringyesSource remote path

No output schema declared.

No examples provided.

mega_put ~47

Upload files from local filesystem to MEGA cloud

NameTypeReqDescription
local_pathstringyesLocal file/folder path to upload
remote_pathstring–Remote destination path in MEGA

No output schema declared.

No examples provided.

mega_pwd ~17

Print current working directory in MEGA cloud

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

mega_rm ~50

Remove files or folders from MEGA cloud storage

NameTypeReqDescription
forceboolean–Force removal without confirmation
pathstringyesRemote path to remove
recursiveboolean–Remove directories recursively

No output schema declared.

No examples provided.

mega_share ~72

Share a folder with another MEGA user

NameTypeReqDescription
access_levelstring–Access level: 'r' (read), 'rw' (read-write), 'full' (full access)
emailstringyesEmail of user to share with
pathstringyesRemote folder path to share

No output schema declared.

No examples provided.

mega_sync ~59

Set up sync between local and remote folders

NameTypeReqDescription
list_onlyboolean–Just list current syncs instead of creating new one
local_pathstring–Local folder path
remote_pathstring–Remote MEGA folder path

No output schema declared.

No examples provided.

mega_transfers ~28

Show current transfers (uploads/downloads)

NameTypeReqDescription
show_completedboolean–Include completed transfers

No output schema declared.

No examples provided.

mega_tree ~26

Show directory tree structure

NameTypeReqDescription
pathstring–Remote path to show tree for

No output schema declared.

No examples provided.

mega_whoami ~19

Get current logged-in MEGA account information

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Install

How do I install the io.github.ExpertVagabond/mega MCP server?

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

npm · mega-mcp-server

# add to Claude Code
claude mcp add expertvagabond-mega -- npx -y mega-mcp-server
Common questions

What is the io.github.ExpertVagabond/mega MCP server?

io.github.ExpertVagabond/mega is an MCP server listed in the public MCP registry as io.github.ExpertVagabond/mega. MEGA cloud storage CLI MCP server. This page covers its npm package (mega-mcp-server).

Is the io.github.ExpertVagabond/mega MCP server safe to use?

io.github.ExpertVagabond/mega scores 76 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 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.ExpertVagabond/mega MCP server expose?

io.github.ExpertVagabond/mega exposes 20 tools: mega_whoami, mega_ls, mega_cd, mega_pwd, mega_mkdir, and 15 more. Their descriptions and schemas cost roughly 825 tokens of context every time the server is loaded.

Is the io.github.ExpertVagabond/mega MCP server still maintained?

io.github.ExpertVagabond/mega is still listed as active in the MCP registry. We last reached this channel on 21 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 io.github.ExpertVagabond/mega MCP server under?

io.github.ExpertVagabond/mega 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 io.github.ExpertVagabond/mega MCP server?

VerifyMCP ran 16 checks on io.github.ExpertVagabond/mega, 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.