HOW ZEPHEX IS BUILT
Zephex is a hosted MCP service. Your client connects to zephex.dev/mcp; tool calls execute on our MCP Server; accounts and API keys live in Supabase; dashboard login uses Supabase Auth. Live status: zephex.dev/status.
| Provider | Role |
|---|
| Supabase | Postgres database and dashboard authentication (accounts, API key hashes, usage logs, sessions). |
| Auth0 | OAuth authorization server for MCP connector clients (Claude.ai, ChatGPT, PKCE flows). |
| Railway | MCP Server — hosts tool execution (find_code, read_code, check_test, etc.). |
| Vercel | Dashboard, public MCP endpoint proxy (zephex.dev/mcp), and edge routing. |
| Upstash Redis | Rate limiting, session cache, and health-check coordination. |
| Stripe | Payments, subscriptions, and billing meters. |
| Resend | Transactional email (verification, security alerts, billing notices). |
| Sentry | Error monitoring with PII redaction. |
| PostHog | Product analytics (optional; EU users can decline via cookie banner). |
1. SERVICE DESCRIPTION
Zephex is a cloud-hosted MCP (Model Context Protocol) proxy service. It provides developer tools accessible through a single API endpoint. Users authenticate with API keys and are billed based on request volume.
2. ACCOUNT RESPONSIBILITIES
- You must provide a valid email address to create an account.
- You are responsible for maintaining the security of your account credentials and API keys.
- You must notify us immediately if you suspect unauthorized access to your account.
- One person or entity may not maintain more than one free account.
- You must be at least 13 years old to use Zephex. If you are under 13, you may not create an account.
- By signing up you represent that you are 13 or older.
- Accounts created with disposable or temporary email addresses may be suspended.
TEAM & ORGANIZATIONAL USE
If you roll Zephex out to a team, the account owner remains responsible for every API key created under that account. Each developer should use named keys per environment; shared keys in chat or public repos violate our acceptable-use rules.
- The account owner is responsible for all API key usage under their organization, including contractors.
- API keys must not be embedded in client-side code, public repositories, or shared chat channels.
- Each team member should use their own named key where possible so usage and revocation are attributable.
- Pro and Max plans may restrict keys to specific tools; calls outside the allowlist are rejected.
- Users must keep at least four of ten MCP tools enabled in editor configuration.
- Exceeding plan quotas or abusing rate limits may result in throttling (HTTP 429) or suspension.
- Enterprise volume or custom limits: contact support@zephex.dev.
Rollout guide: Team MCP rollout
3. ACCEPTABLE USE
You agree not to:
- Use the service to develop malware, exploits, or tools intended to harm others.
- Attempt to circumvent rate limits, usage caps, or authentication mechanisms.
- Share API keys publicly or embed them in client-side code.
- Use automated systems to create multiple free accounts to circumvent plan limits.
- Reverse-engineer, decompile, or attempt to extract the source code of the service.
- Use the service in a way that degrades performance for other users.
- Resell access to the service without written permission.
- Use the service to store, transmit, or process illegal content.
4. API KEYS
- API keys are credentials. Treat them like passwords.
- You are responsible for all activity performed with your API keys.
- If a key is compromised, revoke it immediately from the dashboard.
- Zephex may revoke keys that are detected in public repositories, logs, or other exposed locations.
- Revoked keys cannot be restored. Create a new key as a replacement.
5. BILLING & PAYMENTS
- Paid plans are billed monthly in advance via credit or debit card.
- Prices are in USD. Tax may apply depending on your jurisdiction.
- Upgrades take effect immediately. Downgrades take effect at the end of the billing period.
- Failed payments result in a grace period. If payment is not resolved, the account reverts to the Free tier.
- Top-up purchases are non-refundable one-time charges.
- Overage charges (when enabled) are billed on the next invoice at the published per-request rate.
- You can cancel at any time. Access continues until the end of the paid period.
- No refunds are issued for partial months, except during the 7-day Pro trial.
6. INTELLECTUAL PROPERTY
- Your code remains yours. Zephex does not claim any ownership or license over code, prompts, or data you process through the service.
- Tool outputs (analysis results, architecture diagrams, search results) are derived from your input and belong to you.
- Zephex does not use prompts, tool inputs, tool outputs, or repository content accessed through tools to train, fine-tune, or evaluate AI models. This applies to all plans without exception.
- The Zephex service, brand, documentation, and tooling are the intellectual property of Zephex.
7. SERVICE AVAILABILITY
- Zephex targets 99.9% uptime but does not guarantee uninterrupted service. Current status and history: zephex.dev/status.
- Planned maintenance is announced at least 24 hours in advance.
- Zephex is not liable for downtime caused by third-party infrastructure, network issues, or force majeure events.
- During outages, your editor and local development environment continue to function normally — only Zephex-hosted tools are affected.
8. LIMITATION OF LIABILITY
- Zephex is provided "as is" without warranty of any kind, express or implied.
- Zephex is not liable for indirect, incidental, special, or consequential damages.
- Total liability is limited to the amount you paid in the 12 months preceding the claim.
- Zephex is not responsible for the accuracy or completeness of tool outputs — they are informational aids, not guarantees.
9. TERMINATION
- You may delete your account at any time from Dashboard → Settings.
- Zephex may suspend or terminate accounts that violate these terms.
- On termination, API keys are revoked and data is deleted per the privacy policy.
- Sections on intellectual property, limitation of liability, and dispute resolution survive termination.
10. CHANGES TO TERMS
We may update these terms. Material changes are communicated via email at least 14 days before taking effect. Continued use after the effective date constitutes acceptance.
11. GOVERNING LAW
These Terms are governed by the laws of the State of Delaware, USA. Any dispute arising from these Terms will be resolved through binding arbitration in accordance with the American Arbitration Association rules. Arbitration will be the sole remedy for any dispute, and you waive any right to participate in class actions or jury trials.
12. DMCA AND COPYRIGHT
We respect intellectual property rights. If you believe your copyright has been infringed, send a DMCA notice to our designated agent at support@zephex.dev with: (1) description of the copyrighted work, (2) location of the infringing material, (3) your contact information, (4) a statement of good-faith belief, and (5) a statement of accuracy under penalty of perjury.