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.

End-of-life check

NPM · EOL-CHECK-MCP

Tells an AI assistant whether a project's runtimes and frameworks are still supported.

Available components

71 Trust /100

Last scanned (13 hours ago)

Scores higher than 42% of npm servers

Category Developer Tools

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability69
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 809 tokens (~202/item across 4 items; 4 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
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 5 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 (16)

  • Malware scan
  • Known CVEs
  • Install scripts
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

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.

  • 20 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 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.

  • 16 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 · Analysed npm/eol-check-mcp@0.1.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~713 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
check_version ~217

Checks one product version: supported, security-only or end-of-life on the given date, with the end dates, days remaining or overdue, the latest patch in that cycle, the newest cycle and the recommended upgrade. Accepts versions as people write them: "8", "8.0.11", "net8.0", "net472", "4.8", "v18.19.0", "lts/hydrogen", "3.12".

NameTypeReqDescription
datestring–Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
productstringyesProduct id or common name, for example "dotnet", "dotnetfx", "nodejs", "python", "angularjs".
versionstringyesVersion or release cycle, for example "8", "6.0.25", "net6.0", "net48", "1.8.2", "3.9".

No output schema declared.

No examples provided.

get_cycles ~137

Returns every release cycle of a product, newest first, with release date, LTS flag, end of active support, end of security support (end of life), status on the given date, days remaining or overdue, and the latest patch version.

NameTypeReqDescription
datestring–Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
limitinteger–Only the newest N cycles.
productstringyesProduct id or common name, for example "dotnet", ".NET", "nodejs", "angularjs", "postgres".

No output schema declared.

No examples provided.

list_products ~126

Lists the products in the endoflife.date snapshot (runtimes, frameworks, databases, operating systems and more), with their ids for use in the other tools. Filter by a search text and/or category.

NameTypeReqDescription
categorystring–Only this category: framework, lang, database, os, server-app, app, service, device or standard.
limitinteger–Maximum number of products to return (default 100).
querystring–Text to search in product ids, names and aliases, for example "net", "angular" or "postgres".

No output schema declared.

No examples provided.

scan_project ~233

Reads project files you pass in (contents, not paths on disk) and reports every runtime and framework it detects (Node.js, .NET and .NET Framework, ASP.NET Core, AngularJS, Angular, React, Next.js, Vue, Python, Django, PostgreSQL, MySQL and more) with its support status, sorted most urgent first, plus a one-paragraph summary. Supported files: package.json, package-lock.json, npm-shrinkwrap.json, angular.json, bower.json, *.csproj / *.vbproj / *.fsproj, Directory.Build.props, global.json, web.config, packages.config, requirements*.txt, pyproject.toml, Pipfile, .python-version, runtime.txt, .nvmrc, .node-version, .tool-versions, Dockerfile / *.dockerfile / Containerfile, docker-compose*.yml / compose*.yaml.

NameTypeReqDescription
datestring–Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
filesarrayyesProject files to scan.

No output schema declared.

No examples provided.

Install

How do I install the End-of-life check MCP server?

End-of-life check runs locally as an npm package, launched with npx -y eol-check-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · eol-check-mcp

# add to Claude Code
claude mcp add com-mervenor-eol-check-mcp -- npx -y eol-check-mcp
Common questions

What is the End-of-life check MCP server?

End-of-life check is an MCP server listed in the public MCP registry as com.mervenor/eol-check-mcp. Tells an AI assistant whether a project's runtimes and frameworks are still supported. This page covers its npm package (eol-check-mcp).

Is the End-of-life check MCP server safe to use?

End-of-life check scores 71 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 End-of-life check MCP server expose?

End-of-life check exposes 4 tools: list_products, get_cycles, check_version, scan_project. Their descriptions and schemas cost roughly 713 tokens of context every time the server is loaded.

Is the End-of-life check MCP server still maintained?

End-of-life check 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 licence is the End-of-life check MCP server under?

End-of-life check declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

What did VerifyMCP test on the End-of-life check MCP server?

VerifyMCP ran 16 checks on End-of-life check, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.