heroku@1.2.14

VERIFIED· startup only

Publisher claims: "Heroku Platform MCP Server using the Heroku CLI" Observed in sandbox: no network, touches nothing outside the project, writes no memory.

Registry Docker MCP CatalogPublisher heroku · publishing for 586 daysInstalls 21,200Last detonated 5d ago
$docker run -i --rm mcp/heroku
WatchReport an issue

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.

$vet-skills run --secrets HEROKU_API_KEY=heroku.com -- docker run -i --rm mcp/heroku

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 deviations
t+CategoryObserved action
0.0sprocessno install scripts in bundle
4.4sprocessdependency install exit 0
24sclaimedstartup only: exited (0) before answering · (node:1983) [UNDICI-EHPA] Warning: EnvHttpProxyAgent is experimental, expect them to change at any time. (Use `node --trace-warnings ...` to show where the warning was created) Fatal error in main(): Cannot find module '/tmp/ks-detonate-hMvht0/task/home/work/acme-api/.claude/skills/heroku/dist/index.js' imported from /tmp/ks-detonate-hMvht0/task/home/work/acme-api/.claude/skills/heroku/bin/heroku-
24sprocessscript backend runs setup only
24sprocessno install scripts to re-run

Static findings

MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.ts:139 · npx invocation of non-well-known package — may execute untrusted code* - 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.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.spec.ts:556 · npx invocation of non-well-known package — may execute untrusted code// 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.
AST06
MEDIUM
Access to sensitive file pathssrc/tools/deploy-to-heroku.spec.ts:37 · Access to sensitive file paths — SSH keys, AWS credentials, env files, or system filesexpect(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.
AST05
MEDIUM
Process kill commandsrc/repl/heroku-cli-repl.spec.ts:25 · Process kill command — agent can terminate processespublic kill = sinon.stub();Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.spec.ts:613 · npx invocation of non-well-known package — may execute untrusted codeit('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.
AST06
MEDIUM
Process kill commandsrc/repl/heroku-cli-repl.ts:433 · Process kill command — agent can terminate processes// 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.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.spec.ts:597 · npx invocation of non-well-known package — may execute untrusted code// npx availableFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File permission modification commandpackage.json:86 · File permission modification command — agent changes file ownership/permissions"exec-perms": "shx chmod +x dist/*.js",Fix: Request the narrowest permission that works; replace wildcards with the exact paths or hosts.
AST05
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.ts:191 · npx invocation of non-well-known package — may execute untrusted code'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.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.spec.ts:569 · npx invocation of non-well-known package — may execute untrusted code// npx must not even be probed when a suitable local CLI is foundFix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.ts:145 · npx invocation of non-well-known package — may execute untrusted code* 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.
AST06
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.ts:147 · npx invocation of non-well-known package — may execute untrusted code* null only when neither a usable local CLI nor npx is available.Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
File type combined with upload actionsrc/tools/data.spec.ts:59 · File type combined with upload action — agent may exfiltrate local data files`${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.
AST07
MEDIUM
npx invocation of non-well-known packagesrc/repl/heroku-cli-repl.spec.ts:590 · npx invocation of non-well-known package — may execute untrusted codeit('should fall back to npx when heroku CLI is not available', () => {Fix: Pin versions and sources; vendor anything fetched at install time.
AST06
MEDIUM
Process kill commandsrc/repl/heroku-cli-repl.spec.ts:257 · Process kill command — agent can terminate processes// kill a process that now has work to do.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
MEDIUM
Process kill commandsrc/tools/data.ts:309 · Process kill command — agent can terminate processes* Registers the pg:kill tool with the MCP server.Fix: Build commands from fixed arguments; do not interpolate untrusted strings into a shell.
AST05
LOW
Context shift attemptREADME.md:325 · Context shift attempt — trying to change operational mode · informational: not an instruction file- `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.
AST01
LOW
Context shift attemptmanifest.json:57 · Context shift attempt — trying to change operational mode · informational: not an instruction file{ "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.
AST01

Cost to the agent

Instructions loaded
≈33 tok
1 file · 81 in bundle
Tool list per prompt
≈0 tok
0 tools · 0 per tool
Handshake
no reply
launch to tools/list, stdio
Undocumented tools
0
description under 20 chars · avg 0

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.