pitbox@0.3.2
VERIFIED· startup onlyPublisher claims: "Run, drive and debug apps on emulators, simulators and devices from one MCP server — fast and token-lean" Observed in sandbox: no network, touches nothing outside the project, writes no memory.
Coverage
Startup only; authenticated tool behavior not tested.- Tested
- server startup over stdio (initialize sent) · every file read, file written and host contacted by what ran
- Not tested
- the tool list (the server exited before answering) · what the tools do when called with real credentials
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
PITBOX_REMOTE_TOKENConfiguration, not credentials: ANDROID_SERIAL, ComSpec, PATHEXT, PITBOX_BASH, PITBOX_HOME, PITBOX_PORTS, PITBOX_PUSH_URL, PITBOX_SESSION- Where it talks to
- no vendor host named in the codeAlso example.test, android.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
- the tool list (the server exited before answering) · what the tools do when called with real credentials
Connect it with a scoped credential, under the guard, and read the third-party hosts first. The code names example.test, android.com as well as its own vendor. The guard injects PITBOX_REMOTE_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; startup only; authenticated tool behavior not tested) on 2026-11-15 and scored it 84/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 · 36 s · 2 scenarios · 0 deviationsStatic findings
return framework === 'expo' ? 'npx expo start --port {port}' : 'npx react-native start --port {port}';Fix: Pin versions and sources; vendor anything fetched at install time.const env = { ...process.env, ...ctx.config.devserver?.env };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 @veksa/pitbox@0.3.2 as of 25 min ago. This is the package itself, not its dependencies.