psr-factory-mcp@0.7.0
VERIFIED· not startedPublisher claims: "MCP server that exposes PSR tools to Claude Code" 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-15 and scored it 88/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
Sends a hard kill (SIGKILL / TerminateProcess) to the child executable.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return f"TOOL_ERROR kill_run: could not kill process — {exc}"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# store the process object in _jobs and kill it on demand via kill_run.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.**Goal:** Combine generation (gerter.csv) and marginal cost (cmo.csv) to computeFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.# Append kill marker to the execution log so the log tells the full story.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.# Use Popen so we can track and kill the process from kill_run.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run([exe, "ver"], **kwargs)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# Additionally, we switch from subprocess.call (opaque) to Popen so we canFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out."Send a hard kill to the PSR executable running under the given job_id. "Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.Comprehensive PSR/SDDP analyst workflow guide — always use this skill forFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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 psr-factory-mcp@0.7.0 as of 22 min ago. This is the package itself, not its dependencies.