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.

entsoe-mcp

REMOTE · ENTSOEMCP.COM

European power-market data: day-ahead & balancing prices, load, generation, flows, outages. 47 zones

Available components

+4 this week 84 Trust /100

Last scanned (16 hours ago)

Scores higher than 84% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Data and Analytics

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 Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability69
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 5459 tokens (~303/item across 18 items; 14 tools + 4 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 Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 19 Nov 26 0
    • Tool “data_coverage” rewrote its description, which is the text the model reads security
    • Tool “get_series” rewrote its description, which is the text the model reads security
  • 18 Nov 26 0
    • Tool “get_generation” rewrote its description, which is the text the model reads security
    • Tool “get_series” rewrote its description, which is the text the model reads security
  • 17 Nov 26 +4
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “data_coverage” rewrote its description, which is the text the model reads security
    • Tool “get_derivation” rewrote its description, which is the text the model reads security
    • Tool “get_load” rewrote its description, which is the text the model reads security
    • Tool “get_series” rewrote its description, which is the text the model reads security
    • Tool “list_derivations” rewrote its description, which is the text the model reads security
    • Resource “_coverage” was removed ▼ functional
    • Resource “_endpoints” was removed ▼ functional
    • Resource “_psr_types” was removed ▼ functional
    • Resource “_zones” was removed ▼ functional
    • Schema quality: 43% → 100% ▲ functional
    • New resource “coverage” functional
    • New resource “endpoints” functional
    • New resource “psr-types” functional
    • New resource “zones” functional
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
    • Tool “get_outages” rewrote its description, which is the text the model reads security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 8 Nov 26 0
    • Stability: 0.97 → pass security
  • 7 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 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 21 Nov 2026 · Probed https://entsoemcp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=entsoemcp.com CN=YE2,O=Let's Encrypt,C=US 3 Nov 2026 1 Feb 2027 ECDSA 256 ECDSA-SHA384 60a4b81fe0c3c8384394255633188e0c386
SANs: entsoemcp.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of entsoemcp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
entsoemcp.com. No DS 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
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload
x-content-type-options nosniff
x-frame-options DENY
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://entsoemcp.com/mcp Verified 200
http (plaintext) http://entsoemcp.com/mcp HTTPS enforced 308 https://entsoemcp.com/mcp
MCP tools · 14 exposed · ~4,234 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
compare_zones ~223

Compare one endpoint across multiple zones. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. `tz="local"` is rejected (zones may differ); pass an explicit IANA tz like "Europe/Berlin" if you need wall-clock alignment. `filters={column: [values]}` keeps only rows whose categorical column holds one of the values, in every zone (see get_series); zones whose periods hold several rows are listed under `split_periods_by_zone`. A zone whose series stopped upstream before the window's end (GB day-ahead after 2020-12-31) is listed under `series_ended_by_zone`, with the endpoint that carries it on — an empty `[]` there is not "no data yet".

NameTypeReqDescription
aggregationstring––
endstringyes–
endpointstringyes–
filters–––
startstringyes–
tz–––
zonesarrayyes–

Structured output declared, but exposes no named fields.

No examples provided.

data_coverage ~80

Show what data is available and how current it is for (endpoint × zone) — call before querying if you're not sure a recent date is available yet. Each pair's newest year carries `latest_data_at`, its newest stored record; `lag` grades every pair on how old that record is.

NameTypeReqDescription
endpoint–––
zone–––

Structured output declared, but exposes no named fields.

No examples provided.

get_crossborder_flow ~105

Cross-border physical flow (MW) between two adjacent zones. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. `tz="local"` uses the FROM-zone's timezone; or pass an IANA name.

NameTypeReqDescription
aggregationstring––
endstringyes–
from_zonestringyes–
startstringyes–
to_zonestringyes–
tz–––

Structured output declared, but exposes no named fields.

No examples provided.

get_day_ahead_prices ~417

Day-ahead clearing price for a bidding zone, in the zone's trading currency (EUR for euro zones; the per-row `currency` column and the response `unit` say which — GB=GBP, PL/RO/BG carry local-currency eras). `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For 'all of April 2026' use start=2026-04-01, end=2026-05-01 (end=2026-04-30 silently drops the final UTC day — and 1–2 local-time hours of April for European zones in CET/CEST). The response's `period` block shows the resolved window so you can verify (a 30-day month is 720 hours). `tz`: pass "local" to interpret start/end as wall-clock in the zone's timezone, or an explicit IANA name like "Europe/Berlin". The server converts to UTC at the boundary. GB/UK: ENTSO-E's GB day-ahead price ended 2020-12-31, when GB left European market coupling. For later windows use `get_series(endpoint="day_ahead_price_imrp", zone="GB", …)` — the same GB day-ahead auction, GBP/MWh, published ~D-2; a window past a series' end answers with `series_ended`, naming the endpoint that carries it on. If you're computing a **generation-weighted** price metric — capture price, capture rate, value factor, merchant-PPA achieved price — use `get_derivation(slug="capture_price", …)` instead. It runs server-side over the full window and returns monthly rows; no row cap, no pagination.

NameTypeReqDescription
aggregationstring––
endstringyes–
startstringyes–
tz–––
zonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_derivation ~1,015

Compute **capture price**, **capture rate** (a.k.a. value factor / quality factor / Marktwertfaktor), **TBx battery-arbitrage spreads**, and other generation-weighted market metrics server-side from the stored data. Use this instead of fetching hourly prices + hourly generation yourself and weighting them client-side — server-side aggregation has no row cap and no pagination. `slug`: a key from list_derivations() — today: `"capture_price"`, `"negative_price_hours"`, `"residual_load"`, `"res_share"`, `"emissions"`, `"tb_spread"`. `tb_spread` returns monthly (default) or annual (aggregation='annual') Top-Bottom spreads TB1/TB2/TB4/TB6 in <currency>/MW per period — the sum of daily (top-x minus bottom-x hourly prices) over SDAC market days. The only slug accepting `aggregation`, and the only one accepting multi-zone `zone` ('all', a list, or CSV). Example — annual TB2 across every European market in ONE call: get_derivation("tb_spread", "2025-01-01", "2026-01-01", zone="all", aggregation="annual") For a single day's top/bottom hour TIMESTAMPS use get_tb_spread. `capture_price` returns monthly rows per (zone, psr_type, currency) with columns: currency, capture_price_eur_per_mwh, baseload_price_eur_per_mwh, quality_factor (the capture rate = capture/baseload), total_gen_mwh, n_hours. Months are bucketed by local time using the zone's IANA timezone. ENDED INPUTS: when an input series stopped upstream before the window's end, the answer carries `series_ended` (per zone for a multi-zone tb_spread): which inputs, why, what carries each on, and any metric that carries this one on. GB: ENTSO-E's day-ahead price ended 2020-12-31, so GB capture_price, negative_price_hours and tb_spread stop there; `capture_price_mid` covers GB 2016-09 → now against the Market Index Price (a traded index, not the auction — read its note). CURRENCY (capture_price and tb_spread alike): the `*_eur_per_mwh` / `tb*_eur_per_mw` key names are FIXED for API stability and do NOT t…

NameTypeReqDescription
aggregation–––
endstringyes–
from_zone–––
psr_types–––
slugstringyes–
startstringyes–
to_zone–––
tz–––
zone–––

Structured output declared, but exposes no named fields.

No examples provided.

get_generation ~316

Aggregated generation (MW) per production type. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For a full calendar month set `end` to the first day of the next month. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone. GB/UK: ENTSO-E's GB generation ended 2021-06-15. For later windows in the same ENTSO-E codes use `get_series(endpoint="generation_per_type_elexon", zone="GB", …)` (Elexon, from 2021); for NESO's mix with its estimate of embedded wind use `get_series(endpoint="generation_mix", zone="GB", …)` (2009→now, its own wind codes — `list_psr_types(zone="GB")` first). A window past a series' end answers with `series_ended`, naming both. If you're computing a **generation-weighted** price metric — capture price, capture rate, value factor, merchant-PPA achieved price — use `get_derivation(slug="capture_price", …)` instead. It runs server-side over the full window and returns monthly rows; no row cap, no pagination.

NameTypeReqDescription
aggregationstring––
endstringyes–
psr_types–––
startstringyes–
tz–––
zonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_load ~197

Actual or forecast load (MW). kind = actual | forecast | both. `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. For a full calendar month set `end` to the first day of the next month. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone. GB/UK: ENTSO-E's GB load ended 2021-06-15. A later window answers with `series_ended` naming `demand_outturn_transmission` (Elexon) — national demand at the transmission boundary, ~5.5 GW below total load, not the same quantity.

NameTypeReqDescription
aggregationstring––
endstringyes–
kindstringyes–
startstringyes–
tz–––
zonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_outages ~248

Generation-unit unavailability events (UMM). `start`/`end` default to UTC; `start` inclusive, `end` EXCLUSIVE. An outage is returned if it overlaps the window. Pass `tz="local"` or an IANA name to interpret start/end as wall-clock in that timezone. Each row is one unit's availability step, from its document's latest revision. ENTSO-E lists some outages under several documents with identical rows; each such row is served once, and `copies` counts the documents that filed it. A unit can still have several overlapping rows that differ. To total unavailable MW, count each unit once per instant (its largest unavailable MW), not the sum of its rows. A zone whose outage feed stopped upstream (GB, 2021-06-15) carries `series_ended`: outages announced since then are missing, though older documents may still schedule events into the window.

NameTypeReqDescription
endstringyes–
kindstring––
min_mw–––
startstringyes–
tz–––
zonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_series ~1,009

Generic time-series query for ANY registered series endpoint. One tool covers every dataset except outages (call `list_endpoints()` to see them all), so a new dataset needs no new tool to learn. Argument shape adapts to the endpoint: • single-zone (day_ahead_price, actual_load, generation_per_type, …) → pass `zone="DE_LU"` • cross-zone (crossborder_flow, scheduled_exchanges, net_transfer_capacity_dayahead) → pass `from_zone="DE_LU"` AND `to_zone="FR"` • psr-dependent (generation_per_type, wind_solar_forecast, installed_generation_capacity) → optionally filter via `psr_types=["solar","wind_onshore"]` `start`/`end`: UTC by default; `start` inclusive, `end` EXCLUSIVE (for "all of April 2026" use end=2026-05-01). Pass `tz="local"` or an IANA name to interpret as wall-clock in that timezone. `aggregation`: 'raw' (default — native PT15M/PT60M per endpoint), 'hourly' (AVG over quarters → one row per hour, useful for the growing list of PT15M-stored endpoints like DE_LU day_ahead_price), 'daily', or 'monthly'. For day-ahead prices specifically the auction still clears hourly even where stored at PT15M, so AVG=any-quarter; SUM would 4× over-count. Currency: price columns keep `_eur_` in their names for stability. An endpoint whose rows carry a `currency` column (day-ahead and intraday prices, the A81/A15 capacity prices, activated_balancing_price, imbalance_prices) labels each row (PLN, HUF, RON, CZK, GBP, …) and the response `unit` follows it; `unit` is null when the window mixes currencies (`mixed_currency`) or, for activated_balancing_price and imbalance_prices, holds rows of unknown currency (`currency_unknown_rows`). Never average a price across rows with different `currency`. Split periods: when a response carries `split_periods`, some periods hold more than one row — different published series told apart by the listed columns (activated_balancing_price: `product`, e.g. CZ/SK mFRR standard A01 vs specific A0…

NameTypeReqDescription
aggregationstring––
endstringyes–
endpointstringyes–
filters–––
from_zone–––
psr_types–––
startstringyes–
to_zone–––
tz–––
zone–––

Structured output declared, but exposes no named fields.

No examples provided.

get_tb_spread ~221

Top-Bottom (TBx) spread — daily battery-arbitrage benchmark. TBx = sum(top X priced hours) − sum(bottom X priced hours) over the day-ahead clearing prices for `zone` on `date`. The day is the SDAC market day (23/25 hours on DST-transition days). `date` must be a bare YYYY-MM-DD — time-bearing strings are rejected. Returns both `spread` (<currency>/MW/day) and `mean_spread` (<currency>/MWh = spread/X) in the zone's trading currency — see the response `currency`/`unit` (EUR for euro zones; GB=GBP). Common X: 1, 2, 4. A day past the zone's day-ahead series end (GB after 2020-12-31) answers with `series_ended`, naming the endpoint that carries the prices on.

NameTypeReqDescription
datestringyes–
xinteger––
zonestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

list_derivations ~161

List computed-metric derivations available via get_derivation(). Each derivation is a metric computed on the fly from one or more stored datasets. Today: capture_price (monthly VWAP capture price + baseload + capture rate per technology; "capture rate" is the industry-standard name for what the JSON response calls `quality_factor`), negative_price_hours, residual_load, res_share, emissions (monthly CO2 emissions per fuel using IPCC AR5 lifecycle factors, production-based), and tb_spread (monthly or annual Top-Bottom battery-arbitrage spread TB1/TB2/TB4/TB6 per zone on SDAC market days; accepts zone='all' for every zone in one call).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes–

No examples provided.

list_endpoints ~23

List supported ENTSO-E endpoint families.

NameTypeReqDescription
family–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

list_psr_types ~188

List production-type (psr_type) codes. Pass zone= to scope the answer. Most codes are ENTSO-E's B01..B25 and mean the same thing in every ENTSO-E zone. A few are source-native (source != "entsoe") and exist only where that source publishes — they express concepts the B-codes cannot, so they are NOT interchangeable with a similar-looking B-code. Check `source` and read `description` before comparing a code across zones. Passing zone= also returns `taxonomy_note` for zones that mix taxonomies (e.g. GB), and per-code `endpoints` showing where each code comes from. Each code carries `counts_as_generation`: when False the figure is a net flow or net storage number, not production — do not sum it into a generation total.

NameTypeReqDescription
zone–––

Structured output declared, but exposes no named fields.

No examples provided.

list_zones ~31

List registered ENTSO-E bidding zones.

NameTypeReqDescription
active_onlyboolean––
cluster–––
NameTypeReqDescription
resultarrayyes–

No examples provided.

Install

How do I install the entsoe-mcp server?

entsoe-mcp is a hosted endpoint at https://entsoemcp.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 · entsoemcp.com

# add to Claude Code
claude mcp add --transport http com-entsoemcp-entsoe-mcp 'https://entsoemcp.com/mcp'
Common questions

What is the entsoe-mcp server?

entsoe-mcp is listed in the public MCP registry as com.entsoemcp/entsoe-mcp. European power-market data: day-ahead & balancing prices, load, generation, flows, outages. 47 zones. This page covers its hosted endpoint (https://entsoemcp.com/mcp).

Is the entsoe-mcp server safe to use?

entsoe-mcp scores 84 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 entsoe-mcp server expose?

entsoe-mcp exposes 14 tools: list_zones, list_endpoints, list_psr_types, get_series, get_day_ahead_prices, and 9 more. Their descriptions and schemas cost roughly 4,234 tokens of context every time the server is loaded.

Does the entsoe-mcp server require authentication?

No. We connected to entsoe-mcp without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the entsoe-mcp server still maintained?

entsoe-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the entsoe-mcp server?

VerifyMCP ran 13 checks on entsoe-mcp, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.