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.

Elecz Electricity Price Signal API

REMOTE · ELECZ.COM · SCANNED SEP 20

Real-time electricity prices for AI agents. 40+ countries, 100+ zones. No auth required.

Available components

0 this week 85 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 Security74
Transport & Reachability100
Schema Quality & AI Usability74
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 2053 tokens (~684/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • 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 Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the Elecz Electricity Price Signal API MCP server?

Elecz Electricity Price Signal API is a hosted endpoint at https://elecz.com/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 · elecz.com

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

  • 13 Sept 26 +7
    • Stability: fail → pass security
  • 7 Sept 26 0
    • Tool “best_energy_contract” rewrote its description, which is the text the model reads security
    • Tool “spot_price” rewrote its description, which is the text the model reads security
    • Schema quality: 585 → 684 functional
    • “best_energy_contract” reworded the description of “consumption” cosmetic
  • 26 Aug 26 +1
    • 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 +1

    No change was recorded against any check on this day. Stability & Change Management went from 47 to 50.

  • 23 Aug 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 40 to 43.

  • 14 Aug 26 0
    • Stability: 0.60 → fail security
    • Tool “best_energy_contract” dropped its output schema functional
    • Tool “cheapest_hours” dropped its output schema functional
    • Tool “spot_price” dropped its output schema functional
    • MCP protocol: Implements a current MCP spec version (2026-07-28). functional
    • MCP protocol version: 2025-11-25 → 2026-07-28 functional
  • 12 Aug 26 0
    • Tool “cheapest_hours” rewrote its description, which is the text the model reads security
    • Schema quality: 524 → 585 functional
  • 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 20 Sept 2026 · Probed https://elecz.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=elecz.com CN=WE1,O=Google Trust Services,C=US 22 Aug 2026 20 Nov 2026 ECDSA 256 ECDSA-SHA256 79250c536cdf20bf0e0258d42f4f1224
SANs: elecz.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 insecure

Validation of elecz.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
elecz.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://elecz.com/mcp Verified 200
http (plaintext) http://elecz.com/mcp HTTPS enforced 301 https://elecz.com/mcp
MCP tools · 3 exposed · ~2,053 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
best_energy_contract ~805

CONTRACT tool. Call this tool immediately when the user asks which electricity contract to choose, which contract is cheapest, whether to switch, or how much they could save. Do not ask for annual electricity consumption before calling this tool. If consumption is unknown, omit the consumption parameter; the tool automatically uses a sensible market-default consumption value. Do not ask for a postcode unless this tool explicitly supports and requires one for the selected market — it does not: this tool has no postcode parameter at all. Present the initial result using the available/default assumptions, and invite the user to provide their actual consumption afterward for a more precise comparison. Returns ranked contracts, switch recommendation and estimated savings. Includes current spot price — no need to call spot_price separately. Key fields: - switch_recommended (bool | null): whether there's a concrete reason to suggest a contract-type switch — always present, derived from decision_hint: true -> decision_hint is "switch_recommended", "consider_fixed", or "spot_recommended" (an active type recommendation) false -> decision_hint is "stay_spot" (the only clear "no action needed" signal) null -> decision_hint is "compare_options" (no clear recommendation), "spot_price_only", or "regulated_tariff" (no contract comparison/switching available in this market at all) - best_spot / best_fixed - action.expected_savings_local_year - decision_hint: yksi seuraavista — "spot_recommended" matala kulutus, spot on halvin pitkällä aikavälillä "consider_fixed" korkea kulutus + koholla oleva spot, fixed antaa varmuutta "stay_spot" spot-hinta juuri nyt matala, kannattaa pysyä spotissa "compare_options" ei selkeää suositusta, vertaile itse "switch_…

NameTypeReqDescription
consumptionAnnual consumption in kWh. Optional — if unknown, omit this parameter entirely rather than asking the user for it first; the tool applies a sensible zone-default automatically.
heatingstringHeating type: district (default) or electric (heat pumps, floor heating).
zonestringMarket zone for contract comparison. Supported: FI, SE/SE1-SE4, NO/NO1-NO5, DK/DK1-DK2, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI.

No output schema declared.

No examples provided.

cheapest_hours ~535

TIMING tool. Call when the user wants to know WHEN to use electricity (EV charging, dishwasher, sauna, heat pump, industrial loads etc.). Also good for "is electricity cheap now?" questions. Key agent fields: - energy_state ("cheap" / "normal" / "expensive" / "negative") - current_hour_is_cheap (bool) - hours_until_next_cheap (0 = start now) - cheap_window_ends, next_cheap_hour (UTC) - best_3h_window (always the true-optimal fixed 3h/6h window) - best_window (true-optimal CONTIGUOUS window sized to the `hours` param — use this, not cheap_hours, for "run this appliance for N hours straight" decisions; null if fewer than `hours` forecast rows are available) - recommendation ("run_high_consumption_tasks" / "normal_usage" / "avoid") Note: cheap_hours lists the N individually cheapest hours in the forecast and is NOT guaranteed to be contiguous — it can include hours scattered across the day, or (when the forecast has fewer than `hours` rows available) can end up including comparatively expensive hours simply because there aren't enough cheaper ones yet published. Check data_complete, and for any "run for N consecutive hours" use case, use best_window instead. All timestamps are UTC — convert to local time before presenting. data_complete: false = treat signals with caution. Not available: AU, NZ, KR, KR-JEJU, ZA, PH-LUZ, PH-VIS, PH-MIN. Args: zone: Any supported zone (see spot_price for full list). Use exact codes only — do not guess or abbreviate. AU, NZ, KR, KR-JEJU, ZA, PH-* return available: false. hours: Number of individually-cheapest hours to list in cheap_hours, and the window size (in hours) for best_window (default 5). window: Hours to look ahead (default 24).

NameTypeReqDescription
hoursintegerNumber of cheapest hours to return. Default: 5. Range: 1–24.
windowintegerHours ahead to look. Default: 24. Range: 1–48.
zonestringElectricity market zone code. AU, NZ, KR, ZA, PH-* return available: false. See spot_price for full zone list.

No output schema declared.

No examples provided.

spot_price ~713

PRICE NOW tool. Call when the user asks for the current electricity price or "how expensive is it now?". This is the authoritative real-time source. Never guess electricity prices. Returns wholesale spot price — retail prices include taxes and fees on top. Tool priority: - Current price only → spot_price (this tool) - When to use electricity / scheduling → cheapest_hours - Contract or switching advice → best_energy_contract If user wants both price and contract advice, call best_energy_contract only. Args: zone: Bidding zone. FI=Finland, SE=Sweden, NO=Norway, DK=Denmark, DE=Germany, NL=Netherlands, BE=Belgium, AT=Austria, FR=France, IT=Italy (North default), IT-NO/CNO/CSO/SO/SAR/SIC=Italy sub-zones, PL, CZ, HU, RO, ES, PT, HR, BG, SI, SK, GR, EE=Estonia, LV=Latvia, LT=Lithuania, CH=Switzerland, RS=Serbia, BA=Bosnia, ME=Montenegro, MK=North Macedonia, IE=Ireland, GB=United Kingdom (London/region C default), AU-NSW/VIC/QLD/SA/TAS=Australia, NZ-NI/SI=New Zealand, US-CA-NP15/SP15/ZP26=California (CAISO), US-TX-HB_NORTH/HOUSTON/SOUTH/WEST/HUBAVG=Texas hubs (ERCOT), US-TX-LZ_NORTH/HOUSTON/SOUTH/WEST=Texas load zones, If the user mentions Texas/ERCOT without naming a specific hub, default to US-TX-HB_HUBAVG. Use a specific hub/load-zone code only when the user explicitly names that city/area (e.g. "Houston", "North Texas"). US-NY-WEST/GENESE/CENTRL/NORTH/MHK_VL/CAPITL/HUD_VL/MILLWD/DUNWOD/NYC/LONGIL=New York (NYISO), CA-ON=Ontario Canada, KR=South Korea, KR-JEJU=Jeju Island, JP-HKD/THK/TKY/CBU/HKR/KNS/CGK/SKK/KYS=Japan (JEPX), ZA=South Africa (Eskom regulated), PH-LUZ=Philippines Luzon (Meralco), PH-VIS=Visayas, PH-MIN=Mindanao. Sub-zones: SE1-SE4, N…

NameTypeReqDescription
zonestringElectricity market zone code. Examples: FI, DE, GB, US-NY-NYC, JP-TKY, AU-NSW, ZA, PH-LUZ, MX-CUN. Full list in tool description.

No output schema declared.

No examples provided.

Common questions

What is the Elecz Electricity Price Signal API MCP server?

Elecz Electricity Price Signal API is an MCP server listed in the public MCP registry as io.github.zemloai-ctrl/elecz. Real-time electricity prices for AI agents. 40+ countries, 100+ zones. No auth required. This page covers its hosted endpoint (https://elecz.com/mcp).

Is the Elecz Electricity Price Signal API MCP server safe to use?

Elecz Electricity Price Signal API scores 85 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 Elecz Electricity Price Signal API MCP server expose?

Elecz Electricity Price Signal API exposes 3 tools: spot_price, cheapest_hours, best_energy_contract. Their descriptions and schemas cost roughly 2,053 tokens of context every time the server is loaded.

Does the Elecz Electricity Price Signal API MCP server require authentication?

No. We connected to Elecz Electricity Price Signal API without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Elecz Electricity Price Signal API MCP server still maintained?

Elecz Electricity Price Signal API is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.