Elexon
NPM · @PIPEWORX/MCP-ELEXON · 2 COMPONENTS
Elexon BMRS Insights MCP — Great Britain electricity grid & market data.
Available components
Last scanned (9 hours ago)
Scores higher than 72% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-elexon). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 997 tokens (~199/item across 5 items; 5 tools + 0 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 Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.1 → 0.2.2 functional
- 31 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 30 Oct 26 64
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-elexon@0.2.2
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-elexon |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-elexon/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3617605035 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:17f9c1da45aef28dfc3e07d9bc81fec5a5c388441aadec843d91086f7934fd2eac2b03bff5992b7ceadb5868ff1ecc3cc00af058316f27afdd784620f |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
elexon_list_datasets ~168
Directory of all 84 Elexon BMRS Insights datasets available to query_dataset: the dataset code, what it holds, and which window parameters its route takes (publish time, from/to, settlement date + period, measurement time, or submission time). Covers generation outturn and forecasts, demand and load, balancing mechanism bids/offers and acceptances, market index prices, system frequency, temperature, credit default and system warning notices, and the REMIT outage messages. Search by keyword to find the code for a subject before calling query_dataset. Keyless.
| Name | Type | Req | Description |
|---|---|---|---|
| search | string | – | Optional case-insensitive keyword matched against the dataset code and its title, e.g. "wind", "demand", "price", "forecast". Omit to list all 84. |
No output schema declared.
No examples provided.
elexon_system_prices ~139
Great Britain electricity imbalance prices for a settlement day: system buy price and system sell price per settlement period, in GBP/MWh, plus the price derivation code, reserve scarcity price and net imbalance volume (Elexon DISEBSP). This is the cash-out price the balancing market settles at. Keyless. Elexon serves it outside the /datasets routes, so query_dataset cannot reach it.
| Name | Type | Req | Description |
|---|---|---|---|
| settlement_date | string | yes | Settlement date, e.g. "2026-08-27". |
| settlement_period | number | – | Optional settlement period 1-48. Omit for the whole day (48 rows). |
No output schema declared.
No examples provided.
generation_by_fuel ~159
Great Britain half-hourly electricity generation by fuel type (Elexon BMRS FUELHH dataset). Returns MW generated per fuel (CCGT/gas, COAL, NUCLEAR, WIND, BIOMASS, NPSHYD hydro, PS pumped-storage, OCGT, OIL, and interconnector flows INTFR/INTIRL/etc) for each half-hour settlement period. Keyless. 48 settlement periods per day.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Publish-time start, ISO datetime, e.g. "2024-06-01T00:00Z". |
| to | string | yes | Publish-time end, ISO datetime, e.g. "2024-06-01T01:00Z". |
No output schema declared.
No examples provided.
query_dataset ~366
Fetch records from any of the 84 Elexon BMRS Insights datasets by its dataset code (MID market index/day-ahead prices, FUELHH generation by fuel, WINDFOR wind forecast, FREQ system frequency, TEMP temperature, REMIT outages, BOD/BOALF balancing bids and acceptances, and 77 more — call elexon_list_datasets for the directory). Pass a code and a datetime window; the correct window parameters for that dataset are chosen automatically. Keyless. Returns the raw records.
| Name | Type | Req | Description |
|---|---|---|---|
| dataset | string | yes | Dataset code, case-insensitive, e.g. "MID", "FUELHH", "WINDFOR", "FREQ", "REMIT". Use elexon_list_datasets to find one; an unrecognised code is rejected with the full list rather than passed upstream. |
| date_param | string | – | Rarely needed — the window style is looked up per dataset. Pass "publishDateTime", "from", "settlement" (settlementDateFrom/To, which only FUELHH and FUELINST accept), "settlementDate", "measurement"… |
| from | string | yes | Window start, ISO datetime. For settlement-date datasets (B1610, MDB, MDO, PN, QPN, TUDM) this is the settlement date and settlement_period is also required. |
| settlement_period | number | – | Settlement period 1-48. Required only for the settlement-date datasets B1610, MDB, MDO, PN, QPN and TUDM, which Elexon serves one period at a time. |
| to | string | yes | Window end, ISO datetime. Ignored for settlement-date datasets. |
No output schema declared.
No examples provided.
system_demand ~111
Great Britain half-hourly electricity system demand outturn in MW (Elexon BMRS ITSDO dataset) over a required ISO-datetime window; returns one row per settlement period with settlementDate, settlementPeriod, and demand fields.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | yes | Start, ISO datetime, e.g. "2024-06-01T00:00Z". |
| to | string | yes | End, ISO datetime, e.g. "2024-06-01T01:00Z". |
No output schema declared.
No examples provided.
How do I install the Elexon MCP server?
Elexon runs locally as an npm package, launched with npx -y @pipeworx/mcp-elexon. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-elexon
claude mcp add pipeworx-io-elexon -- npx -y @pipeworx/mcp-elexon
What is the Elexon MCP server?
Elexon is an MCP server listed in the public MCP registry as io.github.pipeworx-io/elexon. Elexon BMRS Insights MCP, Great Britain electricity grid & market data. This page covers its npm package (@pipeworx/mcp-elexon).
Is the Elexon MCP server safe to use?
Elexon scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Elexon MCP server expose?
Elexon exposes 5 tools: generation_by_fuel, system_demand, elexon_list_datasets, elexon_system_prices, query_dataset. Their descriptions and schemas cost roughly 943 tokens of context every time the server is loaded.
Is the Elexon MCP server still maintained?
Elexon is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Elexon MCP server under?
Elexon declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.