snodo-mcp@0.28.3
VERIFIED· install onlyPublisher claims: "Snodo MCP — MCP servers, planning, recon, and jobs" 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
- install scripts, with decoy credentials in place · second launch with the clock 45 days ahead · 8 of 27 bundled scripts run with no arguments (the rest were not run: per-bundle cap), 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
- no credential variables read in the code
- Where it talks to
- no vendor host named in the codeAlso adaptivecards.io — not the publisher's domain; check what for before connecting.
- What the honeypot saw
- no credential files read · no network
- What we could not test
- use of the skill by an agent
Connect it under the guard. Bundled scripts ran with no arguments; no agent task scenario for this bundle. 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.
What changed since 0.27.0
vet-skills diff snodo-mcp 0.27.0 0.28.3In the sandbox, this version reached for nothing 0.27.0 did not. Compared from the two recorded runs, not from source.
The guard can hold an update like this until someone approves it (runtime.on_change: hold). A change that only shows with a real credential, or on a path the run did not reach, is not in a trace and so not in this comparison.
Is [email protected] safe to install?
KillerSkills ran it in the KillerSkills honeypot sandbox (3 scenarios; bundled scripts ran with no arguments; no agent task scenario for this bundle) on 2026-11-18 and scored it 81/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 · 1 s · 3 scenarios · 0 deviationsStatic findings
$("logs").textContent = logs.log || "(no stdout output)";Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.snodo-guide topic="following-a-run" aliases="run,follow-run" summary="Follow an asynchronous job live" section="# Following a run"Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.snodo-guide topic="queues" summary="Validate and run queues" section="# Keep queues moving"Fix: Keep SKILL.md to visible, descriptive text. Remove comments and encoded text that address the agent.subprocess.Popen( # noqa: S603 - fixed module and argv, no shellFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.Popen( # noqa: S603 - argv list (no shell) from build_command; task description/model are single argv elements, never interpretedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.result = subprocess.run( # noqa: S603 - fixed argv, project path passed as one argumentFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(cmd, check=False) # noqa: S603 - argv list (no shell); argv are single CLI elements from the job's task spec, never shell-interpretedFix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.…xtContent=s.status||"unknown";document.querySelector("#logs").textContent=d.logs.log||"(no stdout output)";const began=Number(s.started_at||s.created_at)*1000;const end=Number(s.comple…Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.except Exception as e: # noqa: BLE001 — an observer must not kill its subjectFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.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 snodo-mcp@0.28.3 as of 48 min ago. This is the package itself, not its dependencies.