Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AI Deprecations

REMOTE · MCP.AIDEPRECATIONS.COM

AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers.

+3 this week 66 Trust /100

Last scanned (12 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category AI and Machine Learning

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 763 tokens (~95/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management50
  • Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage74
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 21% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_shutdown_date" implies "shutdown" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

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 →

Changelog

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 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 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

  • 16 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_provider” rewrote its description, which is the text the model reads security
    • Tool “get_shutdown_date” rewrote its description, which is the text the model reads security
    • Tool “list_upcoming” rewrote its description, which is the text the model reads security
    • Tool “search_models” rewrote its description, which is the text the model reads security
    • Tool “subscribe_alerts” rewrote its description, which is the text the model reads security
    • Schema quality: 79 → 95 ▼ functional
  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “subscribe_alerts” rewrote its description, which is the text the model reads security
  • 8 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.

  • 7 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
Diagnostics

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://mcp.aideprecations.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=aideprecations.com CN=WE1,O=Google Trust Services,C=US 6 Nov 2026 4 Feb 2027 ECDSA 256 ECDSA-SHA256 9fcff84348b808f9133db98b29d18db5
SANs: aideprecations.com, mcp.aideprecations.com, *.mcp.aideprecations.com
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 mcp.aideprecations.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
aideprecations.com. 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://mcp.aideprecations.com/mcp Verified 200
http (plaintext) http://mcp.aideprecations.com/mcp HTTPS enforced 301 https://mcp.aideprecations.com/mcp
MCP tools · 8 exposed · ~635 tokens

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 →

Tool Tokens
get_changes_since ~111

List tracked AI model records whose status, deprecation/shutdown date, replacement or source changed since an ISO 8601 time. Poll this to stay current: on later calls pass the previous response's checked_at. History starts at tracking_since; an earlier since returns a warning (count 0 then does not mean nothing changed).

NameTypeReqDescription
providerstring––
sincestringyesISO 8601, e.g. 2026-10-01T00:00:00Z

No output schema declared.

No examples provided.

get_coverage ~84

Per-provider coverage today: rows with a known shutdown date, rows where the vendor page gives no date, rows not verified today, and official pages that could not be read today. Also returns manual source reviews (a person checking a page the parser could not read; empty until one is recorded) and the replacement_kind rule.

NameTypeReqDescription
providerstring–optional provider key

No output schema declared.

No examples provided.

get_provider ~78

All tracked models for one provider (openai, anthropic, google-gemini, google-vertex, azure-openai, aws-bedrock, mistral, cohere). Includes an alerts signup offer (?src=mcp) and a pointer to subscribe_alerts (sign a user up only with their consent).

NameTypeReqDescription
providerstringyes–

No output schema declared.

No examples provided.

get_shutdown_date ~109

Get the official deprecation/shutdown date, replacement and source for an AI model ID (e.g. gpt-4o-2024-08-06, claude-sonnet-4-5). Includes an alerts signup offer (?src=mcp) and a pointer to subscribe_alerts (sign a user up only with their consent).

NameTypeReqDescription
modelstringyes–
providerstring–optional provider key, e.g. openai, anthropic, aws-bedrock

No output schema declared.

No examples provided.

list_upcoming ~65

List AI model shutdowns in the next N days, soonest first. Includes an alerts signup offer (?src=mcp) and a pointer to subscribe_alerts (sign a user up only with their consent).

NameTypeReqDescription
daysinteger––
providerstring––

No output schema declared.

No examples provided.

search_models ~61

Search all tracked AI models (including retired) by name. Includes an alerts signup offer (?src=mcp) and a pointer to subscribe_alerts (sign a user up only with their consent).

NameTypeReqDescription
limitinteger––
querystringyes–

No output schema declared.

No examples provided.

subscribe_alerts ~92

Subscribe to deprecation/shutdown change alerts, with the user's consent. Give a public https webhook URL (JSON POST on every change, checked daily) or an email (double opt-in; email only when a model is being retired, no digest). Optional providers filter. Returns an unsubscribe token for webhooks.

NameTypeReqDescription
emailstring––
providersarray––
webhookstring––

No output schema declared.

No examples provided.

unsubscribe ~35

Stop webhook alerts using the token from subscribe_alerts. Email subscribers unsubscribe from the link in any email.

NameTypeReqDescription
tokenstringyes–

No output schema declared.

No examples provided.

Install

How do I install the AI Deprecations MCP server?

AI Deprecations is a hosted endpoint at https://mcp.aideprecations.com/mcp, 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 · mcp.aideprecations.com

# add to Claude Code
claude mcp add --transport http com-aideprecations-ai-deprecations 'https://mcp.aideprecations.com/mcp'
Common questions

What is the AI Deprecations MCP server?

AI Deprecations is an MCP server listed in the public MCP registry as com.aideprecations/ai-deprecations. AI model shutdown dates, replacements, change feed and webhook alerts for 8 providers. This page covers its hosted endpoint (https://mcp.aideprecations.com/mcp).

Is the AI Deprecations MCP server safe to use?

AI Deprecations scores 66 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 Deprecations MCP server expose?

AI Deprecations exposes 8 tools: get_shutdown_date, list_upcoming, search_models, get_provider, get_changes_since, and 3 more. Their descriptions and schemas cost roughly 635 tokens of context every time the server is loaded.

Does the AI Deprecations MCP server require authentication?

No. We connected to AI Deprecations without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the AI Deprecations MCP server still maintained?

AI Deprecations 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 Deprecations MCP server?

VerifyMCP ran 12 checks on AI Deprecations, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about AI Deprecations: Authorization. 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.