Designed so your API and credentials stay yours
MCP Cloud is in private beta and not live. These are the controls we are building it around. Every item on this page is planned for beta, not a description of a running service.
Planned controls
- Planned for beta
Isolated Worker per server
Each hosted MCP server runs in its own Cloudflare Worker, so servers are kept separate from one another.
- Planned for beta
Open-source, auditable runtime
The code that runs your server is produced by the same MIT-licensed generator you can read, run and audit on GitHub.
- Planned for beta
No request or response bodies in logs
We log metadata only: tool name, status, latency and size. Retention depends on your plan.
- Planned for beta
Credentials passed through by default
By default your API credentials travel with each request and are not stored. If you choose to store them, they are kept as encrypted Worker secrets that cannot be read back.
- Planned for beta
Outbound calls only to your API
A server can only make requests to the API hosts listed in your OpenAPI spec.
- Planned for beta
Write and delete tools off by default
Tools that change or delete data stay disabled until you turn them on.
- Planned for beta
Export your code anytime
Download the generated server and host it yourself whenever you want. No lock-in.
Self-hosting today? The generator's own protections are covered in the security model docs.
Responsible disclosure
If you find a vulnerability in openapi-mcp-generator or this website, please report it privately. Do not open a public GitHub issue.
- Security contact
- To be published Placeholder
- Policy and process
- See SECURITY.md in the GitHub repository.
Subprocessors
Third parties we plan to use to run MCP Cloud.
| Provider | Purpose |
|---|---|
| Cloudflare | Runs hosted MCP servers (Workers) and stores encrypted secrets |
| Supabase | Database for the waitlist and service data |
| Payment providerTBC | Billing for paid plans |
| Email providerTBC | Account and service emails |