Evergreen runs on your own machine — the client starts it, so there is no endpoint to ping. 946 installs a week from npm. Last commit 31 Oct 2026.
Evidence-backed deprecation and end-of-life checks for dependencies, runtimes, and Actions.
What the code does
We read the source, 2 h ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, args, { cwd, stdio: "inherit" });
const delta = `${item.drop > 0 ? "−" : item.drop < 0 ? "+" : ""}${roundOne(Math.abs(item.drop))}`;
"rawBytes": "MIIB+DCCAX6gAwIBAgITNVkDZoCiofPDsy7dfm6geLbuhzAKBggqhkjOPQQDAzAqMRUwEwYDVQQKEwxzaWdzdG9yZS5kZXYxETAPBgNVBAMTCHNpZ3N0b3JlMB4XDTIxMDMwNzAzMjAyOVoXDTMxMDIyMzAzMjAyOVowKjEVMBMGA1UEChMMc2lnc3RvcmUuZGV2MREwDwYDVQQDEwhzaWdzdG9yZTB2MBAGByqGSM49AgEGBSuBBAAiA2IABLS…
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add evergreen -- npx -y evergreen-deprecation{
"mcpServers": {
"evergreen": {
"command": "npx",
"args": [
"-y",
"evergreen-deprecation"
]
}
}
}[mcp_servers.evergreen]
command = "npx"
args = ["-y", "evergreen-deprecation"]{
"mcpServers": {
"evergreen": {
"command": "npx",
"args": [
"-y",
"evergreen-deprecation"
]
}
}
}{
"servers": {
"evergreen": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"evergreen-deprecation"
]
}
}
}Alternatives to Evergreen
same job, measured the same wayIndependent deterministic verification for AI-written software. Local, evidence-backed checks.
Local checks for artifacts, declared claim evidence, and citation containment.
Gender, salutations, name checks and age from names, with the evidence on every answer.
Evidence-backed pre-purchase checks for offer terms, seller trust and policy compliance.
Checks AI agent actions before they run. Signed, RFC 3161 timestamped evidence for audits.
Open-source licence risk checks for AI coding agents and dependency trees.
The changelog of record for the AI stack: sunset checks, deprecations, pricing, and model events.
Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.
Evergreen — questions
Answers built from our own checks of this server.