Rules for using the Runnerhut website, application, and MCP connection
Terms of service
Terms that govern your use of the Runnerhut website, application, and read-only MCP server.
Updated 2026-08-26
Provider and scope
| Item | Details |
|---|---|
| Provider | Derinbogaz Ventures UG (haftungsbeschränkt) |
| Address | Kolonnenstraße 8, 10827 Berlin, Germany |
| Register | Commercial Register of the Local Court of Charlottenburg (Berlin), HRB 232104 B |
| Represented by | Ceyhun Afsin Derinbogaz, managing director |
| Legal contact | legal@runnerhut.com |
These Terms govern your access to runnerhut.com, the Runnerhut application, and the authenticated, read-only Runnerhut MCP server. By using any of them, you agree to these Terms. If you use the service for an organization, you confirm that you are authorized to bind that organization.
The service
Runnerhut helps users connect a GitHub App installation, inspect repository compatibility and runner information, and create migration campaigns. The MCP server provides read-only access to repository compatibility, runner profiles, active-job status, and non-mutating migration previews for the Runnerhut organization you authorize. It cannot create pull requests, change workflows, or start runners.
Your responsibilities
- Connect only GitHub accounts, App installations, and repositories that you are authorized to access and use.
- Keep your GitHub account, Runnerhut session, and MCP client environment secure. Revoke access promptly if you suspect unauthorized use.
- Do not use the service to violate law, infringe third-party rights, interfere with the service, or bypass access controls or rate limits.
- Review any migration output before acting on it. Runnerhut’s MCP tools are informational and do not replace your own security, code-review, or deployment controls.
GitHub and MCP authorization
GitHub authentication and App installation are subject to GitHub’s terms and permissions. When an MCP client asks to connect, you must review the client name, redirect destination, and requested read-only scope before approving it. You may disconnect GitHub or revoke the MCP client’s access at any time through the relevant account or client controls.
Availability and changes
We may change, suspend, or discontinue parts of the service when reasonably necessary for security, maintenance, legal compliance, or product development. We will make reasonable efforts to give advance notice of material changes where practical. You may stop using the service at any time.
Intellectual property and feedback
Runnerhut and its software, branding, and documentation are owned by us or our licensors. These Terms give you a limited, non-exclusive, non-transferable right to use the service as provided. You retain rights in your repositories and other content. If you give us feedback, you grant us a non-exclusive right to use it to improve the service without compensation or restriction.
Liability
Nothing in these Terms excludes or limits liability where it cannot lawfully be excluded or limited. To the maximum extent permitted by law, the service is provided on an “as available” basis and we are liable only for foreseeable damage caused by our breach of these Terms. This does not affect mandatory consumer protections.
Governing law
German law applies, excluding the UN Convention on Contracts for the International Sale of Goods. If you are a merchant, public-law entity, or special fund under public law, the courts of Berlin have exclusive jurisdiction. Mandatory laws and consumer protections that apply to you remain unaffected.
Contact and changes
Questions about these Terms can be sent to legal@runnerhut.com. We may update these Terms by posting a new version here. The updated Terms apply from the effective date shown above; if a material change requires notice or consent by law, we will provide it.
Your next build could be twice as fast, at half the price
Start free. Migrating away is the same one line, and we publish that diff too.