registry / record
@heroku/mcp-server
> throne registry @heroku/mcp-server
sealed
- scan id
- 0cfad3fb66424627876a52787db6f6d6
- target
- @heroku/mcp-server
- sealed at
- 2026-06-13 03:47:50Z
- evidence hash
- sha256:279d4d716b360d53a71996c47b98bd24c2b36a3b67dcc960dcf28e2b16b496c3
initialize ok: server Heroku MCP Server 1.2.3, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools']
supported: tools/list (33 tools), resources/list (1); method not found (tolerated): prompts/list
all 33 tool inputSchemas are valid JSON Schema
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
initialize ok: server Heroku MCP Server 1.2.3, negotiated protocolVersion 2025-11-25, capabilities ['resources', 'tools']
supported: tools/list (33 tools), resources/list (1); method not found (tolerated): prompts/list
all 33 tool inputSchemas are valid JSON Schema
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
TimeoutError:
"prepare" runs on git-dependency installs and local dev (not registry installs): 'husky'
package/package.jsonspawn() called with a dynamically built command (heuristic — review): 'cliCommand, cliArgs, {'
package/dist/repl/heroku-cli-repl.js:168execSync() called with a dynamically built command (heuristic — review): '`git remote add heroku-${result.name} ${app.git_url}`, { cwd: rootUri });'
package/dist/tools/deploy-to-heroku.js:2472 non-local endpoint host(s) referenced in code — verify each is expected for this server's purpose: api.heroku.com (package/dist/tools/deploy-to-heroku.js:85), devcenter.heroku.com (package/dist/resources/dev-center-resource.js:8)
package/dist/resources/dev-center-resource.js:8maintainer of this server? challenge this record: hello@usethrone.dev. tell us what we got wrong and we re-run it in the open.
this page renders the stored record of a real run. nothing on it is asserted without the execution that proved it.