AlgoVault Labs shipped v1.25.0 of its Model Context Protocol server today, and the headline item is a breaking one for self-hosters. The package now declares engines >=22 in its manifest, which means anyone running Node 18 or 20 will hit an engine warning at install time and has to upgrade before they can continue. It's the kind of dependency floor that trading bot operators should plan around rather than discover mid-deploy.

The Breaking Change: Node 22 Minimum

The engines field is now enforced at >=22, cutting off two LTS lines that a surprising amount of production infrastructure still sits on. Self-hosters get the warning immediately when they pull the package, so there's no silent breakage โ€” but there's also no way around it short of upgrading your runtime. The good news for managed-service users: AlgoVault's hosted endpoint is unaffected by the bump, so v1.25.0 works there without touching your local Node setup at all.

scan_trade_calls Gains a Filter

On the feature side, the release adds an optional parameter to scan_trade_calls for filtering results โ€” our copy of the changelog references it with a 'minL' prefix that gets cut off in transmission. The intent is clear enough: you can now set a minimum threshold on trade call scans instead of pulling back everything and doing the trimming client-side. For builders wiring this into automated pipelines, that means less noise hitting your downstream logic.

Upgrade Notes

If you self-host, budget time to bump your Node runtime before installing v1.25.0 โ€” check any CI pipelines or Docker images pinned to older versions first, because they'll be the ones that break silently on next build. The changelog as we received it doesn't detail every change in this release, so treat these as the headline items rather than a complete diff.

Key Takeaways

  • Node 22 is now the minimum runtime for self-hosted AlgoVault MCP; managed endpoints are unaffected.
  • scan_trade_calls gains an optional filter parameter to reduce noise before it hits your pipeline.
  • Plan ahead: upgrade CI and Docker images pinned to older Node versions before pulling v1.25.0.

The Bottom Line

Forcing Node 22 is the right call for a tool still moving fast โ€” you don't want to carry two dead LTS lines forever just to accommodate stragglers. Just don't be the operator who learns about it at 3am during an unattended install.