# Evergreen (npm · evergreen-deprecation)

Evidence-backed deprecation and end-of-life checks for dependencies, runtimes, and Actions.

- Trust score: 92/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `evergreen-deprecation`: 92/100 (this document), [markdown](https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation.md), [page](https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation)

## Channel facts

- Registry: `npm`
- Package: `evergreen-deprecation`
- Version: `0.7.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-05.

- **Supply Chain Security**: 100/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.
  - 0 of 10 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 100/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to arminazimi/evergreen).
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Publishes a security disclosure policy (SECURITY.md).
- **Schema Quality & AI Usability**: 84/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 14344 tokens (~44/item across 326 items; 10 tools + 316 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 12 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 Evergreen MCP server?

Evergreen runs locally as an npm package, launched with npx -y evergreen-deprecation. 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 arminazimi-evergreen -- npx -y evergreen-deprecation
```

### Cursor

```json
{
  "mcpServers": {
    "arminazimi-evergreen": {
      "command": "npx",
      "args": [
        "-y",
        "evergreen-deprecation"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "arminazimi-evergreen": {
      "command": "npx",
      "args": [
        "-y",
        "evergreen-deprecation"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add arminazimi-evergreen -- npx -y evergreen-deprecation
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "arminazimi-evergreen": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "evergreen-deprecation"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add arminazimi-evergreen --command npx --arg -y --arg evergreen-deprecation
```

### Hermes

```yaml
mcp_servers:
  arminazimi-evergreen:
    command: "npx"
    args: ["-y", "evergreen-deprecation"]
```

### Netclaw

```json
{
  "McpServers": {
    "arminazimi-evergreen": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "evergreen-deprecation"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add arminazimi-evergreen -t stdio -c npx -a -y evergreen-deprecation
```

### Other

```json
{
  "mcpServers": {
    "arminazimi-evergreen": {
      "command": "npx",
      "args": [
        "-y",
        "evergreen-deprecation"
      ]
    }
  }
}
```

## 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-05 (score 92, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-03 (score 91, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 75, −14)

- [security regression] Malware scan: pass → unverified
- [functional regression] Schema quality: 12771 → 14344
- [functional] Package version: 0.7.1 → 0.7.2

### 2026-10-31 (score 89, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-29 (score 88, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 87, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-10-27 (score 72, −15)

- [security regression] Malware scan: pass → unverified
- [security regression] Known CVEs: pass → unverified
- [functional regression] Dependency health: 1.00 → unverified
- [functional] Package version: 0.6.0 → 0.7.1
- [functional] Package version: 0.6.0 → 0.7.0

### 2026-10-26 (score 87, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (10)

### `scan_repository` (~94 tokens)

Scan repository

Run all built-in Evergreen detectors against a local repository and return the complete versioned scan result.

Input parameters:

- `baseline` (string): Optional path, relative to the repository, of an Evergreen baseline file. Suppressed findings are left out and the result's suppressions field says how many, and which suppressions are expiring or ex…
- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `asOf` (string): The day the scan was projected onto with --as-of. Present only when one was given.
- `coverage` (object): What the scan checked, so a zero-finding report can say what was covered and what was not. Path arrays are complete here; the text report may show only the first ten of each.
- `data` (object): Which lifecycle data this result was produced with, and how fresh its evidence is.
- `diagnostics` (array)
- `findings` (array)
- `root` (string)
- `scannedAt` (string)
- `schemaVersion`
- `selection` (object): The --only/--exclude selectors applied to the scan. Present only when one was given.
- `suppressions` (object): What a baseline did to this scan. Present only when a baseline was applied.
- `unclassified` (object)

### `list_deprecations` (~47 tokens)

List deprecations

Run a fresh local scan and return a compact, versioned list of lifecycle findings.

Input parameters:

- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `count` (integer)
- `data` (object): Which lifecycle data this result was produced with, and how fresh its evidence is.
- `deprecations` (array)
- `repositoryRoot` (string)
- `scannedAt` (string)
- `schemaVersion`

