entsoe-mcp server
com.entsoemcp/entsoe-mcpentsoemcp.comstreamable-httpv1.0.0Scanned
European power-market data: day-ahead & balancing prices, load, generation, flows, outages. 47 zones
14 tools: 14 only read.
- Reads private data · 0
- Reads text others write · 3
- Can send data out · 3
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
Decide which of this server's tools your agent can use.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the entsoe-mcp server can do
The entsoe-mcp server is published by entsoemcp.com, a domain the MCP Registry verified. It has 14 tools. Every one of them only reads: going by their definitions, none of them creates, changes, sends or deletes anything.
3 tools bring in text other people can write (get_series, compare_zones and data_coverage); 3 tools can send data out of your system (get_series, compare_zones and data_coverage).
The fixed checks matched 2 findings (long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 13, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
14 tools
Only reads 14Show 14 read-only tools
compare_zonesCompare one endpoint across multiple zones.Reads text others writeCan send data outNo findings
Why it is in this group
- The name "compare_zones" says "compare": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it 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".
Annotations the server declares
- title: Compare zones
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
data_coverageShow ingest coverage and lag for (endpoint × zone) — call before queries if you're not sure whether the data is landed yet.Reads text others writeCan send data outNo findings
Why it is in this group
- The description's first verb is "show": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Description, as the server wrote it Show ingest coverage and lag for (endpoint × zone) — call before queries if you're not sure whether the data is landed yet.
Annotations the server declares
- title: Check data coverage
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_crossborder_flowCross-border physical flow (MW) between two adjacent zones.No findings
Why it is in this group
- The name "get_crossborder_flow" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get cross-border flow
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_day_ahead_pricesDay-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 …No findings
Why it is in this group
- The name "get_day_ahead_prices" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get day-ahead prices
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_derivationCompute **capture price**, **capture rate** (a.k.a.1 finding
Why it is in this group
- The name "get_derivation" says "get": a word for reading.
Findings
- Info
The description is 3,617 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...="DE_LU", tz="Europe/Berlin") Returns 12 monthly rows in one call; no pagination."
Description, as the server wrote it 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. 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 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 sum a price column across rows with different `currency` values. Summing `total_gen_mwh` across them IS correct: the split rows partition the month's hours rather than duplicating them. `quality_factor` is a ratio and stays comparable across currencies. `emissions` returns monthly rows per (zone, psr_type) with columns: generation_mwh, n_hours, emission_factor_kg_per_mwh, emissions_t_co2. Production-based; IPCC AR5 lifecycle factors. Zero-emission rows (nuclear, wind, solar, hydro, geothermal, marine) appear with emissions_t_co2 = 0 — useful for stacked charts. Filter via `psr_types=["solar","wind_onshore","wind_offshore"]` (or raw B-codes like "B16") to get only the technologies you care about. Defaults to all psr_types that have generation data. Example — Spain solar capture price, last 12 months: get_derivation("capture_price", "2025-05-01", "2026-05-01", zone="ES", psr_types=["B16"], tz="Europe/Madrid") Example — Germany 2024 emissions by fuel: get_derivation("emissions", "2024-01-01", "2025-01-01", zone="DE_LU", tz="Europe/Berlin") Returns 12 monthly rows in one call; no pagination.
Annotations the server declares
- title: Get a derived metric
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_generationAggregated generation (MW) per production type.No findings
Why it is in this group
- The name "get_generation" says "get": a word for reading.
Description, as the server wrote it 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 use `get_series(endpoint="generation_mix", zone="GB", …)` (NESO, 2009→now, its own wind codes — `list_psr_types(zone="GB")` first); a window past a series' end answers with `series_ended`, naming that endpoint. 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.
Annotations the server declares
- title: Get generation by fuel
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_loadActual or forecast load (MW).No findings
Why it is in this group
- The name "get_load" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get load (actual or forecast)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_outagesGeneration-unit unavailability events (UMM).No findings
Why it is in this group
- The name "get_outages" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get generation outages
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_seriesGeneric time-series query for ANY registered series endpoint.Reads text others writeCan send data out1 finding
Why it is in this group
- The name "get_series" says "get": a word for reading.
What it can reach
- untrusted-inputThe input takes a URL (input.endpoint), and the tool reads it: it reads web pages, which anyone can write.
- outboundThe input takes a URL (input.endpoint): a request to a URL can carry data to whoever runs it.
Claude Code: ask, because it is tagged outbound.
Findings
- Info
The description is 3,018 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "..._mix (NESO). Outage-family endpoints (different schema) stay on `get_outages()`."
Description, as the server wrote it 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. 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 A02; or `currency`). Never average across them. Keep one with `filters={"product": ["A01"]}` — `filters` takes any categorical column of the endpoint (`{column: [values]}`). Process types: activated balancing prices are one endpoint per ENTSO-E processType (activated_balancing_price = A16 realised; _mfrr_scheduled = A60, _mfrr_direct = A61, _afrr_local = A68) — different prices for the same period, never to be merged. `related_series` names the siblings holding data for the zone. Ended series: a window reaching past the day a series stopped upstream (a zone that left ENTSO-E, a frozen archive, a series that ended) carries `series_ended` — the last day, why, and `successors`: the endpoints that carry it on, each with a ready `call` and a `note` on how it differs. GB day-ahead after 2020-12-31 → day_ahead_price_imrp (GBP/MWh); GB generation after 2021-06-15 → generation_mix (NESO). Outage-family endpoints (different schema) stay on `get_outages()`.
Annotations the server declares
- title: Get a time series
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_tb_spreadTop-Bottom (TBx) spread — daily battery-arbitrage benchmark.No findings
Why it is in this group
- The name "get_tb_spread" says "get": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Get top-bottom spread
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_derivationsList computed-metric derivations available via get_derivation().No findings
Why it is in this group
- The name "list_derivations" says "list": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- title: List derived metrics
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_endpointsList supported ENTSO-E endpoint families.No findings
Why it is in this group
- The name "list_endpoints" says "list": a word for reading.
Description, as the server wrote it List supported ENTSO-E endpoint families.
Annotations the server declares
- title: List data endpoints
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_psr_typesList production-type (psr_type) codes.No findings
Why it is in this group
- The name "list_psr_types" says "list": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: List production types
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
list_zonesList registered ENTSO-E bidding zones.No findings
Why it is in this group
- The name "list_zones" says "list": a word for reading.
Description, as the server wrote it List registered ENTSO-E bidding zones.
Annotations the server declares
- title: List bidding zones
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write3
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out3
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:37 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 0
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
Findings
Matches of fixed checks, with the text they matched.
- Infoget_series
The description is 3,018 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "..._mix (NESO). Outage-family endpoints (different schema) stay on `get_outages()`."
- Infoget_derivation
The description is 3,617 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...="DE_LU", tz="Europe/Berlin") Returns 12 monthly rows in one call; no pagination."
History
Changes to its tool definitions and to its remote endpoint, newest first.
Tools1 changed.~1 changedView diff
- Changed:get_outagesOnly readsdescription
Tools7 changed.~7 changedView diff
- Changed:compare_zonesOnly readsdescription
- Changed:get_day_ahead_pricesOnly readsdescription
- Changed:get_derivationOnly readsdescription
- Changed:get_generationOnly readsdescription
- Changed:get_outagesOnly readsdescription
- Changed:get_seriesOnly readsdescription
- Changed:get_tb_spreadOnly readsdescription
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http entsoe https://entsoemcp.com/mcpclaude mcp add --transport http entsoe https://entsoemcp.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__entsoe__list_zones",
"mcp__entsoe__list_endpoints",
"mcp__entsoe__list_psr_types",
"mcp__entsoe__get_day_ahead_prices",
"mcp__entsoe__get_tb_spread",
"mcp__entsoe__get_load",
"mcp__entsoe__get_generation",
"mcp__entsoe__get_crossborder_flow",
"mcp__entsoe__get_outages",
"mcp__entsoe__list_derivations",
"mcp__entsoe__get_derivation"
],
"ask": [
"mcp__entsoe__get_series",
"mcp__entsoe__compare_zones",
"mcp__entsoe__data_coverage"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as entsoe. Review it before you use it.
Capability tags behind 3 rules
- mcp__entsoe__get_series untrusted-input, outbound
- mcp__entsoe__compare_zones untrusted-input, outbound
- mcp__entsoe__data_coverage untrusted-input, outbound
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/com.entsoemcp/entsoe-mcp/verify?hash=fa8e1e2130e8dfc2f5c971566a1456a08676be0319267793fbb98a08298c4675" | jq -e '.changed == false'Pinned hash fa8e1e2130e8, from Nov 13, 2026, 04:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/com.entsoemcp/entsoe-mcp/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/com.entsoemcp/entsoe-mcp)Source: MCP Registry. Synced Oct 21, 2026, 17:54 UTC.
entsoe-mcp server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the entsoe-mcp server safe?
- No scan can promise that. What its definitions show: 14 tools, all of which only read, and 2 findings from fixed checks. Read-only tools can still pass private data to a model.
Can the entsoe-mcp server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the entsoe-mcp server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the entsoe-mcp server have?
- 14 tools: 14 read. list_zones, list_endpoints, list_psr_types, get_series, get_day_ahead_prices, get_tb_spread, get_load, get_generation and 6 more.
Does the entsoe-mcp server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the entsoe-mcp server send data to outside services?
- 3 tools can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): get_series, compare_zones and data_coverage.
Has the entsoe-mcp server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 13, 2026. Every change is on this page and in its Atom feed.