Evergreen
NPM · EVERGREEN-DEPRECATION
Evidence-backed deprecation and end-of-life checks for dependencies, runtimes, and Actions.
Available components
Last scanned (23 hours ago)
Scores higher than 94% of npm servers
Category Developer Tools
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 Security100
- 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
- 0 of 10 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to arminazimi/evergreen). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 1 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability84
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 14344 tokens (~44/item across 326 items; 10 tools + 316 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management57
- Stability observed for 17 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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 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
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.
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- Schema quality: 12771 → 14344 ▼ functional
- Package version: 0.7.1 → 0.7.2 functional
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 28 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 −15
- Malware scan: pass → unverified ▼ security
- Known CVEs: pass → unverified ▼ security
- Dependency health: 1.00 → unverified ▼ functional
- Package version: 0.6.0 → 0.7.1 functional
- Package version: 0.6.0 → 0.7.0 functional
- 26 Oct 26 +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.
- 25 Oct 26 +16
- Stability: 0.20 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.5.0 → 0.6.0 functional
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 4 Nov 2026 · Analysed npm/evergreen-deprecation@0.7.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | arminazimi/evergreen |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/arminazimi/evergreen/.github/workflows/publish.yml@refs/tags/v0.7.2 |
| Rekor log index | 3639474126 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:7e2ba2d8a7393127aca6a3e09b61baedb5a6d7f7d8fa05f4d390f2336c6a4f6848d56dc583d00003e1260734c87646cc14886fe62e0235099e96cbfd7 |
Background: How many MCP packages publish verified provenance →
Dependencies 10 packages
| Packages resolved | 10 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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_dependency Check dependency ~167
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.
| Name | Type | Req | Description |
|---|---|---|---|
| purl | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| data | object | – | Which lifecycle data this result was produced with, and how fresh its evidence is. |
| findings | array | yes | – |
| message | string | yes | – |
| purl | string | yes | Version-less canonical Package URL. |
| schemaVersion | – | yes | – |
| severity | – | – | Highest severity among the findings. |
| status | – | yes | no-data means Evergreen has no rule for the package; it does not mean the package is safe. |
| version | string | – | – |
No examples provided.
check_snippet Check snippet ~142
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.
| Name | Type | Req | Description |
|---|---|---|---|
| content | string | yes | The exact content the agent intends to write. |
| path | string | yes | The intended repository-relative path, for example Dockerfile, .github/workflows/ci.yml, or package.json. It decides which detector reads the snippet. |
| Name | Type | Req | Description |
|---|---|---|---|
| findings | array | yes | – |
| message | string | yes | One sentence a person or an agent can show as is. |
| path | string | yes | The repository-relative path the snippet was checked as, for example Dockerfile. |
| schemaVersion | – | yes | – |
No examples provided.
check_upgrade Check upgrade ~161
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.
| Name | Type | Req | Description |
|---|---|---|---|
| path | string | – | Local path to the repository. Defaults to the server working directory. |
| target | string | yes | Runtime and release to move to, as runtime@version, for example php@8.4 or nodejs@22. |
| Name | Type | Req | Description |
|---|---|---|---|
| analyzers | array | yes | Ids of the analyzers that applied to this repository and target, sorted. |
| issues | array | yes | – |
| schemaVersion | – | yes | – |
| target | object | yes | – |
| verdict | – | yes | blocked when any blocker; unknown when no analyzer applied; ready otherwise. unknown is not a statement that the upgrade is safe. |
No examples provided.
create_migration_context Create migration context ~61
Create a validated, rule-specific migration packet for one finding from a fresh local scan.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | Exact finding ID returned by Evergreen. |
| repository_path | string | – | Local path to the repository. Defaults to the server working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| affectedFiles | array | yes | – |
| constraints | array | yes | – |
| finding | object | yes | – |
| generatedAt | string | yes | – |
| repositoryRoot | string | yes | – |
| schemaVersion | – | yes | – |
| sources | array | yes | – |
| steps | array | yes | – |
| upgradePath | object | – | – |
| usages | array | yes | – |
| verification | array | yes | – |
No examples provided.
explain_deprecation Explain deprecation ~58
Run a fresh local scan and return one complete evidence-backed finding by ID.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | Exact finding ID returned by Evergreen. |
| repository_path | string | – | Local path to the repository. Defaults to the server working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| id | string | yes | – |
| impact | object | – | – |
| location | object | yes | – |
| migration | object | – | – |
| replacement | string | – | – |
| ruleId | string | yes | – |
| severity | – | yes | – |
| sources | array | yes | – |
| summary | string | yes | – |
| title | string | yes | – |
| usages | array | – | – |
No examples provided.
forecast_repository Forecast repository ~128
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| affecting | integer | yes | – |
| groups | array | yes | – |
| months | integer | yes | – |
| root | string | yes | – |
| schemaVersion | – | yes | – |
| today | string | yes | – |
| total | integer | yes | – |
| until | string | yes | – |
No examples provided.
list_deprecations List deprecations ~47
Run a fresh local scan and return a compact, versioned list of lifecycle findings.
| Name | Type | Req | Description |
|---|---|---|---|
| repository_path | string | – | Local path to the repository. Defaults to the server working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| count | integer | yes | – |
| data | object | – | Which lifecycle data this result was produced with, and how fresh its evidence is. |
| deprecations | array | yes | – |
| repositoryRoot | string | yes | – |
| scannedAt | string | yes | – |
| schemaVersion | – | yes | – |
No examples provided.
plan_migrations Plan migrations ~69
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.
| Name | Type | Req | Description |
|---|---|---|---|
| repository_path | string | – | Local path to the repository. Defaults to the server working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| schema | – | yes | – |
| summary | – | yes | – |
| waves | array | yes | – |
No examples provided.
scan_repository Scan repository ~94
Run all built-in Evergreen detectors against a local repository and return the complete versioned scan result.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | – |
| findings | array | yes | – |
| root | string | yes | – |
| scannedAt | string | yes | – |
| schemaVersion | – | yes | – |
| 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 | – | – |
No examples provided.
verify_migration Verify migration ~96
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.
| Name | Type | Req | Description |
|---|---|---|---|
| finding_id | string | yes | Exact finding ID returned by Evergreen. |
| repository_path | string | – | Local path to the repository. Defaults to the server working directory. |
| Name | Type | Req | Description |
|---|---|---|---|
| commandsExecuted | – | yes | – |
| findingId | string | yes | – |
| 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 | yes | – |
| repositoryRoot | string | yes | – |
| schemaVersion | – | yes | – |
| suggestedCommands | array | yes | – |
| summary | string | yes | – |
| verified | boolean | yes | – |
| verifiedAt | string | yes | – |
No examples provided.
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.
npm · evergreen-deprecation
claude mcp add arminazimi-evergreen -- npx -y evergreen-deprecation
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 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.