thrixel-mcp@1.3.38
CAUTION· not startedPublisher claims: "MCP server for Thrixel - text/image to editable, game-ready 3D assets." 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: Caution 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
THRIXEL_API_KEYConfiguration, not credentials: THRIXEL_API_BASE, THRIXEL_GUIDE_BRANCH, THRIXEL_LOG_LEVEL, THRIXEL_NO_TIPS, THRIXEL_OUTPUT_DIR, THRIXEL_TIMEOUT_S- Where it talks to
- thrixel.com (its own)Also githubusercontent.com — 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
- server startup · the tool list · tool behavior
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names githubusercontent.com as well as its own vendor. The guard injects THRIXEL_API_KEY only into requests to thrixel.com (and its subdomains) and refuses the rest.
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-13 and scored it 77/100 (Caution). It is not known to be malicious, but it has behaviour or code a security policy should decide on before install. Notable findings: Collapsed <details> block carrying instructions; Collapsed <details> block carrying instructions; References a credential file in the home directory. Summary: no network, touches nothing outside the project, writes no memory.
Behavior trace
Honeypot run · 0 s · 2 scenarios · 0 deviationsStatic findings
<summary>Passing the key explicitly instead (and why it is second choice)</summary> > **This puts a live key into your shell history** (`~/.bash_history`, > PowFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.<summary>Prefer to create a key by hand?</summary> 1. Open **[thrixel.com/create/#settings/api-keys](https://thrixel.com/create/#settings/api-keys)**. 2. Click Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.in a 0700 directory is what `~/.aws/credentials`, `~/.npmrc`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.<summary><b>Pre-release / unpublished builds</b></summary> `uvx` can run straight from the repository, no PyPI release needed: ```bash # latest main, ahead of tFix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.in a 0700 directory is what `~/.aws/credentials`, `~/.npmrc`,Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose."the build output, so moving the value into .env does NOT fix it. "Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.# into the shipped JavaScript, so a .env that was never going to be uploadedFix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.`~/.docker/config.json` and gh's own fallback do, and it works everywhere.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 thrixel-mcp@1.3.38 as of 36 h ago. This is the package itself, not its dependencies.
What would make this Verified
3 points to 80 · weights: behavior 45%, static 25%, prompt 15%, publisher 15%- Unclaimed publisher≈ +8 on the totalClaim thrixel: a verified publisher gets +50 on publisher trust. It is free and usually instant with GitHub sign-in.
- Hidden instructions≈ +6 on the totalRemove HTML comments, zero-width characters and white-on-white text that carry instructions. Everything the agent is meant to read should be visible to the person reading the file.
- References a credential file in the home directory≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.
- Access to sensitive file paths≈ +4 on the totalStop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.