# 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

- Trust score: 76/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `ukdata.reliness.co.uk`: 76/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle.md), [page](https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle)

## Channel facts

- Endpoint: `https://ukdata.reliness.co.uk/mcp/software-lifecycle`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.5.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 69/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS check failed: the endpoint is reachable over plaintext HTTP.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 47/100
  - Stability observed for 14 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## 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.

### Claude

```bash
claude mcp add --transport http uk-co-reliness-software-lifecycle 'https://ukdata.reliness.co.uk/mcp/software-lifecycle'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-reliness-software-lifecycle": {
      "url": "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-reliness-software-lifecycle": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-reliness-software-lifecycle]
url = "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-reliness-software-lifecycle": {
      "type": "remote",
      "url": "https://ukdata.reliness.co.uk/mcp/software-lifecycle",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-reliness-software-lifecycle --url 'https://ukdata.reliness.co.uk/mcp/software-lifecycle' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-reliness-software-lifecycle:
    url: "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-reliness-software-lifecycle": {
      "Transport": "http",
      "Url": "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-reliness-software-lifecycle -t streamable-http -u 'https://ukdata.reliness.co.uk/mcp/software-lifecycle'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-reliness-software-lifecycle": {
      "type": "http",
      "url": "https://ukdata.reliness.co.uk/mcp/software-lifecycle"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 76, +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.

### 2026-11-18 (score 75, +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.

### 2026-11-16 (score 74, +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.

### 2026-11-14 (score 73, +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.

### 2026-11-12 (score 72, +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.

### 2026-11-10 (score 71, +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.

### 2026-11-08 (score 70, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-07 (score 69)

First indexed and scored.

## MCP tools (6)

### `eol_latest_release` (~121 tokens)

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)

Input parameters:

- `product` (string): string, required, endoflife.date product slug (e.g. python, nodejs, postgresql)

### `eol_unsupported_releases` (~156 tokens)

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)

Input parameters:

- `limit` (string): integer, optional, cycles to return, newest first, 1-100, default 25
- `product` (string): string, required, endoflife.date product slug (e.g. php, python, nodejs)

### `eol_products_by_category` (~167 tokens)

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)

Input parameters:

- `category` (string): string, required, one of app, database, device, framework, lang, os, server-app, service, standard
- `limit` (string): integer, optional, products to return, 1-100, default 25
- `offset` (string): integer, optional, skip this many products for paging, default 0

### `eol_products_by_vendor_tag` (~187 tokens)

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)

Input parameters:

- `limit` (string): integer, optional, products to return, 1-100, default 25
- `offset` (string): integer, optional, skip this many products for paging, default 0
- `tag` (string): string, required, endoflife.date tag (e.g. microsoft, amazon, linux-distribution); see eol_tags

### `eol_product_search` (~144 tokens)

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)

Input parameters:

- `limit` (string): integer, optional, matches to return, 1-50, default 10
- `query` (string): string, required, product name or alias, 2-80 characters

### `eol_tags` (~88 tokens)

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)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle#diagnostics

## Score history

- 2026-11-21: 76
- 2026-11-20: 75
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 72
- 2026-11-11: 71
- 2026-11-10: 71
- 2026-11-09: 70
- 2026-11-08: 70
- 2026-11-07: 69

## 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.

## Links

- Remote endpoint: https://ukdata.reliness.co.uk/mcp/software-lifecycle
- Website: https://ukdata.reliness.co.uk/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-reliness-software-lifecycle/mcp-software-lifecycle
