When a Server You Use Is Deleted

Sometimes developers delete servers from mctx. This guide explains what happens when a server you're subscribed to is deleted and what you need to do.

How You'll Know

When a developer deletes a server you're subscribed to, you're notified through three channels:

1. Email Notification

You'll receive an email from mctx with one of the following subjects:

72-hour notice (standard deletion):

• Subject: "Server deletion notice: [server-name] will shut down within 72 hours"
• Server remains accessible during the wind-down period
• You can continue using it until the shutdown time

Immediate shutdown:

• Subject: "Server shutdown: [server-name] has been shut down"
• Server access ended immediately
• No wind-down period provided

Accelerated shutdown (wind-down ended early):

• Subject: "Server shutdown accelerated: [server-name] shut down immediately"
• Original 72-hour notice was superseded by emergency deletion
• Access ended immediately

2. In-App Countdown Card (72-Hour Notice Only)

When you visit your subscriptions page, servers scheduled for deletion appear with:

• Red warning card with countdown timer
• Shutdown timestamp (exact date and time)
• Emergency delete button (if developer hasn't finalized yet)

Example:

⚠️ Server scheduled for deletion

weather-data-server will shut down in 23 hours, 14 minutes

Your subscription will end and access will be removed at 2026-02-14 15:30 UTC.

3. Login Banner (After Deletion Completes)

When you log in to your dashboard after a server is deleted, you'll see a dismissible banner at the top:

Server deleted: weather-data-server has been shut down. Your subscription has been canceled.

Click the × to dismiss the banner.

What Happens to Your Subscription

During Wind-Down (72-Hour Notice)

Access:

• Server remains fully accessible
• All tools and features continue working
• No service interruption during the wind-down period

Billing:

• Your subscription remains active
• You're billed for any requests you make during the wind-down
• Metered billing continues normally until shutdown

When shutdown occurs:

• Subscription is canceled automatically in Stripe
• Access to the server ends immediately
• You stop being charged

Immediate Shutdown (No Wind-Down)

Access:

• Server taken offline immediately
• All requests return errors
• Credentials stop working instantly

Billing:

• Subscription is canceled immediately
• You're billed only for usage up to the point of cancellation
• No charges for time after shutdown

Billing and Refunds

No Refunds (Metered Billing)

mctx uses usage-based billing, which means:

• You only pay for requests you actually make
• There's no upfront charge or subscription fee to refund
• You're billed for usage up to the point of cancellation
• Metered billing is inherently fair: use nothing, pay nothing

Example:

• You made 5,000 requests before shutdown → Billed for 5,000 requests
• You made 0 requests before shutdown → Billed $0

What You're Charged For

• 72-hour wind-down: Usage during the wind-down period is billed normally
• Immediate shutdown: Usage up to the moment of shutdown is billed
• After cancellation: Zero charges (subscription ended)

What You Should Do

If You Receive 72-Hour Notice

Option 1: Continue Using (No Action Required)

• Server remains accessible for 72 hours
• Use it as normal during the wind-down period
• Subscription cancels automatically at the end of the window

Option 2: Unsubscribe Early

If you don't plan to use the server during the 72-hour window:

1. Go to Subscriptions
2. Find the server with the deletion countdown
3. Click "Cancel Subscription"
4. Confirm cancellation

Why unsubscribe early? If you know you won't use the server during the wind-down, unsubscribing immediately stops any chance of accidental billing.

If Server Shuts Down Immediately

Action required:

1. Update your MCP client configuration to remove the server
2. Check for errors in your AI tool (requests will fail)
3. Find an alternative server if needed

How to remove from your configuration:

Most MCP clients store configuration in a JSON file. Remove the deleted server's entry:

Claude Desktop (claude_desktop_config.json):

{
  "mcpServers": {
    "deleted-server-name": {
      "url": "https://deleted-server.mctx.ai/v1.0.0"
    }
  }
}

Remove the "deleted-server-name" entry entirely.

Finding an Alternative Server

If the deleted server was critical to your workflow, you can:

1. Search the MCP Community Registry for similar servers
2. Check MCP directories like awesome-mcp-servers
3. Ask the developer if they're deploying a replacement (check their GitHub or social profiles)

Frequently Asked Questions

Why was the server deleted?

Common reasons:

• Developer decided to discontinue the service
• Security incident requiring immediate shutdown
• Server replaced with a new version under a different slug
• Developer no longer maintaining the project

mctx doesn't control developer decisions to delete servers. If you have questions about why a specific server was deleted, contact the developer directly (check their GitHub profile or server documentation).

Can I keep using the server after deletion?

No. Once a server is deleted, all deployments are removed from infrastructure. The subdomain becomes unavailable and credentials stop working.

What if I need the server for my business?

If a server is critical to your operations:

1. During 72-hour wind-down: Migrate to an alternative server as soon as possible
2. Immediate shutdown: Find a replacement immediately
3. For critical infrastructure: Consider self-hosting MCP servers you depend on to maintain control

Lesson: Don't build critical business infrastructure on third-party MCP servers without a backup plan.

Will I be notified if other servers I use are deleted?

Yes. You'll receive the same multi-channel notifications (email, countdown card, login banner) for any server you're subscribed to.

Can I resubscribe after deletion?

No. Once a server is deleted, it's permanently removed. If the developer redeploys the server:

• They must use a new slug (7-day cooling-off period prevents immediate reuse)
• You'll need to subscribe to the new server as if it's a completely different service
• Old credentials and configuration won't work

What if I didn't receive a notification?

Check:

1. Email spam folder - Notification emails may be filtered
2. Email preferences - Ensure you haven't disabled notifications in settings
3. Subscriptions page - Countdown cards appear even if email is disabled
4. Recent activity - Check if your subscription was already canceled before deletion

If you still didn't receive a notification, report it via feedback.

Can the developer cancel deletion?

No. Once a developer confirms deletion (standard or emergency), it cannot be reversed. Even during the 72-hour wind-down, the developer can only accelerate deletion (not cancel it).

Related Documentation

• Frequently Asked Questions - General troubleshooting and common questions
• How Pricing Works - Understanding metered billing
• What is an MCP Server? - Learn about MCP protocol and servers

See something wrong? Report it or suggest an improvement — your feedback helps make these docs better.