Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

com.voltcast/voltcast

REMOTE · VOLTCAST.COM · SCANNED SEP 28

European day-ahead electricity prices (43 zones), accuracy-published forecasts, carbon, optimize.

Available components

+7 this week 86 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security83
Transport & Reachability100
Schema Quality & AI Usability74
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 658 tokens (~94/item across 7 items; 7 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage87
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 61% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the com.voltcast/voltcast MCP server?

com.voltcast/voltcast is a hosted endpoint at https://voltcast.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · voltcast.com

# add to Claude Code
claude mcp add --transport http com-voltcast-voltcast 'https://voltcast.com/api/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "com-voltcast-voltcast": {
      "url": "https://voltcast.com/api/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "com-voltcast-voltcast": {
      "type": "http",
      "url": "https://voltcast.com/api/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.com-voltcast-voltcast]
url = "https://voltcast.com/api/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-voltcast-voltcast": {
      "type": "remote",
      "url": "https://voltcast.com/api/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add com-voltcast-voltcast --url 'https://voltcast.com/api/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  com-voltcast-voltcast:
    url: "https://voltcast.com/api/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "com-voltcast-voltcast": {
      "Transport": "http",
      "Url": "https://voltcast.com/api/mcp"
    }
  }
}
# add to Vellum
assistant mcp add com-voltcast-voltcast -t streamable-http -u 'https://voltcast.com/api/mcp'
// mcp.json
{
  "mcpServers": {
    "com-voltcast-voltcast": {
      "type": "http",
      "url": "https://voltcast.com/api/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 24 Sept 26 +7
    • Authorization: unverified → partial ▲ security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “cheapest_window” rewrote its description, which is the text the model reads security
    • Tool “get_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_prices” rewrote its description, which is the text the model reads security
    • Tool “get_renewables” rewrote its description, which is the text the model reads security
    • Tool “cheapest_window” changed its title: Cheapest Window cosmetic
    • Tool “get_carbon” changed its title: Get Carbon cosmetic
    • Tool “get_forecast” changed its title: Get Forecast cosmetic
    • Tool “get_prices” changed its title: Get Prices cosmetic
    • Tool “get_realtime_prices” changed its title: Get Realtime Prices cosmetic
    • Tool “get_renewables” changed its title: Get Renewables cosmetic
    • Tool “list_zones” changed its title: List Zones cosmetic
  • 2 Sept 26 0
    • Tool “cheapest_window” rewrote its description, which is the text the model reads security
    • Schema quality: 86 → 95 ▼ functional
    • “cheapest_window” added an optional parameter “objective” cosmetic
    • “cheapest_window” added an optional parameter “tariff” cosmetic
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_prices” rewrote its description, which is the text the model reads security
  • 12 Aug 26 0
    • Tool “get_forecast” rewrote its description, which is the text the model reads security
    • Tool “get_renewables” rewrote its description, which is the text the model reads security
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 28 Sept 2026 · Probed https://voltcast.com/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=voltcast.com CN=WE1,O=Google Trust Services,C=US 7 Sept 2026 6 Dec 2026 ECDSA 256 ECDSA-SHA256 7c9638fcdfa67c1c0e43d8a61ad79a57
SANs: voltcast.com, *.voltcast.com
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC secure

Validation of voltcast.com. — Secure

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
voltcast.com. present 2371 13 Verified
voltcast.com. Verified address RRset verified with the apex keys
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
x-content-type-options nosniff
x-frame-options SAMEORIGIN
referrer-policy strict-origin-when-cross-origin

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://voltcast.com/api/mcp Verified 200
http (plaintext) http://voltcast.com/api/mcp HTTPS enforced 301 https://voltcast.com/api/mcp
MCP tools · 7 exposed · ~592 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
cheapest_window ~150

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.

NameTypeReqDescription
countinteger–How many windows (default 3)
duration_minutesintegeryesWindow length in minutes
fromstring––
objectivestring–Ranking objective (default cost). Carbon/balanced are experimental historical-profile heuristics, not forward carbon forecasts.
tariffobject–Optional variable household bill inputs; fixed monthly charges are excluded.
tostring––
zonestringyes–

No output schema declared.

No examples provided.

get_carbon ~58

Carbon intensity (gCO2eq/kWh) and green score (0-100 low-carbon share) derived from the live generation mix.

NameTypeReqDescription
fromstring––
tostring––
zonestringyes–

No output schema declared.

No examples provided.

get_forecast ~61

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.

NameTypeReqDescription
horizonstring––
zonestringyes–

No output schema declared.

No examples provided.

get_prices ~95

Day-ahead electricity prices in each zone's native currency and native market resolution. Connect an existing Voltcast account to access account-scoped data.

NameTypeReqDescription
fromstring–ISO 8601 start (default: yesterday)
resolutionstring––
tostring–ISO 8601 end (default: tomorrow)
zonestringyesBidding zone code, e.g. 'DE-LU'

No output schema declared.

No examples provided.

get_realtime_prices ~109

Explicitly labeled real-time market prices (currently WEIM), kept separate from day-ahead curves. Requires an API key.

NameTypeReqDescription
fromstring–ISO 8601 start (default: last 24h)
marketstring–Optional market filter, e.g. 'weim'
tostring–ISO 8601 end (default: now)
zonestringyesMarket reference code, e.g. 'US-WEIM-AZPS'

No output schema declared.

No examples provided.

get_renewables ~92

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.

NameTypeReqDescription
fromstring–ISO 8601 start
tostring–ISO 8601 end
zonestringyesBidding zone code, e.g. 'DE-LU'

No output schema declared.

No examples provided.

list_zones ~27

List all supported European bidding zones with codes, names, and capabilities. No auth required.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

Common questions

What is the com.voltcast/voltcast MCP server?

com.voltcast/voltcast is an MCP server listed in the public MCP registry as com.voltcast/voltcast. European day-ahead electricity prices (43 zones), accuracy-published forecasts, carbon, optimize. This page covers its hosted endpoint (https://voltcast.com/api/mcp).

Is the com.voltcast/voltcast MCP server safe to use?

com.voltcast/voltcast scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the com.voltcast/voltcast MCP server expose?

com.voltcast/voltcast exposes 7 tools: list_zones, get_prices, get_realtime_prices, get_forecast, get_carbon, and 2 more. Their descriptions and schemas cost roughly 592 tokens of context every time the server is loaded.

Does the com.voltcast/voltcast MCP server require authentication?

No. We connected to com.voltcast/voltcast without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the com.voltcast/voltcast MCP server still maintained?

com.voltcast/voltcast is still listed as active in the MCP registry. We last reached this channel on 28 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.