Terms of Service
These terms govern use of mcphost, a hosted runtime for Model Context Protocol (MCP) tools operated by Joseph Yen, sole proprietor, doing business as mcphost ("we", "us"). By signing up — including when an AI agent signs up programmatically — you accept these terms.
1. Accounts and agents
A tenant is created by the signup tool call and controlled by its bearer key. mcphost is designed to be operated by AI agents; the person or entity that runs, authorizes, or benefits from an agent is the account holder and is responsible for everything done with the tenant's key, including charges. Keep the key secret; we store only a hash and cannot recover it.
2. The service
mcphost lets a tenant publish, call, and manage tools (echo, HTTP wrappers, and Python code) in an isolated namespace, subject to the published limits and the plan quotas returned by billing.plans. The service is in early access: features, limits, and pricing may change, and we may modify or discontinue parts of the service with reasonable notice where practical.
3. Your code and data
You retain ownership of tool specifications, code, and data you submit. You grant us the rights needed to store and execute them to provide the service. You are responsible for having the rights to anything you submit, and for what your published tools do when called.
4. Acceptable use
Use of the service is subject to the Acceptable Use Policy, which is part of these terms. We may throttle, suspend, or terminate tenants that violate it, that create security or legal risk, or that abuse resources; where reasonable we will notify the contact we have and describe the cause.
5. Fees and billing
The free plan requires no payment. Paid plans are billed by Stripe on a subscription basis plus metered usage as described at signup and on the pricing section. Metered usage is invoiced per the published per-call rate beyond the included volume. Price changes apply from your next billing period after notice. Taxes are added where required.
6. Sandboxing and security
Tenant code runs in an isolated sandbox with resource limits. We work to keep tenants isolated from each other and from the host, but no sandbox is guaranteed impenetrable. Do not test or probe the sandbox or the service's security except with our prior written permission.
7. Availability
The service is provided without an uptime commitment during early access. We take backups of service data but recommend you keep your own copies of tool specifications and code.
8. Disclaimer of warranties
The service is provided "as is" and "as available", without warranties of any kind, express or implied, including merchantability, fitness for a particular purpose, and non-infringement.
9. Limitation of liability
To the maximum extent permitted by law, our total liability arising out of or related to the service is limited to the amounts you paid us in the twelve months before the claim, and we are not liable for indirect, incidental, special, consequential, or exemplary damages, or for lost profits, data, or goodwill.
10. Indemnification
You will defend and indemnify us against claims arising from your tools, your use of the service, or your violation of these terms.
11. Termination
You can stop using the service at any time; contact us to delete a tenant. We may suspend or terminate tenants as described in section 4, and may delete a terminated tenant's data after 30 days.
12. Changes to these terms
We may update these terms; material changes will be reflected on this page with a new date, and continued use after the change is acceptance. The machine-readable service description at /llms.txt is kept consistent with these terms.
13. Governing law
These terms are governed by the laws of the State of California, USA, excluding conflict-of-law rules, and disputes belong to the state and federal courts located in California.