room-stu-fault-mcp@0.1.5
VERIFIED· not startedPublisher claims: "教室故障排查 MCP:教室日志、网络信息、教室工单、千问诊断" 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
ALIBABA_CLOUD_ACCESS_KEY_IDALIBABA_CLOUD_ACCESS_KEY_SECRETDASHSCOPE_API_KEYNETWORK_API_TOKENTICKET_API_TOKENConfiguration, not credentials: ALIYUN_SLS_ENDPOINT, ALIYUN_SLS_PROJECT, ALIYUN_SLS_TOPIC_ALL_CLIENTS, ALIYUN_SLS_TOPIC_ANDROID, ALIYUN_SLS_TOPIC_IOS, ALIYUN_SLS_TOPIC_JS, NETWORK_API_PATH, NETWORK_API_URL, QWEN_API_BASE, QWEN_MODEL, TICKET_API_PATH, TICKET_API_URL- Where it talks to
- no vendor host named in the codeAlso 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names aliyuncs.com as well as its own vendor. The guard injects ALIBABA_CLOUD_ACCESS_KEY_ID, ALIBABA_CLOUD_ACCESS_KEY_SECRET, DASHSCOPE_API_KEY, NETWORK_API_TOKEN, TICKET_API_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; not started: dependency install failed; the server itself was not observed) on 2026-11-16 and scored it 93/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 · 0 s · 2 scenarios · 0 deviationsStatic findings
No findings across 2,096 lines in 16 files.
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
Not checked against OSV yet; the weekly check has not reached this version.