mcp-switchboard-server-harness@0.4.0.dev6
VERIFIED· not startedPublisher claims: "A stdio MCP server exposing filesystem, git and shell tools for coding agents" 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-10 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
elapsed_s: Optional[float] = Field(default=None, description="Seconds from start to the kill (or exit).")Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.…t (pytest config or tests/), `go test -json ./...` (go.mod), `npm test` (package.json test script) or `cargo test`. Pass command to run something else (pytest and go test output is still parsed). changed_only=true runs ONLY the tests git s…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.subprocess.run(["git", "init", "-q"], cwd=tmp_path, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# The kill and the wait must happen while the loop runs: reaping theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(["git", *cmd], cwd=path, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(["git", "init", "--bare", str(origin)], check=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.description="True when the command was killed at the applied timeout; stdout/stderr are then everything it produced up to the kill and exit_code is the sentinel 124.",Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(["git", "add", "."], cwd=tmp_path, check=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.# hub deadline can kill a wait, and a 24 h watch costs one subprocess per poll.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.proc = subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.so no hub per-call deadline can kill a wait.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.subprocess.run(["git", "clone", str(origin), str(work)], check=True, capture_output=True)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.f"too many background processes and watches ({MAX_PROCESSES}); kill one first"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.return subprocess.run(["python", "-c", "import pytest"], capture_output=True).returncode == 0Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…tch and return its id at once — nothing blocks, so no hub per-call deadline can kill a long wait. The shell predicate `until` (via bash -c) is re-run every `poll` se…Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 mcp-switchboard-server-harness@0.4.0.dev6 as of 5d ago. This is the package itself, not its dependencies.