io.github.ExpertVagabond/mega
NPM · MEGA-MCP-SERVER · SCANNED SEP 22
MEGA cloud storage CLI MCP server
Available components
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 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL redirects; it must resolve directly. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 219 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
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 Management83
- Stability observed for 25 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 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
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
claude mcp add expertvagabond-mega -- npx -y mega-mcp-server
{
"mcpServers": {
"expertvagabond-mega": {
"command": "npx",
"args": [
"-y",
"mega-mcp-server"
]
}
}
} {
"servers": {
"expertvagabond-mega": {
"command": "npx",
"args": [
"-y",
"mega-mcp-server"
]
}
}
} codex mcp add expertvagabond-mega -- npx -y mega-mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"expertvagabond-mega": {
"type": "local",
"command": [
"npx",
"-y",
"mega-mcp-server"
],
"enabled": true
}
}
} openclaw mcp add expertvagabond-mega --command npx --arg -y --arg mega-mcp-server
mcp_servers:
expertvagabond-mega:
command: "npx"
args: ["-y", "mega-mcp-server"] {
"McpServers": {
"expertvagabond-mega": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"mega-mcp-server"
]
}
}
} assistant mcp add expertvagabond-mega -t stdio -c npx -a -y mega-mcp-server
{
"mcpServers": {
"expertvagabond-mega": {
"command": "npx",
"args": [
"-y",
"mega-mcp-server"
]
}
}
} 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.
- 22 Sept 26 −2
- Stability: pass → 0.83 functional
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 19 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 0
- Security disclosure: unverified → fail ▼ functional
- 17 Sept 26 +1
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
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 22 Sept 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 95 packages
| Packages resolved | 95 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
mega_cat ~27
Display contents of a remote file
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Remote file path to display |
No output schema declared.
No examples provided.
mega_cd ~29
Change current working directory in MEGA cloud
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | yes | Remote path to change to |
No output schema declared.
No examples provided.
mega_cp ~38
Copy files/folders within MEGA cloud storage
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination remote path |
| source | string | yes | Source remote path |
No output schema declared.
No examples provided.
mega_df ~29
Show MEGA cloud storage space usage
| Name | Type | Req | Description |
|---|---|---|---|
| human | boolean | – | Show sizes in human-readable format |
No output schema declared.
No examples provided.
mega_du ~39
Show disk usage of remote path
| Name | Type | Req | Description |
|---|---|---|---|
| human | boolean | – | Show sizes in human-readable format |
| path | string | – | Remote path to check |
No output schema declared.
No examples provided.
mega_export ~65
Create a public link for a file/folder
| Name | Type | Req | Description |
|---|---|---|---|
| expire | string | – | Expiration time (e.g., '1d', '1w', '1m') |
| password | string | – | Password protect the link |
| path | string | yes | Remote path to export |
No output schema declared.
No examples provided.
mega_find ~47
Search for files/folders in MEGA cloud storage
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Path to search in (default: /) |
| pattern | string | yes | Search pattern (supports wildcards) |
No output schema declared.
No examples provided.
mega_get ~49
Download files from MEGA cloud to local filesystem
| Name | Type | Req | Description |
|---|---|---|---|
| local_path | string | – | Local destination path (default: current directory) |
| remote_path | string | yes | Remote path in MEGA to download |
No output schema declared.
No examples provided.
mega_import ~45
Import a public MEGA link to your account
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | MEGA public link to import |
| remote_path | string | – | Destination path in your MEGA |
No output schema declared.
No examples provided.
mega_ls ~57
List files and folders in MEGA cloud storage
| Name | Type | Req | Description |
|---|---|---|---|
| long | boolean | – | Show detailed listing with sizes and dates |
| path | string | – | Remote path to list (default: current directory) |
| recursive | boolean | – | List recursively |
No output schema declared.
No examples provided.
mega_mkdir ~42
Create a directory in MEGA cloud storage
| Name | Type | Req | Description |
|---|---|---|---|
| parents | boolean | – | Create parent directories as needed |
| path | string | yes | Remote path for new directory |
No output schema declared.
No examples provided.
mega_mv ~40
Move or rename files/folders in MEGA cloud storage
| Name | Type | Req | Description |
|---|---|---|---|
| destination | string | yes | Destination remote path |
| source | string | yes | Source remote path |
No output schema declared.
No examples provided.
mega_put ~47
Upload files from local filesystem to MEGA cloud
| Name | Type | Req | Description |
|---|---|---|---|
| local_path | string | yes | Local file/folder path to upload |
| remote_path | string | – | 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
| Name | Type | Req | Description |
|---|---|---|---|
| force | boolean | – | Force removal without confirmation |
| path | string | yes | Remote path to remove |
| recursive | boolean | – | Remove directories recursively |
No output schema declared.
No examples provided.
mega_share ~72
Share a folder with another MEGA user
| Name | Type | Req | Description |
|---|---|---|---|
| access_level | string | – | Access level: 'r' (read), 'rw' (read-write), 'full' (full access) |
| string | yes | Email of user to share with | |
| path | string | yes | Remote folder path to share |
No output schema declared.
No examples provided.
mega_sync ~59
Set up sync between local and remote folders
| Name | Type | Req | Description |
|---|---|---|---|
| list_only | boolean | – | Just list current syncs instead of creating new one |
| local_path | string | – | Local folder path |
| remote_path | string | – | Remote MEGA folder path |
No output schema declared.
No examples provided.
mega_transfers ~28
Show current transfers (uploads/downloads)
| Name | Type | Req | Description |
|---|---|---|---|
| show_completed | boolean | – | Include completed transfers |
No output schema declared.
No examples provided.
mega_tree ~26
Show directory tree structure
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | 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.
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 74 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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.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 22 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.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.