zadig-workflow-mcp@0.1.17
VERIFIED· install onlyPublisher claims: "A local MCP server for browsing, building and releasing Zadig product workflows" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Bundled scripts ran with no arguments; no agent task scenario for this bundle.- Tested
- 3 of 3 bundled scripts run with no arguments, with decoy credentials in the environment · every file read, file written and host contacted by what ran
- Not tested
- use of the skill by an agent
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
ZADIG_API_TOKENConfiguration, not credentials: CLAUDE_CONFIG_DIR, CODEX_HOME- Where it talks to
- no vendor host named in the codeAlso tec-develop.cn, tec-develop.com — not the publisher's domain; check what for before connecting.
- What we saw when it ran
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names tec-develop.cn, tec-develop.com as well as its own vendor. The guard injects ZADIG_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; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-21 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
result = subprocess.run([executable, "--version"], capture_output=True, text=True, timeout=10, check=False)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.No other findings across 1,365 lines in 4 files.
Cost to the agent
Tokens estimated at four characters each. Skills load their instruction text when triggered; the figure is what that costs.
Known vulnerabilities
No advisories in OSV for zadig-workflow-mcp@0.1.17 as of 3 h ago. This is the package itself, not its dependencies.