phionyx-pipeline-mcp@0.3.2
VERIFIED· not startedPublisher claims: "Phionyx self-governance gate for Claude Code — three-layer verification (LLM declaration → git diff truth → deterministic gate) over the agent's own 'fixed / tested / changed' claims. v0.3.0 adds opt-in evidence binding: the require_tool directive (a factual claim without same-turn evidence must bind a tool first) and continuity binding (catches 'read-but-not-bound'). Both default-OFF / non-regressive; detector calibration is not yet validated." 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the code
- What the honeypot saw
- no credential files read · no network
- What we could not test
- server startup · the tool list · tool behavior
Connect it under the guard. Not started: dependency install failed; the server itself was not observed. The code names no credential variable; the guard pins the network to what the honeypot saw and logs every call.
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-14 and scored it 85/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
staged = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.recs.append(_rec(f"escalation-{n}", m.group(1), ".claude/CLAUDE.md#escalation", ts))Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.recs.append(_rec(f"forbidden-{m.group(1)}", m.group(2), ".claude/CLAUDE.md#forbidden", ts))Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.("no_secrets", re.compile(r"\.env\b|API[_ ]?key|secret|token|credential", re.I)),Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out._ARTIFACT_BLACKLIST = {"README.md", "node_modules", "package.json", "/path/to", "/etc/passwd"}Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.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 phionyx-pipeline-mcp@0.3.2 as of 2 h ago. This is the package itself, not its dependencies.