# End-of-life check (npm · eol-check-mcp)

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

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

## Components

- npm · `eol-check-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp.md), [page](https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp)

## Channel facts

- Registry: `npm`
- Package: `eol-check-mcp`
- Version: `0.1.2`
- Transport: `stdio`

## Trust breakdown

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

- **Supply Chain Security**: 98/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - 31 of 95 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (excellent).
  - 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.
  - 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 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.

### Claude

```bash
claude mcp add com-mervenor-eol-check-mcp -- npx -y eol-check-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "com-mervenor-eol-check-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eol-check-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mervenor-eol-check-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eol-check-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add com-mervenor-eol-check-mcp -- npx -y eol-check-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-mervenor-eol-check-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "eol-check-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-mervenor-eol-check-mcp --command npx --arg -y --arg eol-check-mcp
```

### Hermes

```yaml
mcp_servers:
  com-mervenor-eol-check-mcp:
    command: "npx"
    args: ["-y", "eol-check-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "com-mervenor-eol-check-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "eol-check-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mervenor-eol-check-mcp -t stdio -c npx -a -y eol-check-mcp
```

### Other

```json
{
  "mcpServers": {
    "com-mervenor-eol-check-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "eol-check-mcp"
      ]
    }
  }
}
```

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

### 2026-11-18 (score 70, +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-16 (score 69)

First indexed and scored.

## MCP tools (4)

### `list_products` (~126 tokens)

List products

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.

Input parameters:

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

### `get_cycles` (~137 tokens)

Get release cycles

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.

Input parameters:

- `date` (string): Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
- `limit` (integer): Only the newest N cycles.
- `product` (string, required): Product id or common name, for example "dotnet", ".NET", "nodejs", "angularjs", "postgres".

### `check_version` (~217 tokens)

Check a version

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

Input parameters:

- `date` (string): Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
- `product` (string, required): Product id or common name, for example "dotnet", "dotnetfx", "nodejs", "python", "angularjs".
- `version` (string, required): Version or release cycle, for example "8", "6.0.25", "net6.0", "net48", "1.8.2", "3.9".

### `scan_project` (~233 tokens)

Scan project files

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.

Input parameters:

- `date` (string): Date to evaluate support on, as YYYY-MM-DD. Defaults to today. Use it for "will this still be supported on ...?" questions.
- `files` (array, required): Project files to scan.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp#diagnostics

## Score history

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

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

## Links

- npm package: https://www.npmjs.com/package/eol-check-mcp
- Socket report: https://socket.dev/npm/package/eol-check-mcp
- Repository: https://github.com/mervenor/eol-check-mcp
- Changelog RSS feed: https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-mervenor-eol-check-mcp/eol-check-mcp
