Slug Reservation & Cooling-Off Period
How mctx reserves subdomains after server deletion. 7-day cooling-off period on production, DNS hijacking protection, and test environment behavior.
When you delete an MCP server on mctx, the subdomain (e.g., hello-world.mctx.ai) isn't immediately released. mctx uses a reservation system to prevent accidents and protect against DNS hijacking.
How Slug Reservation Works
7-Day Cooling-Off Period (Production)
After deleting a server on production, you must wait 7 days before recreating a server with the same slug.
Purpose:
- Prevents accidental permanent deletion
- Gives you time to recover if you change your mind
- Reduces support burden from "I deleted my server by mistake" requests
Example:
- You delete
my-server.mctx.aion February 10, 2026 - You cannot recreate
my-serveruntil February 17, 2026 - If you try before then, you'll see an error message with the exact date
DNS Hijacking Protection
A deleted slug can NEVER be claimed by a different user.
Why this matters:
Once you've deployed an MCP server, subscribers configure their MCP clients with your subdomain URL (e.g., my-server.mctx.ai). If someone else could claim that slug after you delete it, they could:
- Intercept traffic from your former subscribers
- Impersonate your server
- Gain access to subscriber credentials
Result: Your slug is permanently reserved to your account. No one else can ever claim it.
Environment Differences
| Environment | Cooling-Off Period | Why |
|---|---|---|
| Production | 7 days | Prevents accidental deletions |
| Test | None | Fast iteration during development |
On the test environment ({slug}-test.mctx.ai), slugs are immediately reusable by the same owner. This allows faster development iteration without waiting.
Error Messages
When you try to reuse a slug during the cooling-off period, you'll see:
This slug is reserved until [exact date]. You deleted a server with this slug recently.The error message tells you exactly when the slug becomes available again.
What If I Need the Slug Sooner?
You don't. The 7-day cooling-off period is not bypassable.
Why it's enforced:
- Prevents abuse (users deleting and recreating servers to dodge subscriber locks)
- Ensures consistency (no special cases to track or support)
- Protects security (prevents social engineering attempts)
Alternatives
Use a Different Slug
If you need to deploy immediately, create a new server with a different slug.
Examples:
| Original Slug | Alternative |
|---|---|
my-server | my-server-v2 |
weather-api | weather-api-new |
data-helper | data-helper-experimental |
You can delete the new server later and return to the original slug after the cooling-off period.
Wait It Out
The 7-day period passes quickly. Use the time to:
- Improve your server code
- Write documentation
- Plan your relaunch
- Test on the test environment
Checking Slug Availability
When creating a new server, the slug field validates in real-time:
| Status | Message |
|---|---|
| Available | Green checkmark |
| Taken by another user | "This slug is already taken" |
| Cooling-off period | "This slug is reserved until [date]" |
| Invalid format | "Slug must be 3-50 characters, lowercase alphanumeric" |
Technical Details
Reservation Tracking
Slug reservations are stored in the database with:
- Original server ID
- Owner user ID
- Deletion timestamp
- Calculated availability date (deletion timestamp + 7 days)
Validation Flow
When you attempt to create a server:
- mctx checks if slug exists in active servers (rejected if exists)
- mctx checks if slug is reserved to a different user (rejected permanently)
- mctx checks if slug is reserved to you with active cooling-off period (rejected with date)
- If all checks pass, slug is available
Slug Format Rules
| Rule | Example | Valid |
|---|---|---|
| Lowercase letters | my-server | Yes |
| Numbers | server123 | Yes |
| Hyphens | my-cool-server | Yes |
| Length: 3-50 chars | abc | Yes |
| Uppercase letters | My-Server | No |
| Underscores | my_server | No |
| Spaces | my server | No |
| Special characters | my-server! | No |
Best Practices
Before Deleting a Server
- Download any data or logs you need
- Notify active subscribers
- Consider deactivating instead of deleting if you might return
After Deleting a Server
- Note the availability date from the error message
- Set a calendar reminder if you plan to reclaim the slug
- Use the test environment for experimentation during the waiting period
Choosing Slugs
- Pick something unique to reduce collision risk
- Avoid generic names like
serverorapi(likely already taken) - Use your brand or project name for recognizability
- Keep it short but descriptive
Frequently Asked Questions
Can I transfer my slug to another user?
No. Slugs are permanently tied to the account that first created them.
What happens to my slug if I delete my account?
The slug remains reserved. It cannot be reclaimed by anyone.
Can I have multiple servers with the same slug?
No. Each slug is unique across the platform. However, you can have multiple versions of one server (e.g., my-server.mctx.ai/v1.0.0 and my-server.mctx.ai/v2.0.0).
Does the cooling-off period apply if I deactivate instead of delete?
No. Deactivating a server keeps it in your account. You can reactivate it anytime without waiting. The cooling-off period only applies to deletion.
Can I see when a slug becomes available?
Yes. Try creating a server with that slug. The error message displays the exact availability date.
See Also
- Deploy Your Server - Create a new server
- Versioning - Managing multiple versions without changing slugs
- mctx.json Reference - Server configuration
See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.
Server Logs
Real-time log streaming architecture on mctx. How logs are captured, WebSocket streaming, console output, and no retention policy.
Deleting Your Server
How to permanently delete your MCP server from mctx, including the 72-hour wind-down period for servers with active subscribers and emergency immediate deletion.