poselab-mcp@0.7.0
VERIFIED· not startedPublisher claims: "An MCP server of measured spatial answers for posing first-person arms and a rifle in Blender: clipping depth, what the eye sees, and a solver that says which goals no move can meet." 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
POSELAB_TOKENConfiguration, not credentials: POSEFAULT_REPAIR, POSELAB_BLENDER, POSELAB_OUT, POSELAB_RIGS- Where it talks to
- no vendor host named in the codeAlso cdc.gov, eatonhand.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 cdc.gov, eatonhand.com as well as its own vendor. The guard injects POSELAB_TOKEN only into requests to the host you bind (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-14 and scored it 90/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
self.p = subprocess.Popen([sys.executable, "-m", "poselab_mcp"], stdin=subprocess.PIPE, stdout=subprocess.PIPE)Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.list.json: {"poses_dir": <a generate.py output folder>, "episodes": {"r01": "<pose id>", ...}}. The pose ids stay inFix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.self.proc = subprocess.Popen([find_blender(), "-b", "--factory-startup", "-P", str(WORKER), "--", str(port), rigs, str(out)],Fix: Build commands from fixed arguments, never from interpolated strings; prefer an API client over shelling out.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 poselab-mcp@0.7.0 as of 4 min ago. This is the package itself, not its dependencies.