# entsoe-mcp (remote · entsoemcp.com)

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

- Trust score: 79/100 (medium)
- Change this week: +10
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `entsoemcp.com`: 79/100 (this document), [markdown](https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp.md), [page](https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp)

## Channel facts

- Endpoint: `https://entsoemcp.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-24.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 49/100
  - 43% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3860 tokens (~214/item across 18 items; 14 tools + 4 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 87/100
  - Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

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

### Claude

```bash
claude mcp add --transport http com-entsoemcp-entsoe-mcp 'https://entsoemcp.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-entsoemcp-entsoe-mcp": {
      "url": "https://entsoemcp.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-entsoemcp-entsoe-mcp": {
      "type": "http",
      "url": "https://entsoemcp.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-entsoemcp-entsoe-mcp]
url = "https://entsoemcp.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-entsoemcp-entsoe-mcp": {
      "type": "remote",
      "url": "https://entsoemcp.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-entsoemcp-entsoe-mcp --url 'https://entsoemcp.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-entsoemcp-entsoe-mcp:
    url: "https://entsoemcp.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-entsoemcp-entsoe-mcp": {
      "Transport": "http",
      "Url": "https://entsoemcp.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-entsoemcp-entsoe-mcp -t streamable-http -u 'https://entsoemcp.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-entsoemcp-entsoe-mcp": {
      "type": "http",
      "url": "https://entsoemcp.com/mcp"
    }
  }
}
```

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

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-24 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-23 (score 78, +7)

- [security improvement] Authorization: unverified → partial
- [cosmetic] Tool “compare_zones” changed its title: Compare zones
- [cosmetic] Tool “data_coverage” changed its title: Check data coverage
- [cosmetic] Tool “get_crossborder_flow” changed its title: Get cross-border flow
- [cosmetic] Tool “get_day_ahead_prices” changed its title: Get day-ahead prices
- [cosmetic] Tool “get_derivation” changed its title: Get a derived metric
- [cosmetic] Tool “get_generation” changed its title: Get generation by fuel
- [cosmetic] Tool “get_load” changed its title: Get load (actual or forecast)
- [cosmetic] Tool “get_outages” changed its title: Get generation outages
- [cosmetic] Tool “get_series” changed its title: Get a time series
- [cosmetic] Tool “get_tb_spread” changed its title: Get top-bottom spread
- [cosmetic] Tool “list_derivations” changed its title: List derived metrics
- [cosmetic] Tool “list_endpoints” changed its title: List data endpoints
- [cosmetic] Tool “list_psr_types” changed its title: List production types
- [cosmetic] Tool “list_zones” changed its title: List bidding zones

### 2026-09-22 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-19 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-17 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-15 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-13 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-11 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (14)

### `list_zones` (~31 tokens)

List bidding zones

List registered ENTSO-E bidding zones.

Input parameters:

- `active_only` (boolean)
- `cluster`

Output parameters:

- `result` (array)

### `list_endpoints` (~23 tokens)

List data endpoints

List supported ENTSO-E endpoint families.

Input parameters:

- `family`

Output parameters:

- `result` (array)

### `list_psr_types` (~188 tokens)

List production types

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.

Input parameters:

- `zone`

### `get_series` (~413 tokens)

Get a time series

Generic time-series query for ANY registered series endpoint.

One tool covers every (non-outage) endpoint in the registry, so adding
a new dataset (call `list_endpoints()` to see the current 14) gets an
MCP surface automatically — 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.

Outage-family endpoints (different schema) stay on `get_outages()`.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `endpoint` (string, required)
- `from_zone`
- `psr_types`
- `start` (string, required)
- `to_zone`
- `tz`
- `zone`

### `get_day_ahead_prices` (~321 tokens)

Get day-ahead prices

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.

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.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `start` (string, required)
- `tz`
- `zone` (string, required)

### `get_tb_spread` (~182 tokens)

Get top-bottom spread

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.

Input parameters:

- `date` (string, required)
- `x` (integer)
- `zone` (string, required)

### `get_load` (~127 tokens)

Get load (actual or forecast)

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.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `kind` (string, required)
- `start` (string, required)
- `tz`
- `zone` (string, required)

### `get_generation` (~187 tokens)

Get generation by fuel

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.

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.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `psr_types`
- `start` (string, required)
- `tz`
- `zone` (string, required)

### `get_crossborder_flow` (~105 tokens)

Get cross-border flow

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.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `from_zone` (string, required)
- `start` (string, required)
- `to_zone` (string, required)
- `tz`

### `get_outages` (~115 tokens)

Get generation outages

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.

Input parameters:

- `end` (string, required)
- `kind` (string)
- `min_mw`
- `start` (string, required)
- `tz`
- `zone` (string, required)

### `compare_zones` (~111 tokens)

Compare zones

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.

Input parameters:

- `aggregation` (string)
- `end` (string, required)
- `endpoint` (string, required)
- `start` (string, required)
- `tz`
- `zones` (array, required)

### `data_coverage` (~46 tokens)

Check data coverage

Show ingest coverage and lag for (endpoint × zone) — call before queries
if you're not sure whether the data is landed yet.

Input parameters:

- `endpoint`
- `zone`

### `list_derivations` (~169 tokens)

List derived metrics

List computed-metric derivations available via get_derivation().

Each derivation is a metric computed on-the-fly from one or more
landed endpoints (Tier-2 Parquet). 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).

Output parameters:

- `result` (array)

### `get_derivation` (~888 tokens)

Get a derived metric

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 landed
Parquet. 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.

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 track
the actual unit — read the row's `currency` column, which is
authoritative (EUR for euro zones, GBP for GB, PLN/RON/BGN for the
PL/RO/BG local-currency eras). The response echoes it top-level as
\`currency`; a window spanning two currencies instead sets `unit` to null
with `mixed_currency: true` and a `currencies` list. A month (or period)
spanning a redenomination splits into one row PER CURRENCY, each computed
only from that currency's hours — so never average or su…

Input parameters:

- `aggregation`
- `end` (string, required)
- `from_zone`
- `psr_types`
- `slug` (string, required)
- `start` (string, required)
- `to_zone`
- `tz`
- `zone`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp#diagnostics

## Score history

- 2026-09-24: 79
- 2026-09-23: 78
- 2026-09-22: 71
- 2026-09-21: 70
- 2026-09-20: 70
- 2026-09-19: 70
- 2026-09-18: 69
- 2026-09-17: 69
- 2026-09-16: 68
- 2026-09-15: 68
- 2026-09-14: 67
- 2026-09-13: 67
- 2026-09-12: 66
- 2026-09-11: 66
- 2026-09-10: 65
- 2026-09-09: 65
- 2026-09-08: 64
- 2026-09-07: 64
- 2026-09-06: 63
- 2026-09-05: 63
- 2026-09-04: 63
- 2026-09-03: 62
- 2026-09-02: 59
- 2026-09-01: 59
- 2026-08-31: 58
- 2026-08-30: 58
- 2026-08-29: 57

## 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 79 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 2,906 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 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://entsoemcp.com/mcp
- Website: https://entsoemcp.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp.json
- HTML version of this page: https://verifymcp.io/servers/com-entsoemcp-entsoe-mcp/entsoemcp