Alpaca Trading API integration for Model Context Protocol (MCP)
Nothing to run from here
Entsoe is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
14
tools declared
—
trust score
remote
at its publisher
—
calls last 7d
What it does
European power-market data: day-ahead & balancing prices, load, generation, flows, outages. 47 zones
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http entsoe-mcp https://entsoemcp.com/mcp
# 2 — ask your agent for something these tools do
# list_zones, list_endpoints, list_psr_types and 11 more
Entsoe costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
ENAll 1 server
entsoemcp1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http entsoe-mcp https://entsoemcp.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
14 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List registered ENTSO-E bidding zones.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| active_only | boolean | no | — |
| cluster | no | — |
List supported ENTSO-E endpoint families.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| family | no | — |
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 compari
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| zone | no | — | |
| from_zone | no | — | |
| to_zone | no | — | |
| aggregation | string | no | — |
| psr_types | no | — | |
| tz | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| aggregation | string | no | — |
| tz | no | — |
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
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| date | string | yes | — |
| x | integer | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| kind | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| aggregation | string | no | — |
| tz | no | — |
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 achiev
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| psr_types | no | — | |
| aggregation | string | no | — |
| tz | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| from_zone | string | yes | — |
| to_zone | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| aggregation | string | no | — |
| tz | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| kind | string | no | — |
| min_mw | no | — | |
| tz | no | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| endpoint | string | yes | — |
| zones | array | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| aggregation | string | no | — |
| tz | no | — |
Show ingest coverage and lag for (endpoint × zone) — call before queries if you're not sure whether the data is landed yet.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| zone | no | — | |
| endpoint | no | — |
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
No parameter schema on file.
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 li
| Parameter | Type | Required | Notes |
|---|---|---|---|
| slug | string | yes | — |
| start | string | yes | — |
| end | string | yes | — |
| zone | no | — | |
| from_zone | no | — | |
| to_zone | no | — | |
| psr_types | no | — | |
| aggregation | no | — | |
| tz | no | — |
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Entsoe or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
—Grade not published
No rule-by-rule report on file for this release
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0.
1.0.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Entsoe can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.