alibabacloud-devops-mcp-server@0.3.69
VERIFIED· startup onlyPublisher claims: "MCP Server for using the alibabacloud-devops API: allows AI assistants to directly participate in development collaboration, helping teams optimize development processes and improve efficiency." Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
MCP_AUTH_CHECKYUNXIAO_ACCESS_TOKENConfiguration, not credentials: DEVOPS_TOOLSETS, LOG_DEST, MCP_ALLOWED_HOSTS, MCP_CLUSTER, MCP_CLUSTER_WORKERS, MCP_HTTP_HOST, MCP_JSON_BODY_LIMIT, MCP_SSE_MESSAGES_PATH, MCP_SSE_PATH, MCP_STATELESS, MCP_STREAMABLE_PATH, MCP_TRANSPORT, YUNXIAO_ALLOW_REQUEST_API_BASE_URL, YUNXIAO_API_BASE_URL, YUNXIAO_EDITION, YUNXIAO_REGION_DEFAULT_ORG_ID- Where it talks to
- no vendor host named in the codeAlso aliyun.com, placeholder.local, aliyuncs.com — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names aliyun.com, placeholder.local, aliyuncs.com as well as its own vendor. The guard injects MCP_AUTH_CHECK, YUNXIAO_ACCESS_TOKEN only into requests to the host you bind (and its subdomains) and refuses the rest.
Never paste a credential into a chat, a ticket or a report, including ours. How the guard holds it.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios; startup only; authenticated tool behavior not tested) on 2026-11-14 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 · 28 s · 2 scenarios · 0 deviationsStatic findings
"build": "rm -rf dist && tsc && chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.// 攻击者可传 /etc/passwd、密钥等敏感路径，让 server 读取并上传，造成任意文件读取/数据外泄。Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.The personal token authorization pageFix: 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 alibabacloud-devops-mcp-server@0.3.69 as of 7d ago. This is the package itself, not its dependencies.