Model Context Protocol (MCP) server for freee API integration
Voltcast is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
European day-ahead electricity prices (43 zones), accuracy-published forecasts, carbon, optimize.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http voltcast-mcp https://voltcast.com/api/mcp
# 2 — ask your agent for something these tools do
# list_zones, get_prices, get_realtime_prices and 4 more
Voltcast costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http voltcast-mcp https://voltcast.com/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List all supported European bidding zones with codes, names, and capabilities. No auth required.
No parameter schema on file.
Day-ahead electricity prices in each zone's native currency and native market resolution. Connect an existing Voltcast account to access account-scoped data.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Bidding zone code, e.g. 'DE-LU' |
| from | string | no | ISO 8601 start (default: yesterday) |
| to | string | no | ISO 8601 end (default: tomorrow) |
| resolution | string | no | — |
Explicitly labeled real-time market prices (currently WEIM), kept separate from day-ahead curves. Requires an API key.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Market reference code, e.g. 'US-WEIM-AZPS' |
| from | string | no | ISO 8601 start (default: last 24h) |
| to | string | no | ISO 8601 end (default: now) |
| market | string | no | Optional market filter, e.g. 'weim' |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| horizon | string | no | — |
Carbon intensity (gCO2eq/kWh) and green score (0-100 low-carbon share) derived from the live generation mix.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| from | string | no | — |
| to | string | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | Bidding zone code, e.g. 'DE-LU' |
| from | string | no | ISO 8601 start |
| to | string | no | ISO 8601 end |
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 forecast—and support no emissions-reduction claim.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| duration_minutes | integer | yes | Window length in minutes |
| from | string | no | — |
| to | string | no | — |
| count | integer | no | How many windows (default 3) |
| objective | string | no | Ranking objective (default cost). Carbon/balanced are experimental historical-profile heuristics, not forward carbon forecasts. |
| tariff | object | no | Optional variable household bill inputs; fixed monthly charges are excluded. |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Voltcast or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| list_zones | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_prices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_realtime_prices | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_forecast | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_carbon | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| get_renewables | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
| cheapest_window | untrusted-input | untrusted-input: declares openWorldHint: true (interacts with entities outside the server) |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Voltcast can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.