Skills/PyPI/zadig-workflow-mcp

zadig-workflow-mcp@0.1.17

VERIFIED· install only

Publisher 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.

Registry PyPI (MCP server)Publisher pypi · publishing for 730 daysInstalls 902Last detonated 3 h ago
$claude mcp add zadig-workflow-mcp -- uvx zadig-workflow-mcp
WatchReport an issue

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.

$vet-skills run --net declared -- uvx zadig-workflow-mcp

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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
0.0sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.1sprocessexited 1: ModuleNotFoundError: No module named 'httpx'
0.1sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.2sprocessexited 1: ModuleNotFoundError: No module named 'tomlkit'
0.2sprocessbundled script run in the sandbox with no arguments · not named in the instructions
0.4sprocessexited 1: ModuleNotFoundError: No module named 'httpx'
0.4sprocess3 of 3 bundled scripts run with no arguments
0.4sprocessscript backend runs setup only
0.4sprocessscript backend runs setup only
0.4sprocessno install scripts to re-run

Static findings

MEDIUM
Python subprocess execution detectedzadig_install.py:93 · Python subprocess execution detectedresult = 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.
AST05

No other findings across 1,365 lines in 4 files.

Cost to the agent

Instructions loaded
≈60 tok
1 file · 4 in bundle

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.