# Which base images in this Dockerfile are out of support? (remote · referencesource.org)

Which Python, Node, Debian, Alpine, Go, Postgres or Ubuntu base images in this Dockerfile are dead?

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `referencesource.org`: 72/100 (this document), [markdown](https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images.md), [page](https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images)

## Channel facts

- Endpoint: `https://referencesource.org/mcp/images`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.1.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**: 74/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 is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 679 tokens (~339/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Which base images in this Dockerfile are out of support? MCP server?

Which base images in this Dockerfile are out of support? is a hosted endpoint at https://referencesource.org/mcp/images, 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 org-referencesource-dockerfile-base-image-end-of 'https://referencesource.org/mcp/images'
```

### Cursor

```json
{
  "mcpServers": {
    "org-referencesource-dockerfile-base-image-end-of": {
      "url": "https://referencesource.org/mcp/images"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "org-referencesource-dockerfile-base-image-end-of": {
      "type": "http",
      "url": "https://referencesource.org/mcp/images"
    }
  }
}
```

### Codex

```toml
[mcp_servers.org-referencesource-dockerfile-base-image-end-of]
url = "https://referencesource.org/mcp/images"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "org-referencesource-dockerfile-base-image-end-of": {
      "type": "remote",
      "url": "https://referencesource.org/mcp/images",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add org-referencesource-dockerfile-base-image-end-of --url 'https://referencesource.org/mcp/images' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  org-referencesource-dockerfile-base-image-end-of:
    url: "https://referencesource.org/mcp/images"
```

### Netclaw

```json
{
  "McpServers": {
    "org-referencesource-dockerfile-base-image-end-of": {
      "Transport": "http",
      "Url": "https://referencesource.org/mcp/images"
    }
  }
}
```

### Vellum

```bash
assistant mcp add org-referencesource-dockerfile-base-image-end-of -t streamable-http -u 'https://referencesource.org/mcp/images'
```

### Other

```json
{
  "mcpServers": {
    "org-referencesource-dockerfile-base-image-end-of": {
      "type": "http",
      "url": "https://referencesource.org/mcp/images"
    }
  }
}
```

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 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-18 (score 71, +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.

### 2026-11-17 (score 70, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-16 (score 70)

First indexed and scored.

## MCP tools (2)

### `check_dockerfile` (~220 tokens)

Which base images in this Dockerfile are out of support?

Paste a whole Dockerfile. Covers releases of Alpine Linux, Debian, Go, Node.js, PostgreSQL, Python and Ubuntu. Returns every FROM line whose base image is one this register holds, with that release's end-of-active-support and end-of-security-support dates, whether it is past either one today, and a verbatim quote of the vendor's own published line. Every FROM line it could NOT answer for — another product, a `latest`, floating or build-argument tag, a bare digest, an earlier build stage — comes back in `not_in_our_records` or `unresolvable` with the reason in words, and is counted in `images_unresolved`. An empty `out_of_support` list with a non-zero `images_unresolved` does NOT mean the file is clean.

Input parameters:

- `dockerfile` (string, required): The Dockerfile text. Multi-stage files, `--platform` flags, `AS` stage names, comments, registry prefixes and digest pins are all handled; nothing else in the file is read.

Output parameters:

- `coverage` (string)
- `from_lines` (integer): FROM lines found in the file.
- `images_checked` (integer): FROM lines matched to a release in this register.
- `images_unresolved` (integer): FROM lines not checked. See not_in_our_records and unresolvable.
- `not_in_our_records` (array): FROM lines this tool could not answer for. Read this before reporting a Dockerfile clean: these lines were NOT checked, which is not the same as being in support.
- `out_of_support` (array): Checked images past end of security support, soonest-expired first.
- `past_active_support` (array): Checked images still getting security fixes but no longer bug fixes.
- `register` (object)
- `supported` (array): Checked images inside both windows.
- `unresolvable` (array): FROM lines this tool could not answer for. Read this before reporting a Dockerfile clean: these lines were NOT checked, which is not the same as being in support.
- `verdict` (string): One sentence. Always says how many lines were not checked.

### `release_support_status` (~257 tokens)

Is this release still supported?

One release, without a Dockerfile. Covers Alpine Linux, Debian, Go, Node.js, PostgreSQL, Python and Ubuntu. Give a product and a release — a number like "3.9" or "22.04", a major like Node's "18" or PostgreSQL's "16", or a codename like "jammy" or "bookworm" — and get its release date, its end of active support, its end of security support, the paid extended window where there is one, and a verbatim quote of the vendor's own published line. A release this register does not hold returns found: false rather than a guess.

Input parameters:

- `product` (string, required): One of Alpine Linux, Debian, Go, Node.js, PostgreSQL, Python and Ubuntu, case-insensitive; "node", "nodejs", "golang", "postgres" and "alpine" are accepted too.
- `release` (string, required): "3.9", "3.11.9", "22.04", a major such as Node's "18" or "v18.17.0" or PostgreSQL's "16", or a codename such as "jammy" or "bookworm".

Output parameters:

- `coverage` (string)
- `found` (boolean)
- `newest_supported_release_we_hold` (string): OURS, computed from these records; no source here names a successor.
- `note` (string)
- `products_we_hold` (array)
- `register` (object)
- `release` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images#diagnostics

## Score history

- 2026-11-21: 72
- 2026-11-20: 71
- 2026-11-19: 71
- 2026-11-18: 71
- 2026-11-17: 70
- 2026-11-16: 70

## Common questions

### What is the Which base images in this Dockerfile are out of support? MCP server?

Which base images in this Dockerfile are out of support? is an MCP server listed in the public MCP registry as org.referencesource/dockerfile-base-image-end-of-support. Which Python, Node, Debian, Alpine, Go, Postgres or Ubuntu base images in this Dockerfile are dead? This page covers its hosted endpoint (https://referencesource.org/mcp/images).

### Is the Which base images in this Dockerfile are out of support? MCP server safe to use?

Which base images in this Dockerfile are out of support? scores 72 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 Which base images in this Dockerfile are out of support? MCP server expose?

Which base images in this Dockerfile are out of support? exposes 2 tools: check_dockerfile, release_support_status. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.

### Does the Which base images in this Dockerfile are out of support? MCP server require authentication?

No. We connected to Which base images in this Dockerfile are out of support? without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Which base images in this Dockerfile are out of support? MCP server still maintained?

Which base images in this Dockerfile are out of support? 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 Which base images in this Dockerfile are out of support? MCP server?

VerifyMCP ran 13 checks on Which base images in this Dockerfile are out of support?, 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://referencesource.org/mcp/images
- Website: https://referencesource.org/software-end-of-support
- Changelog RSS feed: https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images.xml
- Changelog JSON feed: https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images.json
- HTML version of this page: https://verifymcp.io/servers/org-referencesource-dockerfile-base-image-end-of-support/mcp-images