### `explain_deprecation` (~58 tokens)

Explain deprecation

Run a fresh local scan and return one complete evidence-backed finding by ID.

Input parameters:

- `finding_id` (string, required): Exact finding ID returned by Evergreen.
- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `advisoryIds` (array): OSV advisory identifiers with no fixed version for this finding's package, from the bundled OSV cross-reference.
- `confidence`
- `deadline` (string)
- `dependencyPath` (array)
- `detector` (string)
- `id` (string)
- `impact` (object)
- `location` (object)
- `migration` (object)
- `replacement` (string)
- `ruleId` (string)
- `severity`
- `sources` (array)
- `summary` (string)
- `title` (string)
- `usages` (array)

### `create_migration_context` (~61 tokens)

Create migration context

Create a validated, rule-specific migration packet for one finding from a fresh local scan.

Input parameters:

- `finding_id` (string, required): Exact finding ID returned by Evergreen.
- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `affectedFiles` (array)
- `constraints` (array)
- `finding` (object)
- `generatedAt` (string)
- `repositoryRoot` (string)
- `schemaVersion`
- `sources` (array)
- `steps` (array)
- `upgradePath` (object)
- `usages` (array)
- `verification` (array)

### `verify_migration` (~96 tokens)

Verify migration

Re-scan locally and check whether a finding observed earlier in this MCP session is gone. Suggested project commands are returned but never executed. When the repository was scanned earlier in the session, the result also carries a receipt and receipt_markdown for the pull request body.

Input parameters:

- `finding_id` (string, required): Exact finding ID returned by Evergreen.
- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `commandsExecuted`
- `findingId` (string)
- `receipt` (object): What the change since the session's last scan did to the repository's findings. Present when a scan was observed before verification.
- `receipt_markdown` (string): The receipt rendered for a pull request body, with the evergreen-receipt marker.
- `remainingFindings` (array)
- `repositoryRoot` (string)
- `schemaVersion`
- `suggestedCommands` (array)
- `summary` (string)
- `verified` (boolean)
- `verifiedAt` (string)

### `check_dependency` (~167 tokens)

Check dependency

Check one package, and optionally one version, against Evergreen's lifecycle rules before adding it to a project. Pass a Package URL such as pkg:npm/request@2.88.2 or pkg:github/actions/checkout@v4. Returns evergreen.check.v1: a status (affected, not-affected, version-dependent, or no-data), the evidence-backed findings, and a replacement when one is known. no-data means Evergreen has no rule for the package, not that it is safe. No repository is read.

Input parameters:

- `purl` (string, required): Package URL of the dependency, with the version when it is known, for example pkg:npm/request@2.88.2.
- `version` (string): Exact version to check; overrides a version written in the PURL.

Output parameters:

- `data` (object): Which lifecycle data this result was produced with, and how fresh its evidence is.
- `findings` (array)
- `message` (string)
- `purl` (string): Version-less canonical Package URL.
- `schemaVersion`
- `severity`: Highest severity among the findings.
- `status`: no-data means Evergreen has no rule for the package; it does not mean the package is safe.
- `version` (string)

### `check_upgrade` (~161 tokens)

Check upgrade

Answer from files already in the repository whether a project can move to a target runtime, without running anything or using the network. Pass target as runtime@version, for example php@8.4. Returns evergreen.upgrade.v1: the verdict, the analyzers that applied, and every blocker, warning, and unknown with its path, line, and the exact constraint it read. An unknown verdict means Evergreen found no evidence for this runtime in this repository; it is not a statement that the upgrade is safe.

Input parameters:

- `path` (string): Local path to the repository. Defaults to the server working directory.
- `target` (string, required): Runtime and release to move to, as runtime@version, for example php@8.4 or nodejs@22.

Output parameters:

