Custom domain on Namecheap
Namecheap’s record editor is the Advanced DNS tab. Like most registrars, its Host field is relative — subdomain labels only, no domain suffix.
The records you’ll create
Your exact names and values are generated on the server’s Deployments tab → Custom domain card. They follow this shape:
| Type | Name | Value | Purpose |
|---|---|---|---|
| CNAME | mcp.acme.com | connect.mcp-dns.com | Routes traffic to MCPCloud |
| TXT | _cf-custom-hostname.mcp.acme.com | ce2337e3-…-c789c237d377 | Proves you own the domain |
Setup on Namecheap
- Sign in at namecheap.com, open Domain List, click Manage on the domain, then the Advanced DNS tab.
- Add New Record → CNAME Record: Host is the subdomain only (e.g. `mcp`), Value is the CNAME target from your MCPCloud domain card. Leave TTL on Automatic.
- Add New Record → TXT Record: Host is the ownership labels without your domain (e.g. `_cf-custom-hostname.mcp`), Value is the token from the card.
- Save all changes, then hit Recheck in MCPCloud. Namecheap propagation is usually under five minutes.
Verify and go live
Back on the Custom domain card, hit Recheck. The status walks from Verifying DNS to Issuing certificate to Active — usually within minutes of the records propagating. Once Active, your server answers at https://mcp.acme.com/mcp and the certificate renews automatically.
Troubleshooting
The subdomain still shows a parking page or redirect.
Delete any URL Redirect Record on the same host — Namecheap serves redirects before your CNAME resolves.
Records look right but verification fails.
If the domain uses custom nameservers (e.g. pointing at another host), Advanced DNS records are ignored — add the records wherever the nameservers actually live.
Calls through the custom domain get a 403 (often “browser_signature_banned” or a challenge page) while the platform URL works.
Your DNS zone’s WAF or bot-protection rules apply to the custom hostname, and MCP clients send unusual or minimal user agents. Exempt the hostname (or the path) from bot fight / managed challenge rules in your zone, or point clients at the platform URL until you do. The 403 comes from your zone, not from MCPCloud.
Other DNS providers