co.yungle/yungle — Watchlist

MCP100 Assessment

Watchlist / Tracking

Why we’re tracking it

Monitor identity continuity, MCP tool inventory, permissions and adoption.

Reviewed Oct 10, 2026 · Documentation review; complete setup workflow not independently tested

Best fit

Yungle file transfer and download/share tracking through MCP

What we know

Yungle file transfer and download/share tracking through MCP. Published by the owner of npm package yungle-mcp. Ask about your Yungle file deliveries — what was sent, who downloaded, what expires. Read-only.

Maintenance / activity evidence

1386 npm downloads, 2026-09-09 to 2026-10-08

Tracking evidence observed Oct 10, 2026. These dated signals do not establish current maintenance. Reviewed enrichment confidence: high_for_identity_and_metrics_medium_for_verified_package_description.

Verification gaps / watch-outs

Installation and comprehensive security have not been independently audited.
File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations. Reported action classes: Create/manage file shares. Complete write authority is not verified.
Yungle API key or one-click auth
Sensitive access: Service account information and data accessible by supplied credentials

File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

Full authority, access and evidence limits are available in Review context and Access & risk.

Popularity

· 1.4k package downloads / 30 days

Downloads observed Oct 10, 2026.

Exact npm package yungle-mcp; provider interval 2026-09-09–2026-10-08 (inclusive); observed 2026-10-10T04:43:53Z.

All limitations / Review context

Has yungle-mcp changed publishing identity, permissions, install requirements, or risk exposure?

Published package documentation reviewed; public listing with prominently disclosed risks: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.

File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.
Public listing suitability does not imply safe installation or entitlement to access third-party accounts.
Yungle API key or one-click auth
Reviewed write actions: Create/manage file shares
Sensitive access: Service account information and data accessible by supplied credentials
Complete write authority is not verified.
Installation, client compatibility and comprehensive security have not been independently audited. Authentication and access depend on the configured services.
Respect upstream entitlements, version constraints and least-privilege setup.
Write actions/tool inventory not confirmed against exact tool documentation; listed action classes remain illustrative or context-dependent. Empty inventory does not establish read-only.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Original activity observations

1386 npm downloads, 2026-09-09 to 2026-10-08

Technical identity

npm/yungle-mcp

Exact implementation source: https://www.npmjs.com/package/yungle-mcp ↗
Reviewed resource type: MCP Server
Package identity: npm:yungle-mcp

Evidence & Sources

Evidence basis: Recorded source evidence
Setup runtime verification: Not independently runtime-tested by MCP100 for this setup workflow.

Reviewed Oct 10, 2026 · Latest source observation Oct 10, 2026

Registry source ↗
registry.modelcontextprotocol.io/v0/servers
Source material retained for this review.
Package registry ↗
yungle-mcp
Recorded package identity, distribution or download evidence.

Setup · Watchlist

Install & Agents

Publisher instructions.

Source evidence observed Oct 14, 2026.

Additional setup details required — see the specific gaps below.

Install / connect
Publisher instructions
Publisher-documented package/connection route; replace placeholders and verify host-specific syntax.
Publisher setup example · Publisher instructions
npm install -g yungle-cli; yungle mcp install
Configure / authenticate
MCP100 setup guide
Publisher Yungle CLI installs MCP definition across supported hosts; remote OAuth alternative needs no local install.
Use correct transport and published host config. Never paste secrets in chat; server registration is separate from software installation.
Check connection
Suggested check
Confirm authorization and list/import status with read-only tools.
Remove / uninstall / revoke
MCP100 setup guide
If registered as `yungle-mcp` in Claude Code, remove its exact client entry with `claude mcp remove yungle-mcp`; for Cursor/Claude Desktop/Codex, remove the matching MCP entry in that host settings. This client removal is MCP100-composed, not a vendor uninstall instruction. Npx does not imply a global install; do not delete user data or revoke credentials implicitly. For an explicitly globally installed package (not npx-only), npm uninstall -g yungle-cli.
Conditional host / package cleanup · Claude Code only · MCP100 composed guide
claude mcp remove yungle-mcp

Official Documentation & Sources

What it does

Yungle file transfer and download/share tracking through MCP. Published by the owner of npm package yungle-mcp. Ask about your Yungle file deliveries — what was sent, who downloaded, what expires. Read-only.

Capability: Files & Knowledge
Resource type: MCP Server
Best fit: Yungle file transfer and download/share tracking through MCP

Representative uses

Yungle file transfer and download/share tracking through MCP

Limitations

File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.
Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes.
Public exact-package npm downloads observed for recent 30-day window.

Reviewed access

Access & risk

Review the exact access boundary before connecting this MCP to accounts, credentials, or sensitive data.

Authentication: Yungle API key or one-click auth
Permissions: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.
Data handling: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.
Cost: Credit/subscription costs may apply; inspect provider docs
Risk and cautions: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.

Access scope and cautions

Write actions: Not verified Create/manage file shares
Sensitive access: Service account information and data accessible by supplied credentials
Risk level: high
Security notes: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations. Public listing suitability does not imply safe installation or entitlement to access third-party accounts.

The reviewed evidence does not establish the complete write authority of this MCP. Consult the unresolved evidence before granting write access.

FAQ

Based on reviewed evidence as of 2026-10-10T04:43:53Z. Watchlist tracking is not a recommendation or a security certification.

What setup and authentication are documented?

A complete connection procedure is not verified. Client notes: Do not infer shell entrypoint or automated credential setup if a command is not explicitly verified. These facts do not supply missing installation commands, credentials or a verified authentication procedure. Authentication: Yungle API key or one-click auth

Can it modify data or perform write operations?

Not verified. The available evidence does not establish the complete write authority. The partial inventory lists: Create/manage file shares. Recorded permission context: File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations.

What data-handling boundary should I consider?

File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations. Recorded sensitive-access context: Service account information and data accessible by supplied credentials.

What limitations and risks should I check before use?

File-delivery data, sharing operations and download recipient history may be sensitive; require confirmation for share mutations. Publicly documented capabilities are not a guarantee of a safe deployment; review third-party data processing and access scopes. Public exact-package npm downloads observed for recent 30-day window. Public listing suitability does not imply safe installation or entitlement to access third-party accounts. Respect upstream entitlements, version constraints and least-privilege setup.

What cost model is recorded?

The reviewed cost model is Credit/subscription costs may apply; inspect provider docs. This classification does not establish current prices, quotas or the cost of every downstream operation. Check the applicable service terms before authorizing paid actions.