Voltcast MCP server

Which servers in the official MCP registry are Voltcast's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-14

← Back to Voltcast

Whose server it is

Registry namecom.voltcast/voltcastverified in the MCP registry

The registry name sits under voltcast.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-14

Stateanswerschecked 2026-10-14
Tools7
Server calls itselfvoltcast
Server version1.0.0
Protocol version2025-06-18

On 2026-10-14 the server answered initialize and tools/list without a sign-in. First answer in 244 ms.

Tools it offers7 tools · read 2026-10-14

list_zones
List all supported European bidding zones with codes, names, and capabilities. No auth required.
get_prices
Day-ahead electricity prices in each zone's native currency and native market resolution. Connect an existing Voltcast account to access account-scoped data.
get_realtime_prices
Explicitly labeled real-time market prices (currently WEIM), kept separate from day-ahead curves. Requires an API key.
get_forecast
Probabilistic price forecast up to 7 days ahead. Returns the P50 curve and any uncertainty bands included in the connected account. Accuracy is published daily at voltcast.com/accuracy.
get_carbon
Carbon intensity (gCO2eq/kWh) and green score (0-100 low-carbon share) derived from the live generation mix.
get_renewables
Day-ahead wind and solar generation forecasts: the TSO official forecast and Voltcast model with uncertainty bands, realized generation, and disclosed head-to-head verification. Requires the corresponding existing account entitlement.
cheapest_window
Rank household action windows by cost using current Voltcast curves and optional user-supplied variable tariff inputs. Experimental carbon/balanced modes use a disclosed trailing historical production-mix profile—not a forward carbon…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "voltcast": {
      "type": "http",
      "url": "https://voltcast.com/api/mcp"
    }
  }
}

OpenAPI spec

54 paths, read 2026-10-14. Open the spec ↗

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.