Find end-of-life and deprecated runtimes, packages, and GitHub Actions at exact file locations, with sources and migration context. CLI, MCP server, GitHub Action, Agent Skill.
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.
scan_repositoryRun all built-in Evergreen detectors against a local repository and return the complete versioned scan result.Run all built-in Evergreen detectors against a local repository and return the complete versioned scan result.
No input schema was published for this tool.
list_deprecationsRun a fresh local scan and return a compact, versioned list of lifecycle findings.Run a fresh local scan and return a compact, versioned list of lifecycle findings.
No input schema was published for this tool.
explain_deprecationRun a fresh local scan and return one complete evidence-backed finding by ID.Run a fresh local scan and return one complete evidence-backed finding by ID.
No input schema was published for this tool.
create_migration_contextCreate a validated, rule-specific migration packet for one finding from a fresh local scan.Create a validated, rule-specific migration packet for one finding from a fresh local scan.
No input schema was published for this tool.
verify_migrationRe-scan locally and check whether a finding observed earlier in this MCP session is gone. Suggested project commands are returned but never executed.Re-scan locally and check whether a finding observed earlier in this MCP session is gone. Suggested project commands are returned but never executed.
No input schema was published for this tool.
check_dependencyCheck 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 ev…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 ev…
No input schema was published for this tool.
6 of 6 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
Find end-of-life and deprecated runtimes, packages, and GitHub Actions at exact file locations, with sources and migration context. CLI, MCP server, GitHub Action, Agent Skill.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.