# Ofgem (npm · @pipeworx/mcp-ofgem)

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

- Trust score: 83/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 70/100, [markdown](https://verifymcp.io/servers/pipeworx-io-ofgem/ofgem-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ofgem/ofgem-mcp)
- npm · `@pipeworx/mcp-ofgem`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem.md), [page](https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ofgem`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

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

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ofgem).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 66/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 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.

### Claude

```bash
claude mcp add pipeworx-io-ofgem -- npx -y @pipeworx/mcp-ofgem
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-ofgem": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ofgem"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-ofgem": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ofgem"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-ofgem -- npx -y @pipeworx/mcp-ofgem
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-ofgem": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-ofgem"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-ofgem --command npx --arg -y --arg @pipeworx/mcp-ofgem
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-ofgem:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-ofgem"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-ofgem": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-ofgem"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-ofgem -t stdio -c npx -a -y @pipeworx/mcp-ofgem
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-ofgem": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-ofgem"
      ]
    }
  }
}
```

## 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-11-05 (score 83, +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.

### 2026-11-04 (score 82, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 67, −12)

- [security regression] Malware scan: pass → unverified
- [functional improvement] Stability: unverified → 0.17
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 79, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `ofgem_datasets` (~171 tokens)

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" })

Input parameters:

- `page` (number): 0-based page of the catalogue (24 datasets per page, default 0)
- `query` (string): Free-text search over dataset titles and descriptions, e.g. "price cap", "switching", "wholesale gas"

### `ofgem_price_cap` (~207 tokens)

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 })

Input parameters:

- `payment_method` (string): Which cap to return: "direct_debit" (default), "prepayment" or "standard_credit"
- `periods` (number): How many most-recent cap periods to return (default 8, max 60; 0 returns every period)

### `ofgem_dataset_rows` (~186 tokens)

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 })

Input parameters:

- `dataset_id` (string, required): Dataset id from ofgem_datasets, e.g. "qRvAxIgho"
- `latest_first` (boolean): Return the last rows of the table first — these series run oldest-first (default false)
- `limit` (number): Maximum rows to return (default 50, max 1000; 0 returns every row)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 67
- 2026-11-02: 79
- 2026-11-01: 79
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

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

### What did VerifyMCP test on the Ofgem MCP server?

VerifyMCP ran 16 checks on Ofgem, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-ofgem
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ofgem
- Repository: https://github.com/pipeworx-io/mcp-ofgem
- Website: https://pipeworx.io/packs/ofgem
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ofgem/pipeworx-mcp-ofgem