yuque-mcp@1.1.0
VERIFIED· not startedPublisher claims: "MCP server for Yuque (语雀) — expose Yuque knowledge base to AI assistants via Model Context Protocol" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Not started: dependency install failed; the server itself was not observed.- Tested
- the dependency install step · every file read, file written and host contacted by what ran
- Not tested
- server startup · the tool list · tool behavior
What this means for the label: Verified here covers what ran. The server's tools were not exercised with a real credential, so nothing about their behavior is asserted; the credential summary below says what to do with that.
Before you give it your token
- It will ask for
YUQUE_PERSONAL_TOKENYUQUE_TOKENConfiguration, not credentials: YUQUE_BASE_URL, YUQUE_HOST- Where it talks to
- yuque.com (its own)
- What we saw when it ran
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard. It asks for YUQUE_PERSONAL_TOKEN, YUQUE_TOKEN and talks to yuque.com. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
What changed since 1.0.0
vet-skills diff yuque-mcp 1.0.0 1.1.0This version reaches for something 1.0.0 did not: 1 new credential variable (YUQUE_TOKEN). Compared from the two recorded runs, not from source.
- New credential variables
- YUQUE_TOKEN
1.0.0 was not run in the sandbox (install failed); the comparison covers what static analysis recorded only.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; not started: dependency install failed; the server itself was not observed) on 2026-11-21 and scored it 84/100 (Verified). In what ran, nothing we could detect went wrong: no undeclared network egress, no credential reads, no persistent instruction writes. What it does with a real credential was not observed; the static findings and the publisher carry the rest of the score. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 13 s · 2 scenarios · 0 deviationsStatic findings
<summary><b>Claude Code</b></summary> 直接注册 server: ```bash claude mcp add yuque -- npx -y yuque-mcp --token=YOUR_TOKEN ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary>Migrating from an older config?</summary> `YUQUE_PERSONAL_TOKEN`, `YUQUE_BASE_URL`, and `--base-url` still work as legacy fallbacks. Precedence: `YUQUEFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary><b>Claude Code</b></summary> Register the server directly: ```bash claude mcp add yuque -- npx -y yuque-mcp --token=YOUR_TOKEN ```Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct."build": "tsc && chmod +x dist/cli.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.npx yuque-mcp setupFix: Pin versions and sources; vendor anything fetched at install time.npx yuque-mcp install --client=vscode --token=YOUR_TOKENFix: Pin versions and sources; vendor anything fetched at install time.npx yuque-mcp install --client=cursor --token=YOUR_TOKENFix: Pin versions and sources; vendor anything fetched at install time.console.error('Usage: npx yuque-mcp install --token=YOUR_TOKEN --client=CLIENT [--host=HOST]');Fix: Pin versions and sources; vendor anything fetched at install time.console.error('Usage: npx yuque-mcp install --token=YOUR_TOKEN --client=CLIENT [--host=HOST]');Fix: Pin versions and sources; vendor anything fetched at install time.<summary>从旧配置迁移?</summary> `YUQUE_PERSONAL_TOKEN`、`YUQUE_BASE_URL` 和 `--base-url` 仍作为兼容 fallback 生效。优先级:`YUQUE_TOKEN` > `YUQUE_PERSONAL_TOKEN` > `--token`;`YUQUFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.Cost to the agent
Tokens estimated at four characters each. The tool list is re-read by the agent on every turn, so it is the number to compare between servers that do the same job: ranked across the index.
Known vulnerabilities
No advisories in OSV for yuque-mcp@1.1.0 as of 26 min ago. This is the package itself, not its dependencies.