co.yungle/yungle
NPM · YUNGLE-MCP · 2 COMPONENTS · SCANNED SEP 29
Ask about your Yungle transfers, share big files, download what you're sent. Approve every send.
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 Security48
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 94 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to heindewilde/yungle-clients). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1345 tokens (~89/item across 15 items; 15 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management10
- Stability observed for 3 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 60% of tool parameters carry a description.Partial
Tool Safety83
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_transfer" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 16 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 co.yungle/yungle MCP server?
co.yungle/yungle runs locally as an npm package, launched with npx -y yungle-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 · yungle-mcp
claude mcp add co-yungle-yungle -- npx -y yungle-mcp
{
"mcpServers": {
"co-yungle-yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp"
]
}
}
} {
"servers": {
"co-yungle-yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp"
]
}
}
} codex mcp add co-yungle-yungle -- npx -y yungle-mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"co-yungle-yungle": {
"type": "local",
"command": [
"npx",
"-y",
"yungle-mcp"
],
"enabled": true
}
}
} openclaw mcp add co-yungle-yungle --command npx --arg -y --arg yungle-mcp
mcp_servers:
co-yungle-yungle:
command: "npx"
args: ["-y", "yungle-mcp"] {
"McpServers": {
"co-yungle-yungle": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"yungle-mcp"
]
}
}
} assistant mcp add co-yungle-yungle -t stdio -c npx -a -y yungle-mcp
{
"mcpServers": {
"co-yungle-yungle": {
"command": "npx",
"args": [
"-y",
"yungle-mcp"
]
}
}
} 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.
- 29 Sept 26 −13
- Malware scan: pass → unverified ▼ security
- Schema quality: 72 → 89 ▼ functional
- Tool coverage: 20% → 60% ▲ functional
- Stability: unverified → 0.10 ▲ functional
- Package version: 0.2.4 → 0.3.0 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +40
- Known CVEs: pass → unverified ▼ security
- Injection markers: unverified → pass ▲ security
- Provenance: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- The attested source repository moved: heindewilde/yungle-clients security
- Dependency health: 0.85 → unverified ▼ functional
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: excellent functional
- First check of Tool coverage: 20 functional
- First check of Schema quality: pass functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: 33 functional
- Package version: 0.1.2 → 0.2.4 functional
- Package version: 0.1.2 → 0.2.3 functional
- Package version: 0.1.2 → 0.2.0 functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 8 Aug 26 0
- Known CVEs: partial → pass ▲ security
- Dependency health: partial → 0.85 functional
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 29 Sept 2026 · Analysed npm/yungle-mcp@0.3.0
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 | heindewilde/yungle-clients |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/heindewilde/yungle-clients/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2997278016 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2197fffa0aaf08d8121712027155e6eb3d5e9a0aa812636828e5dcace08272d5fb4cca3d05bc3ecebd9b4a6a7879c71679be31c7c699c041bbb1a772e |
Background: How many MCP packages publish verified provenance →
Dependencies 94 packages
| Packages resolved | 94 |
|---|---|
| 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 →
create_transfer Prepare a transfer ~119
Prepare a draft transfer for files that live on a machine with a shell, and return one upload command per file. Each command (`npx -y yungle-cli put …`) needs no Yungle key: it carries a token that can write only that file, for two hours, and it resumes if interrupted. Nothing is shared and nobody is emailed until the transfer is finalized.
| Name | Type | Req | Description |
|---|---|---|---|
| expiresInDays | integer | – | – |
| files | array | yes | – |
| title | string | – | Label for the dashboard; never shown to recipients. |
No output schema declared.
No examples provided.
download_files Download files to this computer ~193
Save the files of a Yungle link, or of one of your own transfers or collections, into a folder on this machine — resumably, keeping their folder structure. Files land in a new subfolder of `directory`; nothing outside it is written, and files already there at full size are skipped. Returns the saved paths.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | – | The id of one of your own collections (when there is no link). |
| directory | string | yes | Absolute path of an existing folder to save into, e.g. ~/Downloads expanded. |
| password | string | – | For a password-protected link. |
| transferId | string | – | The id of one of your own transfers (when there is no link). |
| url | string | – | A Yungle link someone shared: https://yungle.co/t/… (transfer) or https://yungle.co/c/… (collection). |
No output schema declared.
No examples provided.
get_account Account and storage ~49
Answers: how much storage am I using? how much is left? what plan am I on? what can this connection do? Returns the workspace, its plan and quota, and the key's permissions.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_collection Collection detail ~53
Answers: what is the link for this collection? how much is in it? when does it expire? Returns one collection with its secret share link, file count, total size and expiry.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_download_links Download links ~218
Answers: what is in this link someone sent me? how do I get these files? Turns a Yungle link (https://yungle.co/t/… or /c/…), or one of your own transfers or collections, into signed download URLs: one per file, with its folder path, plus a ZIP. The URLs need no key, support HTTP Range (resumable), and work for 24 hours — fetch them with curl or any HTTP client. Resolving someone else's link counts as one download of it, like opening it in a browser.
| Name | Type | Req | Description |
|---|---|---|---|
| collectionId | string | – | The id of one of your own collections (when there is no link). |
| password | string | – | For a password-protected link. |
| transferId | string | – | The id of one of your own transfers (when there is no link). |
| url | string | – | A Yungle link someone shared: https://yungle.co/t/… (transfer) or https://yungle.co/c/… (collection). |
No output schema declared.
No examples provided.
get_transfer Transfer detail ~66
Answers: what is in this transfer? was it delivered? has a specific recipient downloaded it? is it safe to share? Returns the files with their malware-scan verdicts, plus per-recipient delivery and download status for one transfer id.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Transfer id. |
No output schema declared.
No examples provided.
get_transfer_downloads Download receipts ~61
Answers: did the client download it? when? how many times? Returns download events with timestamps and per-recipient status. One visit can fetch several files: events that share a sessionId belong to the same visit.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
get_upload_request Upload request detail ~55
Answers: who has uploaded through this link, when, and how much? Returns the request and its submissions, newest first, with the name, email and note each uploader typed.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Upload request id. |
No output schema declared.
No examples provided.
list_collection_files Files in a collection ~83
Answers: what files are in this collection? what is in this folder? are the raws uploaded yet? Returns filenames, sizes and types. Omit folderId for every file; pass "root" for the top level only, or a folder id. Filenames only — never file contents.
| Name | Type | Req | Description |
|---|---|---|---|
| folderId | string | – | – |
| id | string | yes | – |
No output schema declared.
No examples provided.
list_collections List collections ~75
Answers: what collections do I have? which are empty? how big is each one? Returns collections with file counts, sizes and when each was last touched. A collection is a durable space clients are invited into, as opposed to a one-off transfer. Never includes the vault, which is unreadable to this server by design.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_contacts Address book ~47
Answers: what is this client's email address? who do I have saved? Returns the workspace address book. A contact grants no access on its own — it is a convenience, not a permission.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_folders Folders in a collection ~57
Answers: how is this collection organised? what folders exist? Returns the folder tree. Ordered by depth, then path (not a pre-order traversal). Each folder carries its parentId and its full path.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_guests Guests on a collection ~60
Answers: who has access to this collection? who did I invite? has someone accepted? Returns the invited guests and their status. Guests are not workspace members — they can view and download this one collection and nothing else.
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | – |
No output schema declared.
No examples provided.
list_transfers List transfers ~54
Answers: what have I sent recently? what is expiring soon? which deliveries has nobody picked up? who did I send that to? Returns recent transfers with size, recipients, download count, expiry date and share link.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_upload_requests Upload requests ~47
Answers: which upload links do I have out? has anyone sent files through them? Returns each public upload page that feeds a collection, with its link, status and how much has arrived.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
What is the co.yungle/yungle MCP server?
co.yungle/yungle is an MCP server listed in the public MCP registry as co.yungle/yungle. Ask about your Yungle transfers, share big files, download what you're sent. Approve every send. This page covers its npm package (yungle-mcp).
Is the co.yungle/yungle MCP server safe to use?
co.yungle/yungle scores 65 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 29 September 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 co.yungle/yungle MCP server expose?
co.yungle/yungle exposes 15 tools: get_account, list_transfers, get_transfer, get_transfer_downloads, list_collections, and 10 more. Their descriptions and schemas cost roughly 1,237 tokens of context every time the server is loaded.
Is the co.yungle/yungle MCP server still maintained?
co.yungle/yungle is still listed as active in the MCP registry. We last reached this channel on 29 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 co.yungle/yungle MCP server under?
co.yungle/yungle declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.