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.MrLinWang/aliyun-yunxiao-projex-mcp

PYPI · YUNXIAO-PROJEX-MCP

Alibaba Cloud Yunxiao Projex MCP with authenticated file downloads.

Available components

0 Trust /100

Last scanned (5 hours ago)

Scores higher than 0% of PyPI servers

Category Project Management

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 Security25
  • Malware scan not yet available for this package.Unverified
  • CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 62 of 64 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability0
  • Schema quality not yet verified: our sandbox could not run this package, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: our sandbox could not run this package, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: our sandbox could not run this package, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: our sandbox could not run this package, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: our sandbox could not run this package, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox could not run this package, so we have no schema for these checks to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until we can run it. How we score packages →

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.

  • 5 Nov 26 0
    • Malware scan: pass → unverified ▼ security
  • 4 Nov 26 0

    First indexed and scored.

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 5 Nov 2026 · Analysed pypi/yunxiao-projex-mcp@0.1.0

Provenance No attestation

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

Result No attestation
Ecosystem pypi
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Vulnerabilities 13 findings
ID CVE Severity Vector Fix available
GHSA-537c-gmf6-5ccf high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-g6cj-pr64-35w5 CVE-2026-69247 high yes
GHSA-jwv3-5hgf-82ww CVE-2026-69249 high yes
GHSA-m2h6-j472-rp4c CVE-2026-69248 medium yes
GHSA-m959-cc7f-wv43 CVE-2026-34073 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
GHSA-p423-j2cm-9vmq CVE-2026-39892 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes
GHSA-r6ph-v2qm-q3c2 CVE-2026-26007 high yes
PYSEC-2026-2141 CVE-2026-26007 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:R/S:U/C:H/I:N/A:N yes
PYSEC-2026-35 CVE-2026-34073 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:L/A:N yes
PYSEC-2026-3552 CVE-2026-69247 none yes
PYSEC-2026-3553 CVE-2026-69249 none yes
PYSEC-2026-3554 CVE-2026-69248 none yes
PYSEC-2026-36 CVE-2026-39892 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:H/I:H/A:H yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 62 packages
Packages resolved 62
Stale 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools

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 →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.MrLinWang/aliyun-yunxiao-projex-mcp server?

io.github.MrLinWang/aliyun-yunxiao-projex-mcp runs locally as a PyPI package, launched with uvx yunxiao-projex-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · yunxiao-projex-mcp

# add to Claude Code
claude mcp add mrlinwang-aliyun-yunxiao-projex-mcp -- uvx yunxiao-projex-mcp
Common questions

What is the io.github.MrLinWang/aliyun-yunxiao-projex-mcp server?

io.github.MrLinWang/aliyun-yunxiao-projex-mcp is listed in the public MCP registry as io.github.MrLinWang/aliyun-yunxiao-projex-mcp. Alibaba Cloud Yunxiao Projex MCP with authenticated file downloads. This page covers its PyPI package (yunxiao-projex-mcp).

Is the io.github.MrLinWang/aliyun-yunxiao-projex-mcp server still maintained?

io.github.MrLinWang/aliyun-yunxiao-projex-mcp is still listed as active in the MCP registry. We last reached this channel on 5 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.MrLinWang/aliyun-yunxiao-projex-mcp server under?

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