heroku@1.2.14
VERIFIED· startup onlyPublisher claims: "Heroku Platform MCP Server using the Heroku CLI" 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
HEROKU_API_KEYConfiguration, not credentials: HEROKU_HEADERS, HEROKU_MCP_MODE, HEROKU_MCP_SERVER_VERSION, MCP_SERVER_IDLE_TIMEOUT, MCP_SERVER_REQUEST_TIMEOUT- Where it talks to
- heroku.com, herokuapp.com (its own)Also test.com, example.invalid — 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 test.com, example.invalid as well as its own vendor. The guard injects HEROKU_API_KEY only into requests to heroku.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; startup only; authenticated tool behavior not tested) on 2026-11-10 and scored it 87/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 · 25 s · 2 scenarios · 0 deviationsStatic findings
* - it avoids the npx cold-start penalty (npm registry resolution, often 5-15s) on every spawn,Fix: Pin versions and sources; vendor anything fetched at install time.// npx is also available, but must not be used when a suitable local CLI existsFix: Pin versions and sources; vendor anything fetched at install time.expect(isSafeSourceRelativePath('/etc/passwd')).to.be.false;Fix: Stop enumerating or reading credential locations; take secrets from a declared environment variable the user sets on purpose.public kill = sinon.stub();Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.it('should fall back to npx when the local heroku CLI is too old (< 10.10.0)', () => {Fix: Pin versions and sources; vendor anything fetched at install time.// Keep an error sink so a post-kill 'error' doesn't become an uncaught throw.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.// npx availableFix: Pin versions and sources; vendor anything fetched at install time."exec-perms": "shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.'Startup error: No suitable Heroku CLI found. Install the Heroku CLI (version 10.10.0 or higher) in your PATH, or make npx available. Please install one of them.'Fix: Pin versions and sources; vendor anything fetched at install time.// npx must not even be probed when a suitable local CLI is foundFix: Pin versions and sources; vendor anything fetched at install time.* Falls back to `npx -y heroku@latest repl` only when no suitable local CLI is foundFix: Pin versions and sources; vendor anything fetched at install time.* null only when neither a usable local CLI nor npx is available.Fix: Pin versions and sources; vendor anything fetched at install time.`${TOOL_COMMAND_MAP.PG_PSQL} --app='myapp' --command='SELECT * FROM users' --file='query.sql' --credential='mycred' -- 'HEROKU_POSTGRESQL_RED'`Fix: Remove the call, or declare the host in frontmatter and explain in the README what is sent and why.it('should fall back to npx when heroku CLI is not available', () => {Fix: Pin versions and sources; vendor anything fetched at install time.// kill a process that now has work to do.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.* Registers the pg:kill tool with the MCP server.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.- `maintenance_on` - Enable maintenance mode for an app.Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.{ "name": "maintenance_on", "description": "Enable maintenance mode for an app." },Fix: Remove the text that addresses the agent rather than the reader; describe behavior, do not instruct.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
Vulnerability advisories (OSV) cover npm and PyPI packages; this registry has no advisory database.