AI model deprecation and retirement dates, by provider
REMOTE · REFERENCESOURCE.ORG
Is this AI model id retired, when does it shut off, and what does its provider say replaces it?
Available components
Last scanned (23 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 1136 tokens (~378/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 69
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://referencesource.org/mcp/models
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 284c538e5c38c80d0eb8e23b1bba01ab |
| SANs: referencesource.org | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| referencesource.org. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://referencesource.org/mcp/models | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/models | HTTPS enforced | 301 | https://referencesource.org/mcp/models |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
model_status Is this AI model id retired, and when does it shut off? ~317
Ask this before you pin, recommend or migrate off a model id. Give the id exactly as it goes in the config — "gpt-4o", "anthropic.claude-3-haiku-20240307-v1:0", "gemini-1.5-pro-002", "mistral-large-2407" — and get whether it is retired, the shutdown date the provider published, the replacement the provider names, and a verbatim quote of the page that says so. Where several hosts sell the same id you get every one of them, and earliest_announced_shutdown is the date a migration actually has to meet: on 34 records a second host switches the model off EARLIER than the record's primary source does. An id we hold nothing for returns found: false and no date, which means not in our records, never "still supported".
| Name | Type | Req | Description |
|---|---|---|---|
| model_id | string | yes | The model id as the provider writes it. Matched exactly, then case-insensitively, then against the alternative name a record's own id prints, then against the human-readable model name. Never as a su… |
| provider | string | – | Optional. Narrow to one provider's schedule, matched case-insensitively as a substring of the provider name ("bedrock", "azure", "groq"). Leave it out to see every host's clock for this id, which is… |
| Name | Type | Req | Description |
|---|---|---|---|
| answer | string | – | One sentence, computed here from the records below, for a caller that needs a line rather than a structure. |
| as_of | string | yes | The UTC date every "has it passed" answer here was computed against. |
| coverage | string | yes | – |
| earliest_announced_shutdown | object | – | The soonest shutdown date any source states for this id, with the page and quote that state it. THE FIGURE TO PLAN AGAINST. Floors and no-date sentences are excluded; null where no source gives a dat… |
| found | boolean | yes | – |
| matched_on | string | – | Which rung of the ladder matched. Absent when nothing did. |
| model_id_asked | string | yes | – |
| models | array | – | – |
| records_found | integer | yes | – |
| register | object | – | – |
| similar_ids_in_our_records | array | – | Only on a miss. Ids in this register containing the string you asked about. NOT AN ANSWER about any of them — no date and no status is attached, because you did not ask about them. Call model_status… |
No examples provided.
upcoming_retirements Which AI models shut off in the next N days? ~251
What is about to break? Lists the model ids whose provider has published a shutdown date inside the next N days, soonest first, each with the provider, the replacement it names and a verbatim quote. Use it to sweep a codebase's pins before they bite, or to see what a quarter's migration work looks like. Optionally narrowed to one provider. Dates a provider printed as a floor ("not sooner than") are deliberately left out and counted in the response, because such a model could go years later and listing it here would be a guess.
| Name | Type | Req | Description |
|---|---|---|---|
| days | integer | – | How far ahead to look, in days from today (UTC). 90 by default. Pass 0 to get only what is already past its date. |
| include_already_retired | boolean | – | Include models whose shutdown date has already passed. False by default: this tool answers "what is coming". Set true to audit pins that are already dead. |
| limit | integer | – | How many to return, 1–20. Default 20. |
| provider | string | – | Optional case-insensitive substring of the provider name ("openai", "bedrock", "azure", "together"). |
| Name | Type | Req | Description |
|---|---|---|---|
| as_of | string | yes | – |
| coverage | string | yes | – |
| excluded_floor_dates | integer | – | How many records fell in the window only on a date the provider printed as a floor ("not sooner than"), and were therefore left out. Reported so the omission is visible instead of silent. |
| from | string | yes | – |
| models | array | yes | – |
| models_matched | integer | yes | – |
| models_returned | integer | – | – |
| register | object | – | – |
| to | string | yes | – |
| window_days | integer | yes | – |
No examples provided.
verify_quote Check a claimed model retirement date against the register ~302
Is this right? Check a claim about a model id — its shutdown date, its lifecycle status, the replacement it was given — against the provider's own record instead of trusting it. Says whether the claim equals a stored value, appears only in the verbatim quote, or differs (and then what the record says instead). A model retirement date recalled from memory is exactly the kind of confident wrong answer that leaves a config pinned to something that stopped answering.
| Name | Type | Req | Description |
|---|---|---|---|
| claimed_value | string | yes | The value to check, exactly as claimed, e.g. "Terminated" or "2026-10-29". |
| field | string | – | Which field the claim is about, if you know it. Without it, every stored field of the record is checked. |
| model_id | string | yes | The model id the claim is about, matched the same way model_status matches it. Where more than one record holds the id, narrow with `provider` or `record_id` — the check is refused rather than run ag… |
| provider | string | – | Optional case-insensitive substring of the provider name, to pick which host's record the claim is checked against. |
| record_id | string | – | Optional. The exact record to check against, as model_status returns it in record_id. Settles the case where one provider holds the same id twice (AWS Bedrock publishes two schedules for claude-3-hai… |
| Name | Type | Req | Description |
|---|---|---|---|
| attestation | string | yes | – |
| claimed_value | string | yes | – |
| in_source_quote | boolean | – | – |
| match | object | – | – |
| quote_source | string | – | – |
| record | object | – | – |
| stored_values | object | – | – |
| verdict | string | yes | matches_record: the claim equals a stored value (match.match_type says how exactly). matches_quote: it appears in the verbatim source quote but is not a stored value. differs: the record was found an… |
No examples provided.
How do I install the AI model deprecation and retirement dates, by provider MCP server?
AI model deprecation and retirement dates, by provider is a hosted endpoint at https://referencesource.org/mcp/models, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · referencesource.org
claude mcp add --transport http org-referencesource-ai-model-retirement-dates 'https://referencesource.org/mcp/models'
What is the AI model deprecation and retirement dates, by provider MCP server?
AI model deprecation and retirement dates, by provider is an MCP server listed in the public MCP registry as org.referencesource/ai-model-retirement-dates. Is this AI model id retired, when does it shut off, and what does its provider say replaces it? This page covers its hosted endpoint (https://referencesource.org/mcp/models).
Is the AI model deprecation and retirement dates, by provider MCP server safe to use?
AI model deprecation and retirement dates, by provider scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the AI model deprecation and retirement dates, by provider MCP server expose?
AI model deprecation and retirement dates, by provider exposes 3 tools: model_status, upcoming_retirements, verify_quote. Their descriptions and schemas cost roughly 870 tokens of context every time the server is loaded.
Does the AI model deprecation and retirement dates, by provider MCP server require authentication?
No. We connected to AI model deprecation and retirement dates, by provider without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the AI model deprecation and retirement dates, by provider MCP server still maintained?
AI model deprecation and retirement dates, by provider is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the AI model deprecation and retirement dates, by provider MCP server?
VerifyMCP ran 13 checks on AI model deprecation and retirement dates, by provider, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.