energidata-mcp
Related Servers
Alternatives to energidata-mcp
No user-submitted related servers found.
Related Servers
- AlicenseAqualityDmaintenanceProvides access to Danish energy data from Energinet, including real-time electricity spot prices, CO2 emissions, and production mix. It enables users to monitor grid status and identify the most cost-effective hours for energy-intensive tasks.4MIT
- AlicenseAqualityBmaintenanceEnables querying Danish energy data—electricity prices, carbon intensity, consumption, production, grid capacity, balancing markets, and gas—from Energinet's public Energi Data Service without an API key.7MIT
- FlicenseNot gradedqualityBmaintenanceProvides tools for querying Danish day-ahead electricity prices, finding cheapest charging windows, estimating costs, and creating pending charging plans, with strict validation and human-in-the-loop approval for write operations.-
- AlicenseAqualityDmaintenanceProvides real-time electricity grid data including CO2 intensity, power mix, and wholesale prices, plus optimal green time windows for energy-intensive AI tasks. Supports UK, Germany, and global regions with optional API keys.9MIT
- AlicenseNot gradedqualityCmaintenanceEnables users to query current and historical UK electricity carbon intensity, generation mix, and regional intensity data to schedule energy-intensive tasks during low-carbon periods.90 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables querying Denmark's official open energy data from Energinet through MCP tools.160 npmMIT
TDQS
Scored across 3 tools
Each tool targets a clearly distinct concern: raw CO2 intensity series, raw spot price series, and an optimization/selection query. Although best_hours draws on the same data as the other two, its purpose (picking hours) is unambiguous and descriptions make the boundary explicit.
All three names are lowercase snake_case noun phrases with no mixed conventions: co2_intensity, spot_price, best_hours. Predictable and readable.
Three tools is well-scoped for a narrow domain (two data series plus a selection helper), with no redundancy. It sits near the thin edge — a bare minimum surface for a data server.
The core lifecycle (fetch CO2, fetch price, pick optimal hours) is covered with sensible parameters like metric, n_hours, consecutive, and source. Minor gaps exist: no way to list available price areas, no finer-than-hourly resolution option, and no combined CO2+cost ranking for best_hours.