- `analyzers` (array): Ids of the analyzers that applied to this repository and target, sorted.
- `issues` (array)
- `schemaVersion`
- `target` (object)
- `verdict`: blocked when any blocker; unknown when no analyzer applied; ready otherwise. unknown is not a statement that the upgrade is safe.

### `check_snippet` (~142 tokens)

Check snippet

Check one file snippet before writing it: pass the intended repository-relative path and the exact content, and Evergreen runs all built-in detectors against that one file in an isolated temporary directory. Call this before writing or editing package manifests, Dockerfiles, CI workflows, and Kubernetes manifests. Returns the same findings as scan_repository, with paths and lines relative to the snippet. The real repository is never read or written.

Input parameters:

- `content` (string, required): The exact content the agent intends to write.
- `path` (string, required): The intended repository-relative path, for example Dockerfile, .github/workflows/ci.yml, or package.json. It decides which detector reads the snippet.

Output parameters:

- `findings` (array)
- `message` (string): One sentence a person or an agent can show as is.
- `path` (string): The repository-relative path the snippet was checked as, for example Dockerfile.
- `schemaVersion`

### `forecast_repository` (~128 tokens)

Forecast repository

Run a fresh local scan and list what reaches a dated end of life in the next months, grouped by month, with the findings in this repository that each event will affect. Only events that carry an authoritative date are listed; nothing is estimated.

Input parameters:

- `as_of` (string): The day to start the window from, as YYYY-MM-DD. Defaults to today in UTC.
- `months` (integer): How many months ahead to look, from 1 to 36. Defaults to 12.
- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `affecting` (integer)
- `groups` (array)
- `months` (integer)
- `root` (string)
- `schemaVersion`
- `today` (string)
- `total` (integer)
- `until` (string)

### `plan_migrations` (~69 tokens)

Plan migrations

Run a fresh local scan and return a migration plan: waves of independent tasks a coordinating agent can hand to other agents. Each item names the finding, the paths it touches, and a suggested branch.

Input parameters:

- `repository_path` (string): Local path to the repository. Defaults to the server working directory.

Output parameters:

- `items` (array)
- `schema`
- `summary`
- `waves` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation#diagnostics

## Score history

- 2026-11-05: 92
- 2026-11-04: 91
- 2026-11-03: 91
- 2026-11-02: 75
- 2026-11-01: 89
- 2026-10-31: 89
- 2026-10-30: 88
- 2026-10-29: 88
- 2026-10-28: 87
- 2026-10-27: 72
- 2026-10-26: 87
- 2026-10-25: 86
- 2026-10-24: 70
- 2026-10-23: 85
- 2026-10-22: 85
- 2026-10-21: 84
- 2026-10-20: 84
- 2026-10-19: 83
- 2026-10-18: 83

## Common questions

### What is the Evergreen MCP server?

Evergreen is an MCP server listed in the public MCP registry as io.github.arminazimi/evergreen. Evidence-backed deprecation and end-of-life checks for dependencies, runtimes, and Actions. This page covers its npm package (evergreen-deprecation).

### Is the Evergreen MCP server safe to use?

Evergreen scores 92 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Evergreen MCP server expose?

Evergreen exposes 10 tools: scan_repository, list_deprecations, explain_deprecation, create_migration_context, verify_migration, and 5 more. Their descriptions and schemas cost roughly 1,023 tokens of context every time the server is loaded.

### Is the Evergreen MCP server still maintained?

Evergreen is still listed as active in the MCP registry. We last reached this channel on 5 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 Evergreen MCP server under?

Evergreen declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/evergreen-deprecation
- Socket report: https://socket.dev/npm/package/evergreen-deprecation
- Repository: https://github.com/arminazimi/evergreen
- Website: https://arminazimi.github.io/evergreen/
- Changelog RSS feed: https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation.xml
- Changelog JSON feed: https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation.json
- HTML version of this page: https://verifymcp.io/servers/arminazimi-evergreen/evergreen-deprecation