Skills/PyPI/iflow-mcp-dabaigoose-mcp-wechat-adb-server

iflow-mcp-dabaigoose-mcp-wechat-adb-server@0.1.1

CAUTION

Publisher claims: "A MCP Server for WeChat automation via ADB, supporting message sending and screenshot capture" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry PyPI (MCP server)Publisher your-username · joined 7 days agoInstalls 28Last detonated 16 h ago
What would fix thisWatchDispute verdict

Is [email protected] safe to install?

KillerSkills ran it in the KillerSkills honeypot sandbox (2 scenarios) on 2026-11-02 and scored it 74/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: OS command execution function call detected. Summary: no network, touches nothing outside the project, writes no memory.

Behavior trace

Honeypot run · 0 s · 2 scenarios · 0 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.4sprocessdependency install exit 1
0.4sprocessexec /usr/bin/timeout
0.4sprocessexec .venv/bin/wechat-adb-server
0.4sprocessexited 127: timeout: failed to run command '.venv/bin/wechat-adb-server': No such file or directory
0.4sclaimedno tools/list reply (exit 127)
0.4sprocessscript backend runs setup only

Static findings

CRITICAL
OS command execution function call detectedadb_utils.py:480 · OS command execution function call detectedFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Python subprocess execution detectedadb_utils.py:63 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05
MEDIUM
Python subprocess execution detectedadb_utils.py:530 · Python subprocess execution detectedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
AST05

What would make this Verified

6 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%
  1. OS command execution function call detected≈ +9 on the totalBuild commands from fixed arguments; do not interpolate untrusted strings into a shell.
  2. Unclaimed publisher≈ +8 on the totalClaim your-username: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
  3. Does not do what the description says≈ +5 on the totalIn the sandbox the skill never performed the task it claims (no call to the service it is for). Make sure the happy path runs without extra setup, or describe the real behavior.
  4. New publisher≈ +3 on the totalTime clears this on its own after 14 and 30 days. Claiming the handle (+50) is the fastest way past it.
  5. Python subprocess execution detected≈ +2 on the totalBuild commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.
Publish a new version to PyPI, then queue it here. Not your skill? Claim the handle to get verdict changes by email.Claim your-username