OpenCost
v1.120.1Observabilityv1.120.1 is a patch release focused on carbon cost fixes, AWS Spot pricing performance, memory optimization, and a security-relevant MCP server default change.
breakingCheck if MCP server was relied upon — it's now off by default
The MCP server flipped from opt-out to opt-in. If any tooling or integrations depended on the MCP server being active without explicit configuration, they will silently stop working after this upgrade. Before deploying, audit whether MCP_SERVER_ENABLED needs to be explicitly set to true in your environment config.
enhancementAWS Spot users: Spot Price History caching reduces API pressure
If you run workloads on AWS Spot instances, OpenCost was previously hitting the Spot Price History API more aggressively. The new caching layer cuts down on AWS API calls, which matters both for rate limiting and for cost attribution latency. No action required, but worth validating your Spot cost data accuracy after upgrading.
enhancementCarbon cost data was wrong — upgrade if you track emissions
The carbon cost fixes address incorrect provider detection and broken fallback logic, meaning prior carbon cost figures may have been inaccurate. If you surface carbon/emissions data to teams or dashboards, re-baseline your metrics post-upgrade rather than comparing historical data across this version boundary.
主な変更 (5)
- MCP server now defaults to disabled (MCP_SERVER_ENABLED=false) — previously it was opt-out, now it's opt-in
- Carbon cost lookups fixed: provider detection, fallback logic, and network cost support corrected
- AWS Spot Price History API now has a caching layer, reducing API call volume and latency
- Memory usage tweaks in a second pass of optimizations, continuing work from prior releases
- Local storage cost queries replaced with direct math, removing Prometheus query dependency for that path