tmodloader-mcp@0.7.1
VERIFIED· not startedPublisher claims: "Drive a running tModLoader instance: launch it, ask it questions, photograph it, and read its state back." 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 we saw when it ran
- 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-19 and scored it 80/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 · 2 scenarios · 0 deviationsStatic findings
proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.done = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.proc = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(_client_join_cmd(cfg, PORT_B, PLAYER_B), **spawn)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.subprocess.Popen(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.<summary><code>TMODLOADER_MOD_NAME</code> — when the derived name is wrong, and what the name keeps apart</summary> `TMODLOADER_MOD_NAME` is the mod's **internaFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.#: FILETIME. The creation time is what pins a kill to the PROCESS rather thanFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`unkillable` is how a kill that does not take is expressed: taskkill stillFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.bad = await session.call_tool("read_capture", {"name": "../../../etc/passwd"})Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.A teardown-on-failure that also fired on success would kill the game theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."../../../etc/passwd",Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.logs.read_since(tmp_path, "../../etc/passwd", offset=0)Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.#: finished, so a restore that dies partway - a /mnt/c lock, a kill - is onFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.old pid-only behaviour rather than refusing to kill what this sessionFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.result = subprocess.run(Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.signals. And a teardown must kill ONLY what this session started: a developerFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.`capture://../../../etc/passwd` fails to match the URI template and comesFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.for escape in ["../../secrets.log", "Old/2026-07-29-4.zip", "/etc/passwd"]:Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose._write(tml, "client.log", "a long first run with plenty of output\n")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why."""`Path(dir) / "/etc/passwd"` is `/etc/passwd` — joining does not containFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.(tmp_path / f"{stem}-server.txt").write_text("hooks-seen: PostUpdateWorld\n")Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.# `stop` will later kill it. The creation stamps recorded beside the pidsFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."""A process table a kill can actually change.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.THIS form goes on to act on the answer - refuse a launch, kill a pid,Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.kill was aimed at. If any survive, this FAILS rather than answering with aFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell."capture://../../../etc/passwd", # refused by routing - see docstringFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.assert windows.aimed == [4808], "it never even tried to kill it"Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.died between the listing and the kill exits non-zero, and that is theFix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.spec.loader.exec_module(module)Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.module = importlib.util.module_from_spec(spec)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 tmodloader-mcp@0.7.1 as of 2 h ago. This is the package itself, not its dependencies.