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?
Available components
Last scanned (14 hours ago)
Scores higher than 57% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Security
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 Security74
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 →
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 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.
- 18 Nov 26 +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.
- 17 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 16 Nov 26 70
First indexed and scored.
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://referencesource.org/mcp/images
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=referencesource.org | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 284c538e5c38c80d0eb8e23b1bba01ab |
| SANs: referencesource.org | ||||||
| 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 referencesource.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| org. | DS published | 725 | 8 | Verified |
| referencesource.org. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://referencesource.org/mcp/images | Verified | 200 | |
| http (plaintext) | http://referencesource.org/mcp/images | HTTPS enforced | 301 | https://referencesource.org/mcp/images |
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 →
check_dockerfile Which base images in this Dockerfile are out of support? ~220
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.
| Name | Type | Req | Description |
|---|---|---|---|
| dockerfile | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| from_lines | integer | yes | FROM lines found in the file. |
| images_checked | integer | yes | FROM lines matched to a release in this register. |
| images_unresolved | integer | yes | FROM lines not checked. See not_in_our_records and unresolvable. |
| not_in_our_records | array | yes | 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 | yes | 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 | yes | 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 | yes | One sentence. Always says how many lines were not checked. |
No examples provided.
release_support_status Is this release still supported? ~257
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.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | 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 | yes | "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". |
| Name | Type | Req | Description |
|---|---|---|---|
| coverage | string | yes | – |
| found | boolean | yes | – |
| 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 | – | – |
No examples provided.
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.
remote · referencesource.org
claude mcp add --transport http org-referencesource-dockerfile-base-image-end-of 'https://referencesource.org/mcp/images'
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.