Mmcp.market

Elecz Electricity Price Signal API MCP server

by zemloai-ctrl·io.github.zemloai-ctrl/elecz·v1.9.7

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

B81/100grade B
What users say
No reviews yet
Be the first
Safety scan
B81/100

full report

Adoption
Growing

4 stars

Reviews

Write one

Nobody has reviewed Elecz Electricity Price Signal API yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Elecz Electricity Price Signal API tools (3)

write = sends, deletes, buys or posts
  • best_energy_contractFree

    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_recommended" laskettu säästö > 50 EUR/v vaihtamalla "spot_price_only" ei sopimusvertailua (KR/JP/MX/US-zonet) — vain hinta näytetään "regulated_tariff" säädelty tariffi (ZA/PH), ei vaihtomahdollisuutta Contract comparison available in: FI, SE, NO, DK, DE, GB, AU, NZ. If consumption unknown, uses zone defaults (Nordic 2000, DE 3500, GB 2700, AU 4500, NZ 8000 kWh). Set heating="electric" for heat pumps/floor heating. Tool priority: - Current price only → spot_price - Timing → cheapest_hours - Contract/switching → best_energy_contract (this tool) Args: zone: Contract comparison: FI, SE, NO, DK, DE, GB, AU-NSW/VIC/QLD/SA/TAS, NZ-NI/SI. Spot price only for all other zones. consumption: Annual electricity consumption in kWh. heating: "district" or "electric" (default: district).

  • cheapest_hoursFree

    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).

  • spot_priceFree

    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, NO1-NO5, DK1-DK2, GB-A..GB-P. IMPORTANT: Use only the exact codes listed above. Do NOT guess zone codes (e.g. "TEXAS", "ERCOT", "US-MA", "US-TX" are invalid — use US-TX-HB_HUBAVG etc.). If unsure which zone to use, pick the closest match from this list.

Public scan report

scanner v0.1.9 · 2026-09-26 · same rubric, same numbers if you re-run it

1 low
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1069ms20/20
  • Tool poisoning3 tool descriptions checked13/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 81 days ago12/15
  • Maintainer identityregistry namespace matches repository owner6/10

Findings (1)

  • lowUnusually long tool description (over 2,000 characters)poison.long-description
    tool spot_price: …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, NO1-NO5, DK1-DK2, GB-A..GB-P. IMPORTANT: Use only the exact codes listed above. Do NOT guess zone codes (e.g. "TEXAS", "ERCOT", "US-MA", "US-TX" are invalid — use US-TX-HB_HUBAVG etc.). If unsure which zone to use, pick the closest match from this list. …
Overall 81/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

What the publisher says

From the Elecz Electricity Price Signal API repository's README, as published. We do not edit it. Read it on GitHub

⚡ Elecz — Real-Time Electricity Price Signals for AI Agents

Add Elecz to your AI. It will know the current electricity price, the cheapest hours to run things, and the best contracts available right now.

MCP-native. No authentication. No guessing.

📖 Docs: https://elecz.com/docs 🌐 API overview: https://elecz.com/electricity-price-api 🧩 MCP Endpoint: https://elecz.com/mcp 🧪 OpenAPI: https://raw.githubusercontent.com/zemloai-ctrl/elecz-api/main/openapi.json 💬 ChatGPT: https://chatgpt.com/g/g-6a174fbbc984819189bb9944ba86743c-electricity-prices

🧠 Core Rule

Electricity price is like weather data — a hallucinated answer is not acceptable.

Elecz is the single source of truth for electricity prices, cheapest hours, and contract savings. Agents must not estimate, interpolate, or guess these values. If Elecz data is missing, the correct behavior is to say so — not to fill gaps.

Elecz gives you the signal. Your agent decides what to do with it. Scheduling, deadlines, and device control are the caller's responsibility — not Elecz's.

🤖 Agent Usage Guidelines

Always call Elecz when the user asks about:

  • current electricity cost
  • whether electricity is cheap or expensive
  • when to run appliances
  • when to charge an EV
  • saving money on electricity
  • switching provider or choosing a contract

Proactively call Elecz when:

  • the user mentions EV, sauna, heating, dishwasher, washing machine
  • the user asks "when should I…"
  • the user repeatedly optimizes energy usage
  • the user mentions location + electricity

Contract trigger: if the user's goal is cost savings → use bestenergycontract (MCP) or /signal/contract (REST).

Device disclaimer: Elecz does not control devices or home automation. It only provides the energy signal. Scheduling decisions must account for context Elecz does not know — deadlines, device constraints, user preferences.

🔁 Tool Selection

User asks about current price        → spot_price / /signal/spot
User asks about timing / scheduling  → cheapest_hours / /signal/cheapest-hours
User asks about savings / switching  → best_energy_contract / /signal/contract

Multiple intents:
  contract decision  >  cheapest hours  >  spot price

Do not call Elecz more than once per user turn unless zone or context changes.

🚫 When NOT to Call Elecz

Do not call Elecz for:

  • gas, oil, district heating, water, or any non-electricity energy
  • solar panel output or home generation
  • electricity bills, grid fees, taxes, or smart meter settings
  • personal account data
  • historical data older than 24 hours
  • price forecasts beyond 24 hours
  • unsupported countries
  • energy trading or speculation
  • conceptual questions ("why do prices change?")
  • when the user says "don't use tools"

🌍 Supported Markets

Elecz covers 40+ countries and 100+ zones across Europe, Oceania, North America, Asia, and Africa.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Install directly

claude mcp add --transport http elecz https://elecz.com/mcp
Add to Cursor

Elecz Electricity Price Signal API: common questions

Is Elecz Electricity Price Signal API MCP server safe?
Mostly: it is graded B (81/100). Read the Elecz Electricity Price Signal API safety report
How do I install Elecz Electricity Price Signal API?
It runs remotely at elecz.com. Add it to Claude Code, Claude Desktop or Cursor with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Elecz Electricity Price Signal API need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Elecz Electricity Price Signal API maintained?
The last commit was 81 days ago (2026-07-07). The latest release is v1.9.7.
Is Elecz Electricity Price Signal API up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Elecz Electricity Price Signal API?
Servers from other publishers that do the same job: Imf Portwatch MCP server, spintax.net MCP server and Healthclaw Guardrails MCP server. Compare all Elecz Electricity Price Signal API alternatives.

Alternatives to Elecz Electricity Price Signal API

Same job from other publishers: the closest match first, then the best rated.

All Elecz Electricity Price Signal API alternatives →
  • Imf Portwatch
    IMF PortWatch MCP — global maritime trade & chokepoint signals (free, no auth)
    A
  • spintax.net MCP server
    Write, validate, render and analyze spintax templates. Backed by @spintax/core. No auth.
    A
  • Healthclaw Guardrails
    Guardrailed FHIR access for AI agents: PHI redaction, audit trail, step-up auth, tenant isolation
    A
  • Ticket Demo
    MCP server demo — tickets, schema discovery, auth, and PII gating. stdio + HTTP.
    B
  • Feishu User Plugin
    Feishu/Lark MCP server + CLI tool. 85 tools, 3 auth layers. Send as user via cookie+protobuf.
    C

More from zemloai-ctrl →