Skip to content

Which base images in this Dockerfile are out of support? MCP server

org.referencesource/dockerfile-base-image-end-of-supportreferencesource.orgstreamable-httpv1.1.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 0
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the Which base images in this Dockerfile are out of support? MCP server can do

The Which base images in this Dockerfile are out of support? MCP server is published by referencesource.org, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: check_dockerfile), but cannot delete data. 1 tool only reads.

None of its tools reads private data, brings in text other people write, or sends data out.

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 16, 2026, version 1.1.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • check_dockerfilePaste a whole Dockerfile.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Which base images in this Dockerfile are out of support?
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 1Show 1 read-only tool
  • release_support_statusOne release, without a Dockerfile.No findings

    Why it is in this group

    • The name "release_support_status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Is this release still supported?
    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 16, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://referencesource.org/mcp/images: tools/list returned 2 tools to an anonymous client, including check_dockerfile (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

  1. Tools2 changed.~2 changedView diff

Install

Pinned to version 1.1.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http dockerfile-base-image-end-of-support https://referencesource.org/mcp/images
claude mcp add --transport http dockerfile-base-image-end-of-support https://referencesource.org/mcp/images

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__dockerfile-base-image-end-of-support__release_support_status"
    ],
    "ask": [
      "mcp__dockerfile-base-image-end-of-support__check_dockerfile"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as dockerfile-base-image-end-of-support. Review it before you use it.

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/org.referencesource/dockerfile-base-image-end-of-support/verify?hash=40570c5ab56e437bc2f7ba4c7fa393d6e5b56aca75c1790c6610873a64af65c9" | jq -e '.changed == false'

Pinned hash 40570c5ab56e, from Nov 16, 2026, 18:20 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/org.referencesource/dockerfile-base-image-end-of-support/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for org.referencesource/dockerfile-base-image-end-of-support
[![Anlyon Radar](https://radar.anlyon.com/badge/org.referencesource/dockerfile-base-image-end-of-support.svg)](https://radar.anlyon.com/servers/org.referencesource/dockerfile-base-image-end-of-support)

Source: MCP Registry. Synced Nov 16, 2026, 19:19 UTC.

Which base images in this Dockerfile are out of support? MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

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

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the Which base images in this Dockerfile are out of support? MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the Which base images in this Dockerfile are out of support? MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the Which base images in this Dockerfile are out of support? MCP server have?

2 tools: 1 write, 1 read. check_dockerfile and release_support_status.

Does the Which base images in this Dockerfile are out of support? MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the Which base images in this Dockerfile are out of support? MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the Which base images in this Dockerfile are out of support? MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 16, 2026. Every change is on this page and in its Atom feed.