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.

UK Data: Software end-of-life dates

REMOTE · UKDATA.RELINESS.CO.UK

Release, support and end-of-life dates for about 490 languages, OSes, databases and frameworks

+3 this week 76 Trust /100

Last scanned (21 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Developer Tools

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 Security69
  • 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 check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
  • 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 Usability77
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 863 tokens (~143/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 Management47
  • Stability observed for 14 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
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 6 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 (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.

  • 21 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 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 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 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 14 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.

  • 12 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.

  • 10 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.

  • 8 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 7 Nov 26 69

    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://ukdata.reliness.co.uk/mcp/software-lifecycle

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=reliness.co.uk CN=WE1,O=Google Trust Services,C=US 4 Nov 2026 2 Feb 2027 ECDSA 256 ECDSA-SHA256 f1d4f4e9f24c919b0e13c306162294a4
SANs: reliness.co.uk, ukdata.reliness.co.uk, *.ukdata.reliness.co.uk
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 ukdata.reliness.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
reliness.co.uk. 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=31536000; includeSubDomains
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://ukdata.reliness.co.uk/mcp/software-lifecycle Verified 200
http (plaintext) http://ukdata.reliness.co.uk/mcp/software-lifecycle Served over HTTP 200
MCP tools · 6 exposed · ~863 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
eol_latest_release ~121

What is the latest version of a product right now? Returns the newest release cycle, its latest patch version and date, release date, support status and end-of-life date. Live data avoids out-of-date answers about "the latest Python/Node/PostgreSQL". Source: endoflife.date (community-maintained, typically refreshed daily); preview or beta releases are not included. (cost: 1 credit)

NameTypeReqDescription
productstring–string, required, endoflife.date product slug (e.g. python, nodejs, postgresql)

No output schema declared.

No examples provided.

eol_product_search ~144

Find the endoflife.date product slug for an everyday name or alias ("postgres", "k8s", "node", "windows server") and check whether a product is tracked at all. Matches names, labels and aliases and returns the best matches first. Use it before the other end-of-life tools. Source: endoflife.date product list (about 490 products); untracked software returns no match. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, matches to return, 1-50, default 10
querystring–string, required, product name or alias, 2-80 characters

No output schema declared.

No examples provided.

eol_products_by_category ~167

List the products endoflife.date tracks in one category: operating systems, databases, programming languages, frameworks, server applications, cloud services, applications, devices or standards. Returns each product slug, name, aliases and tags so you can then look up release dates. Source: endoflife.date; coverage is about 490 products and is not a full software inventory. (cost: 1 credit)

NameTypeReqDescription
categorystring–string, required, one of app, database, device, framework, lang, os, server-app, service, standard
limitstring–integer, optional, products to return, 1-100, default 25
offsetstring–integer, optional, skip this many products for paging, default 0

No output schema declared.

No examples provided.

eol_products_by_vendor_tag ~187

List the products endoflife.date tracks under one tag, usually a vendor (microsoft, amazon, google, oracle, red-hat), a family (linux-distribution) or a runtime (php-runtime, javascript-runtime). Answers "which Microsoft products have end-of-life dates" before you look up each one. Source: endoflife.date; tags are the project's own grouping (see eol_tags) and a vendor's list may be incomplete. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, products to return, 1-100, default 25
offsetstring–integer, optional, skip this many products for paging, default 0
tagstring–string, required, endoflife.date tag (e.g. microsoft, amazon, linux-distribution); see eol_tags

No output schema declared.

No examples provided.

eol_tags ~88

List every tag endoflife.date uses to group products: vendors (microsoft, amazon, google), families (linux-distribution) and runtimes (php-runtime, java-runtime). Use it to find a valid tag for eol_products_by_vendor_tag. Source: endoflife.date; tags are the project's own grouping, not an official vendor list. (cost: 1 credit)

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

eol_unsupported_releases ~156

Which versions of a product are already end of life? Lists the release cycles past their end-of-life date, newest first, with the end-of-life date, the last patch version and whether extended (often paid) support is still available. Useful for security audits and spotting outdated versions in an estate. Source: endoflife.date (community-maintained); it reports published dates, not whether a given install is patched. (cost: 1 credit)

NameTypeReqDescription
limitstring–integer, optional, cycles to return, newest first, 1-100, default 25
productstring–string, required, endoflife.date product slug (e.g. php, python, nodejs)

No output schema declared.

No examples provided.

Install

How do I install the UK Data: Software end-of-life dates MCP server?

UK Data: Software end-of-life dates is a hosted endpoint at https://ukdata.reliness.co.uk/mcp/software-lifecycle, 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 · ukdata.reliness.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-reliness-software-lifecycle 'https://ukdata.reliness.co.uk/mcp/software-lifecycle'
Common questions

What is the UK Data: Software end-of-life dates MCP server?

UK Data: Software end-of-life dates is an MCP server listed in the public MCP registry as uk.co.reliness/software-lifecycle. Release, support and end-of-life dates for about 490 languages, OSes, databases and frameworks. This page covers its hosted endpoint (https://ukdata.reliness.co.uk/mcp/software-lifecycle).

Is the UK Data: Software end-of-life dates MCP server safe to use?

UK Data: Software end-of-life dates scores 76 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 UK Data: Software end-of-life dates MCP server expose?

UK Data: Software end-of-life dates exposes 6 tools: eol_latest_release, eol_unsupported_releases, eol_products_by_category, eol_products_by_vendor_tag, eol_product_search, eol_tags. Their descriptions and schemas cost roughly 863 tokens of context every time the server is loaded.

Does the UK Data: Software end-of-life dates MCP server require authentication?

No. We connected to UK Data: Software end-of-life dates without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the UK Data: Software end-of-life dates MCP server still maintained?

UK Data: Software end-of-life dates 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 UK Data: Software end-of-life dates MCP server?

VerifyMCP ran 13 checks on UK Data: Software end-of-life dates, 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.