hatchbox-mcp-server@0.1.3
VERIFIED· startup onlyPublisher claims: "MCP server for Hatchbox Rails hosting — env var inspection, deploys, and process monitoring." 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
- Needs
- HATCHBOX_API_KEY, HATCHBOX_DEPLOY_KEY — give it to the server where it runs, through vet-skills run --secrets, so the value never enters the server's environment. Never paste a credential into a chat, a ticket or a report.
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
HATCHBOX_API_KEYConfiguration, not credentials: ALLOW_DEPLOYS, HATCHBOX_ACCOUNT_ID, HATCHBOX_APP_ID, HATCHBOX_APP_NAME, HATCHBOX_DEPLOY_KEY, HATCHBOX_MOCK_DATA, READONLY, SSH_KEY_PATH, WEB_SERVER_IP_ADDRESS- Where it talks to
- hatchbox.io (its own)
- 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. It asks for HATCHBOX_API_KEY and talks to hatchbox.io. Give the credential to the guard, not the server: the value never enters the server's environment and only travels to the host you bind. What the tools do with a real credential was not observed.
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-13 and scored it 95/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 (it asks for HATCHBOX_API_KEY, HATCHBOX_DEPLOY_KEY); 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 · 47 s · 2 scenarios · 0 deviationsStatic findings
No findings across 1,827 lines in 43 files.
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 hatchbox-mcp-server@0.1.3 as of 18 h ago. This is the package itself, not its dependencies.