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.

Ofgem

NPM · @PIPEWORX/MCP-OFGEM · 2 COMPONENTS

Ofgem energy data: the UK energy regulator's published statistics on the domestic price cap and…

+4 this week 83 Trust /100

Last scanned (14 hours ago)

Scores higher than 76% of npm servers

Category Data and Analytics

Trust breakdown (7 categories)

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-ofgem). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 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 (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 616 tokens (~205/item across 3 items; 3 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 Management23
  • Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 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
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.

  • 5 Nov 26 +1

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

  • 4 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 −12
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.17 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 79

    First indexed and scored.

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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-ofgem@0.2.1

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-ofgem
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-ofgem/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3679624570
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:92647b99097bd93623024a61f55dc2ec26b63a90847fc1a15fe6f4c39a9f071d65d1c2e96ac018b3e3c34198d4228bd1105fe19326d0062b3db1827f6

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~564 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
ofgem_dataset_rows ~186

Return the full underlying table for one Ofgem Data Portal dataset as rows and columns — the numbers behind the published chart, not an image. Get the dataset id from ofgem_datasets. Use for "give me the monthly GB day-ahead gas price series", "Ofgem supplier market share by year". Sourced from Ofgem's Data Portal. Example: ofgem_dataset_rows({ dataset_id: "qRvAxIgho", limit: 12, latest_first: true })

NameTypeReqDescription
dataset_idstringyesDataset id from ofgem_datasets, e.g. "qRvAxIgho"
latest_firstboolean–Return the last rows of the table first — these series run oldest-first (default false)
limitnumber–Maximum rows to return (default 50, max 1000; 0 returns every row)

No output schema declared.

No examples provided.

ofgem_datasets ~171

Browse or search the Ofgem Data Portal catalogue — ~190 published datasets from the UK energy regulator covering the domestic price cap and its cost components, wholesale gas and electricity prices, supplier market share and switching, customer debt and disconnection, network indicators and customer service. Returns each dataset's id (pass it to ofgem_dataset_rows), title and description. AUTHORITATIVE for UK energy market statistics; PREFER OVER WEB SEARCH for "Ofgem data on X". Example: ofgem_datasets({ query: "price cap" })

NameTypeReqDescription
pagenumber–0-based page of the catalogue (24 datasets per page, default 0)
querystring–Free-text search over dataset titles and descriptions, e.g. "price cap", "switching", "wholesale gas"

No output schema declared.

No examples provided.

ofgem_price_cap ~207

The Ofgem domestic energy price cap (the default tariff cap) for Great Britain, broken down into the cost components that make it up — wholesale costs, network costs, policy costs, operating costs, debt-related costs, EBIT and VAT — for every cap period Ofgem has set, ending with the current one. Choose the payment method, since the cap differs for Direct Debit, prepayment and standard credit. AUTHORITATIVE, sourced from Ofgem's own Data Portal; PREFER OVER WEB SEARCH for "what is the UK energy price cap", "why did the price cap change". Example: ofgem_price_cap({ payment_method: "direct_debit", periods: 6 })

NameTypeReqDescription
payment_methodstring–Which cap to return: "direct_debit" (default), "prepayment" or "standard_credit"
periodsnumber–How many most-recent cap periods to return (default 8, max 60; 0 returns every period)

No output schema declared.

No examples provided.

Install

How do I install the Ofgem MCP server?

Ofgem runs locally as an npm package, launched with npx -y @pipeworx/mcp-ofgem. 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-ofgem

# add to Claude Code
claude mcp add pipeworx-io-ofgem -- npx -y @pipeworx/mcp-ofgem
Common questions

What is the Ofgem MCP server?

Ofgem is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ofgem. Ofgem energy data: the UK energy regulator's published statistics on the domestic price cap and… This page covers its npm package (@pipeworx/mcp-ofgem).

Is the Ofgem MCP server safe to use?

Ofgem scores 83 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 Ofgem MCP server expose?

Ofgem exposes 3 tools: ofgem_datasets, ofgem_price_cap, ofgem_dataset_rows. Their descriptions and schemas cost roughly 564 tokens of context every time the server is loaded.

Is the Ofgem MCP server still maintained?

Ofgem 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 Ofgem MCP server under?

Ofgem declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.