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.

EOL Watch

REMOTE · EOLWATCH.DEV

Cloud retirements, end of support dates and IaC breaking changes for Azure, AWS, GCP and OCI.

Available components

+3 this week 75 Trust /100

Last scanned (12 hours ago)

Scores higher than 62% of remote servers

Reachable. Last reached 21 Nov 2026.

Category CI/CD and DevOps

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 Security80
  • 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
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 1415 tokens (~235/item across 6 items; 6 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 Management27
  • Stability observed for 8 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 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
What we tested

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 →

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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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 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.

  • 16 Nov 26 +1

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

  • 14 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 13 Nov 26 71

    First indexed and scored.

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://eolwatch.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=eolwatch.dev CN=YR2,O=Let's Encrypt,C=US 13 Nov 2026 11 Feb 2027 RSA 2048 SHA256-RSA 5c3bcb8d40718c2bc8dd0d43bc988d53b18
SANs: eolwatch.dev
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of eolwatch.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
eolwatch.dev. 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
Header Value
strict-transport-security max-age=63072000
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob:; font-src 'self'; connect-src 'self'; worker-src 'self' blob:; object-src 'none'; base-uri 'self'; form-action 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://eolwatch.dev/mcp Verified 200
http (plaintext) http://eolwatch.dev/mcp HTTPS enforced 308 https://eolwatch.dev/mcp
MCP tools · 6 exposed · ~1,285 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_item ~132

Returns one published item in full: its dates, summary, impact, migration path, replacement, affected versions and sources, as Markdown and as structured data. Use it with the slug of a row that search_items returned; the address of the item page or its short address works too. An unknown slug is answered as an error, and so is a withdrawn item, with the notice that it was withdrawn.

NameTypeReqDescription
slugstringyesSlug of the item, as in the slug field of a row. The address of the item page, of its Markdown or JSON form, or its short address is accepted too.
NameTypeReqDescription
affected_versionsarrayyesVersions affected. Array in JSON, joined with "; " in CSV.
announced_date–yesDate the vendor announced the change (YYYY-MM-DD), or null when not stated.
categorystringyesKind of thing affected, for example service, runtime, kubernetes or database.
cloudstringyesCloud the item belongs to: azure, aws, gcp, oci or multi.
created_atstringyesTimestamp (ISO 8601, UTC) when the item was first published here.
effective_date–yesDate the change takes effect (YYYY-MM-DD), or null when not announced. For month, quarter and year precision this is the first day of the period.
effective_precisionstringyesHow exact effective_date is: day, month, quarter or year.
estate_check–yesWhat the estate check reads to detect resources this item affects, as the item page lists it. Null when the item has no estate check rules. The check runs in the browser of the reader: no address of…
extra_source_urlsarrayyesAdditional sources: official pages, or an endoflife.date page. Array in JSON, joined with "; " in CSV.
impactstringyesWhat stops working and who is affected.
json_urlstringyesThe same item as JSON.
last_checked_atstringyesTimestamp (ISO 8601, UTC) of the last successful recheck against the source.
markdown_urlstringyesThe same item as Markdown.
migration_pathstringyesSteps to take before the effective date. May contain Markdown.
replacementstring|nullyesRecommended replacement, or null when the vendor names none.
servicestringyesDisplay name of the affected service.
service_slugstringyesURL-safe identifier of the service.
short_urlstringyesShort address of the item page. It redirects to url.
slugstringyesStable identifier of the item. Never changes once published.
source_notestring|nullyesA note on the address of the source. Set when the id of an Azure Updates address names a day, effective_date has day precision and the two days differ. Null when this check does not apply or finds no…
source_urlstringyesPage the item was verified against: an official vendor page, or the endoflife.date page for the few products where it is the only source of the date.
summarystringyesOne or two plain sentences describing the change.
titlestringyesShort headline of the lifecycle change.
typestringyesKind of change: retirement, end_of_support or breaking_change.
updated_atstringyesTimestamp (ISO 8601, UTC) of the last change to the item.
urlstringyesPage for this item on the site.
vendor_refstring|nullyesVendor reference for the announcement, or null.

No examples provided.

get_provider_changes ~178

Returns what the page of one provider, tool or module shows: the range of releases that is tracked, the summary sentence, the notices and the breaking changes of each release that lists any. Send from with the version in use to get only the releases above it. Read the notices before you call a range clear: they say which releases were not tracked or whose release notes were not read.

NameTypeReqDescription
fromstring–The version in use, or a version constraint, of at most 64 characters. Only releases newer than that version are in the answer. For a constraint, that version is the lowest one the constraint allows.…
providerstringyesKey of the provider, tool or module, as in the key field of list_providers.
NameTypeReqDescription
as_ofstringyesThe UTC day (YYYY-MM-DD) every value that depends on the day was counted for.
breaking_releases_last_12_monthsintegeryesNumber of tracked stable releases published in the twelve months up to the as_of day whose release notes were read and list at least one breaking change.
cloudstringyesCloud the entry belongs to.
counted_sincestring|nullyesSet when the tracked releases start less than twelve months before the as_of day: the oldest tracked version, where that count really starts. Null otherwise.
fromstring|nullyesThe version in use that the answer starts from, as plain semver. For a constraint it is the lowest version the constraint allows. Only newer releases are in the answer. Null when no version was given…
json_urlstringyesThe same page as JSON.
keystringyesKey of the entry: the provider key (for example azurerm) or the name of the module. It is the last part of its page address.
kindstringyesWhat the entry is: a Terraform provider, a tool or language, or a module.
latest_confirmedbooleanyesTrue when the tracked list holds every stable release from oldest_tracked_version on, so latest_version is the latest stable release. False when it is only the newest release tracked here: a newer on…
latest_date–yesDay that release was published (YYYY-MM-DD), or null when it is not known.
latest_notes_readboolean|nullyesFalse when the newest release is known from the Terraform Registry only and has no GitHub release: its release notes were not read. Null when no release is loaded.
latest_versionstring|nullyesThe newest tracked stable release, without a leading v. Null when none is loaded.
markdown_urlstringyesThe same page as Markdown.
namestringyesDisplay name of the entry.
namespacestringyesWhere the entry is published: its address in the Terraform Registry, or its GitHub repository when it is not in the registry.
noticesarrayyesThe sentences that go with the summary: a range that reaches below the oldest tracked release and versions whose release notes were not read, both word for word from the page, and a from value that c…
oldest_tracked_versionstring|nullyesThe oldest tracked stable release. Releases before it were not read. Null when none is loaded.
registry_url–yesPage of a module in the Terraform Registry. Null for providers and tools.
releasesarrayyesThe releases in the answered range whose release notes were read and list a breaking change, newest first.
repo_urlstringyesThe GitHub repository whose releases are read.
short_urlstringyesShort address of the page for this answer. It redirects to url.
statestringyesHow the answer was chosen. all: no version was given, so every tracked release whose release notes were read and list a breaking change is in it. range: the tracked releases newer than from whose rel…
subjectstring|nullyesWhat a module deploys, as the Azure Verified Modules index names it. Null for providers and tools.
summarystringyesThe summary sentence of the page for this answer.
unread_versionsarrayyesThe versions in the answered range whose release notes were not read, newest first. Nothing is known about breaking changes in them, and they are not in releases.
urlstringyesPage of the entry on the site.

No examples provided.

list_providers ~46

Lists the infrastructure as code providers, tools and modules whose releases are read for breaking changes, each with its newest tracked release. Use it to find the key that get_provider_changes takes.

Input schema present but exposes no named parameters.

NameTypeReqDescription
as_ofstringyesThe UTC day (YYYY-MM-DD) every value that depends on the day was counted for.
countintegeryesNumber of entries in this answer.
generated_atstringyesMoment this answer was built (ISO 8601, UTC).
licenseobjectyesThe license of the data.
providersarrayyesThe providers and tools, then the modules, in the order of the site.
siteobjectyesThe site the data comes from.

No examples provided.

list_services ~106

Lists every service that has a published item, with its number of items, how many of them are upcoming and the date of the next one. Use it to find the slug of a service before you filter search_items by service, or to see what is tracked for one cloud.

NameTypeReqDescription
cloudstring–Only the services of this cloud.
qstring–Search text of at most 100 characters. Every word must occur in the name or the slug of the service.
NameTypeReqDescription
as_ofstringyesThe UTC day (YYYY-MM-DD) every value that depends on the day was counted for.
countintegeryesNumber of services in this answer.
generated_atstringyesMoment this answer was built (ISO 8601, UTC).
licenseobjectyesThe license of the data.
servicesarrayyesThe services, by cloud and then by name.
siteobjectyesThe site the data comes from.

No examples provided.

recent_changes ~118

Returns one page of the changelog of EOL Watch, newest first: items added, effective dates changed, items updated and items withdrawn. Use it to see what changed since you last read the data.

NameTypeReqDescription
changestring–Only this kind of change: added, date_changed, updated or withdrawn.
cloudstring–Only changes to items of this cloud.
pageinteger–Page of the changelog, from 1. One page holds 50 changes, and a page past the end is the last page.
NameTypeReqDescription
countintegeryesNumber of changes in this answer.
generated_atstringyesMoment this answer was built (ISO 8601, UTC).
itemsarrayyesThe changes of this page, newest first.
licenseobjectyesThe license of the data.
pageintegeryesThe page this answer holds. A page past the end is the last page.
pagesintegeryesNumber of pages.
queryobjectyesThe query as it was understood.
siteobjectyesThe site the data comes from.
totalintegeryesNumber of changes that match the query.

No examples provided.

search_items ~705

Lists published items of EOL Watch: retirements, end of support dates and breaking changes. Filter by cloud, kind of change, category, service, search text and effective date. Without status it lists upcoming items only, soonest first. To list ended items, breaking changes in effect or every item, send status ended, in_effect or all. Use it for questions such as what retires in the next 90 days or what is due for one service. It returns one page of compact rows as a Markdown table and as structured data, with the UTC day the countdowns were counted for (as_of). Call get_item for the full text of one item. This tool does not check an estate: that check runs in the reader's browser only.

NameTypeReqDescription
categorystring–Category group, as in the address of a category page.
cloudarray–Clouds to include. Leave it out for every cloud.
dirstring–asc (the default) or desc. The added order ignores it.
fromstring–Earliest effective_date to include (YYYY-MM-DD). An item without a date never matches. A month, quarter or year is compared by its first day; use within_days for what is due or what ended.
limitinteger–Most items in one answer: 1 to 100, 25 by default.
offsetinteger–Number of matching items to skip. Send the next_offset of an answer to get the next page.
qstring–Search text of at most 100 characters. Every word must occur in the title, the summary, the service, the slug or an affected version.
servicestring–Service slug of at most 80 characters, as in the service_slug field. Two clouds can use the same slug, so send cloud with it.
sortstring–date (the default): by effective_date, items without a date last; a list of ended items or of changes in effect (status=ended, status=in_effect) is ordered by the last day of each effective period. a…
statusstring–upcoming (the default): items whose effective period is not over, including items without a date. ended: retirements and end of support dates whose whole period is over. in_effect: breaking changes w…
tostring–Latest effective_date to include (YYYY-MM-DD). An item without a date never matches. A month, quarter or year is compared by its first day; use within_days for what is due or what ended.
typearray–Kinds of change to include. Leave it out for every kind.
within_daysinteger–Only items at most this many days from the as_of day (1 to 3650). With status upcoming: items due in the next N days, including an item whose month, quarter or year has started and is not over. With…
NameTypeReqDescription
as_ofstringyesThe UTC day (YYYY-MM-DD) every value that depends on the day was counted for.
countintegeryesNumber of items in this answer.
generated_atstringyesMoment this answer was built (ISO 8601, UTC).
itemsarrayyesThe items of this page, as compact rows. Call get_item with the slug of a row for its full record.
licenseobjectyesThe license of the data.
limitintegeryesMost items one answer holds for this query.
next_offset–yesThe offset of the next page, or null when this answer holds the last match.
next_url–yesAddress of the next page of this list, at the data address, or null when this answer holds the last match.
offsetintegeryesNumber of matching items skipped before the first of this answer.
queryobjectyesThe query as it was understood: every parameter with the value that was used.
siteobjectyesThe site the data comes from.
status_countsobjectyesNumber of items the query matches in each status, with every other parameter as it was used. An empty list of upcoming items can stand next to items that have ended or are in effect: send status=all…
totalintegeryesNumber of items that match the query.

No examples provided.

Install

How do I install the EOL Watch MCP server?

EOL Watch is a hosted endpoint at https://eolwatch.dev/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 · eolwatch.dev

# add to Claude Code
claude mcp add --transport http dev-eolwatch-eolwatch 'https://eolwatch.dev/mcp'
Common questions

What is the EOL Watch MCP server?

EOL Watch is an MCP server listed in the public MCP registry as dev.eolwatch/eolwatch. Cloud retirements, end of support dates and IaC breaking changes for Azure, AWS, GCP and OCI. This page covers its hosted endpoint (https://eolwatch.dev/mcp).

Is the EOL Watch MCP server safe to use?

EOL Watch scores 75 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 EOL Watch MCP server expose?

EOL Watch exposes 6 tools: search_items, get_item, list_services, list_providers, get_provider_changes, recent_changes. Their descriptions and schemas cost roughly 1,285 tokens of context every time the server is loaded.

Does the EOL Watch MCP server require authentication?

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

Is the EOL Watch MCP server still maintained?

EOL Watch 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 EOL Watch MCP server?

VerifyMCP ran 13 checks on EOL Watch, 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.