# Octopus Energy (npm · @pipeworx/mcp-octopus-energy)

Octopus Energy public API MCP — UK energy tariffs & products.

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

## Components

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-octopus-energy`
- 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-octopus-energy).
  - 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**: 69/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 728 tokens (~182/item across 4 items; 4 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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 Octopus Energy MCP server?

Octopus Energy runs locally as an npm package, launched with npx -y @pipeworx/mcp-octopus-energy. 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-octopus-energy -- npx -y @pipeworx/mcp-octopus-energy
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-04 (score 83, +16)

- [security improvement] Malware scan: unverified → pass

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

- [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 80, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (4)

### `list_products` (~171 tokens)

List Octopus Energy UK energy products (electricity & gas tariff families, e.g. "Agile Octopus", "Flexible Octopus"). Returns {count, results:[{code, display_name, direction, is_variable, is_green, is_tracker, is_prepay, is_business, term, available_from, available_to}]}. The "code" feeds product_details. Optional filters narrow the list.

Input parameters:

- `available_at` (string): ISO-8601 timestamp; only products available at that moment, e.g. "2026-06-01T00:00Z".
- `is_green` (boolean): Only 100% renewable products.
- `is_tracker` (boolean): Only wholesale-tracker products.
- `is_variable` (boolean): Only variable-rate products (prices change over time).

### `product_details` (~156 tokens)

Full detail for one product code, including its tariffs broken out by GSP region "_A".."_P" and payment method (e.g. direct_debit_monthly). Each tariff entry has a "code" (e.g. "E-1R-AGILE-24-10-01-C"), standing charges and unit rates (inc/exc VAT). Use the tariff "code" with tariff_unit_rates. Tariff sets returned: single_register_electricity_tariffs, dual_register_electricity_tariffs, four_rate_ev_electricity_tariffs, single_register_gas_tariffs.

Input parameters:

- `productCode` (string, required): Product code from list_products, e.g. "AGILE-24-10-01".

### `tariff_unit_rates` (~262 tokens)

Time-series of electricity unit rates for a specific tariff — for Agile this is the half-hourly wholesale-tracked pricing. Returns {count, results:[{value_exc_vat, value_inc_vat, valid_from, valid_to, payment_method}]} in p/kWh, newest first. Set kind="standing_charges" for the p/day standing charge instead. Defaults to the most recent rates; pass period_from/period_to to bound a window.

Input parameters:

- `kind` (string): Which series to fetch. Default "standard_unit_rates".
- `page_size` (number): Results per page (default 100, max 1500).
- `period_from` (string): ISO-8601 start, e.g. "2026-06-01T00:00Z".
- `period_to` (string): ISO-8601 end, e.g. "2026-06-02T00:00Z".
- `productCode` (string, required): Product code, e.g. "AGILE-24-10-01".
- `tariffCode` (string, required): Tariff code from product_details, e.g. "E-1R-AGILE-24-10-01-C" (the trailing letter is the GSP region).

### `grid_supply_point` (~84 tokens)

Map a UK postcode to its GSP (Grid Supply Point) group "_A".."_P". The group_id is the region suffix used in tariff codes and in product_details regional breakdowns. Returns {count, results:[{group_id}]}.

Input parameters:

- `postcode` (string, required): UK postcode, e.g. "SW1A 1AA" (spaces optional).

## Diagnostics

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

## Score history

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

## Common questions

### What is the Octopus Energy MCP server?

Octopus Energy is an MCP server listed in the public MCP registry as io.github.pipeworx-io/octopus-energy. Octopus Energy public API MCP, UK energy tariffs & products. This page covers its npm package (@pipeworx/mcp-octopus-energy).

### Is the Octopus Energy MCP server safe to use?

Octopus Energy 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 Octopus Energy MCP server expose?

Octopus Energy exposes 4 tools: list_products, product_details, tariff_unit_rates, grid_supply_point. Their descriptions and schemas cost roughly 673 tokens of context every time the server is loaded.

### Is the Octopus Energy MCP server still maintained?

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

Octopus Energy 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 Octopus Energy MCP server?

VerifyMCP ran 16 checks on Octopus Energy, 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-octopus-energy
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-octopus-energy
- Repository: https://github.com/pipeworx-io/mcp-octopus-energy
- Website: https://pipeworx.io/packs/octopus-energy
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-octopus-energy/pipeworx-mcp-octopus-energy.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-octopus-energy/pipeworx-mcp-octopus-energy/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-octopus-energy/pipeworx-mcp-octopus-energy.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-octopus-energy/pipeworx-mcp-octopus-energy