SunsetDiff

SunsetDiff MCP server

This server answers questions about AI model shutdown dates, official replacements, and migration diffs. It is free. It does not need an API key. The transport is streamable HTTP. Publisher: SunsetDiff.

Endpoint: https://sunsetdiff-api.onrender.com/mcp
Server name: sunsetdiff
Server version: 1.0.0
Client steps below were read from the linked official docs on . Other ways to use the same dates are on Integrations. The static files are on the API page.

Tools

Each input schema is the JSON Schema the server builds from the Zod fields in the service code.

check_model

Look up status, dates, replacement, and source for a model id.

Input schema

{
  "type": "object",
  "properties": {
    "model_id": {
      "type": "string"
    },
    "provider": {
      "type": "string"
    }
  },
  "required": [
    "model_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Example prompt

Check the model id gpt-4o. Add the provider if you know it.

upcoming_shutdowns

List models with an exact shutdown date inside the next N days.

Input schema

{
  "type": "object",
  "properties": {
    "days": {
      "type": "number"
    },
    "provider": {
      "type": "string"
    }
  },
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Example prompt

Which models have an exact shutdown date in the next 30 days?

migration_diff

Return the migration diff for a model. Defaults to the official replacement.

Input schema

{
  "type": "object",
  "properties": {
    "from_model_id": {
      "type": "string"
    },
    "to_model_id": {
      "type": "string"
    }
  },
  "required": [
    "from_model_id"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Example prompt

Show the migration diff from gpt-4o to the official replacement.

scan_text

Find known model ids in text that are deprecated or shutting down.

Input schema

{
  "type": "object",
  "properties": {
    "text": {
      "type": "string"
    }
  },
  "required": [
    "text"
  ],
  "additionalProperties": false,
  "$schema": "http://json-schema.org/draft-07/schema#"
}

Example prompt

Scan this text for model ids that are deprecated, retired, or legacy.

Add it to a client

Each snippet uses only fields those docs show for a remote streamable HTTP server. Leave out any API key header. This server does not use one.

Claude custom connector

Claude's help center says custom connectors using remote MCP are available on Claude, Cowork, and Claude Desktop for Free, Pro, Max, Team, and Enterprise plans. Free users are limited to one custom connector. Claude connects to the server from Anthropic's cloud, so the server must be reachable on the public internet.

The same page says local servers configured in claude_desktop_config.json are a separate mechanism. This server is remote. Add it as a custom connector and paste the URL.

This server does not use an API key. On the authentication step, the help center lists Sign in now, Sign in when needed, and No sign in. Choose No sign in.

  1. Pro and Max: open Customize, then Connectors. Click + Add, then Add custom connector. Enter the name SunsetDiff. Paste the remote MCP server URL. Continue.
  2. Team and Enterprise: an Owner opens Organization settings, then Connectors, clicks Add, hovers Custom, and selects Web. Enter the name and the same URL.
  3. Claude's connector docs also publish a link that opens the add dialog with the name and URL filled in. The person still reviews the values and confirms before anything is added.

Remote MCP server URL

https://sunsetdiff-api.onrender.com/mcp

Add custom connector link

https://claude.ai/customize/connectors?modal=add-custom-connector&connectorName=SunsetDiff&connectorUrl=https%3A%2F%2Fsunsetdiff-api.onrender.com%2Fmcp

Sources: Get started with custom connectors using remote MCP , Directory connectors vs custom connectors , checked October 23, 2026.

Cursor

Cursor's MCP docs list Streamable HTTP as a transport. Its input is a URL to an HTTP endpoint. Put that URL on a server entry in mcp.json.

A project file is .cursor/mcp.json. A global file is ~/.cursor/mcp.json.

The docs' remote sample also includes a headers object. This server does not use an API key, so the snippet has only the url.

mcp.json

{
  "mcpServers": {
    "sunsetdiff": {
      "url": "https://sunsetdiff-api.onrender.com/mcp"
    }
  }
}

Source: Cursor MCP docs , checked October 23, 2026.

VS Code

VS Code's MCP configuration reference says an HTTP server sets type to http and sets url. VS Code tries the HTTP Stream transport first and falls back to SSE when HTTP is not supported.

The workspace file is .vscode/mcp.json. The top-level key in that file is servers. Open the user file with the command MCP: Open User Configuration.

The same reference documents a portable Copilot file, .mcp.json at the workspace root, or mcp-config.json for the user. That file uses mcpServers, with the same type and url.

.vscode/mcp.json

{
  "servers": {
    "sunsetdiff": {
      "type": "http",
      "url": "https://sunsetdiff-api.onrender.com/mcp"
    }
  }
}

Portable .mcp.json

{
  "mcpServers": {
    "sunsetdiff": {
      "type": "http",
      "url": "https://sunsetdiff-api.onrender.com/mcp"
    }
  }
}

Sources: Add and manage MCP servers in VS Code , VS Code MCP configuration reference , checked October 23, 2026.

Windsurf

The Windsurf Cascade MCP page says its mcp_config.json steps apply to the legacy Cascade agent only. The Devin Local agent, the default agent for new tabs, configures MCP servers in the Devin CLI config files instead.

Cascade supports stdio, Streamable HTTP, and SSE. For a remote HTTP server, that page says the entry needs a serverUrl or url field. Open the file from the Cascade panel: the ... menu, then Open MCP config file. On macOS and Linux the file is ~/.config/devin/mcp_config.json. On Windows it is %APPDATA%\devin\mcp_config.json. The page's sample includes a headers object for an API key. This server does not use one.

Devin's MCP configuration page says a URL uses Streamable HTTP. Set transport to http, or omit it. A URL still defaults to Streamable HTTP. devin mcp add sunsetdiff followed by the endpoint URL saves the local scope, .devin/mcp_config.local.json. Add -s user to save the global file, or -s project to save .devin/mcp_config.json.

Legacy Cascade mcp_config.json

{
  "mcpServers": {
    "sunsetdiff": {
      "serverUrl": "https://sunsetdiff-api.onrender.com/mcp"
    }
  }
}

Devin Local mcp_config.json

{
  "mcpServers": {
    "sunsetdiff": {
      "url": "https://sunsetdiff-api.onrender.com/mcp",
      "transport": "http"
    }
  }
}

Devin CLI

devin mcp add -s user sunsetdiff https://sunsetdiff-api.onrender.com/mcp

Sources: Windsurf Cascade MCP , Devin CLI MCP configuration , checked October 23, 2026.

mcp-remote

mcp-remote is a local proxy for a client that starts a command instead of calling a remote URL. The package readme shows an mcpServers entry whose command is npx and whose args are mcp-remote plus the server URL.

The readme says --transport http-only uses only the HTTP transport. The readme also says Claude Desktop, Cursor, and Windsurf use this mcpServers shape for a local command.

Local command config

{
  "mcpServers": {
    "sunsetdiff": {
      "command": "npx",
      "args": [
        "mcp-remote",
        "https://sunsetdiff-api.onrender.com/mcp",
        "--transport",
        "http-only"
      ]
    }
  }
}

Sources: mcp-remote on npm , mcp-remote readme , checked October 23, 2026.

Registry manifest

server.json follows the MCP registry schema at https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json. The server name is com.sunsetdiff/sunsetdiff. The remote type is streamable-http. The URL is the endpoint above.

The registry's authentication docs say a domain name must be the reverse-DNS form of a domain you control. com.sunsetdiff is the reverse-DNS form of sunsetdiff.com. Publishing needs a person who can prove that domain, either with a file at https://sunsetdiff.com/.well-known/mcp-registry-auth or with a DNS TXT record on sunsetdiff.com. This site does not publish the server.

Sources: Publishing remote servers, Registry authentication, checked October 23, 2026.

Questions

Does the SunsetDiff MCP server need an API key?

No. The server is free and public. Do not send an API key.

What is the MCP endpoint?

The streamable HTTP endpoint is https://sunsetdiff-api.onrender.com/mcp. Setup for each client is on this page.

Which tools does it expose?

check_model, upcoming_shutdowns, migration_diff, and scan_text. The input schema for each tool is on this page.

Is this server listed in the official MCP registry?

The manifest is server.json. Its name is com.sunsetdiff/sunsetdiff. The registry accepts that name after a domain check for sunsetdiff.com. This page does not publish the server.