# Battery Payback (remote · batterypayback.co.uk)

UK home battery payback estimates, tariffs and sourced battery specifications.

- Trust score: 69/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `batterypayback.co.uk`: 69/100 (this document), [markdown](https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback.md), [page](https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback)

## Channel facts

- Endpoint: `https://batterypayback.co.uk/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-21.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Context-footprint check failed: tool/resource definitions use about 802 tokens (~114/item across 7 items; 7 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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 7 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the Battery Payback MCP server?

Battery Payback is a hosted endpoint at https://batterypayback.co.uk/mcp, so there is nothing to install locally. 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 --transport http uk-co-batterypayback-battery-payback 'https://batterypayback.co.uk/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "uk-co-batterypayback-battery-payback": {
      "url": "https://batterypayback.co.uk/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "uk-co-batterypayback-battery-payback": {
      "type": "http",
      "url": "https://batterypayback.co.uk/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.uk-co-batterypayback-battery-payback]
url = "https://batterypayback.co.uk/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "uk-co-batterypayback-battery-payback": {
      "type": "remote",
      "url": "https://batterypayback.co.uk/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add uk-co-batterypayback-battery-payback --url 'https://batterypayback.co.uk/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  uk-co-batterypayback-battery-payback:
    url: "https://batterypayback.co.uk/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "uk-co-batterypayback-battery-payback": {
      "Transport": "http",
      "Url": "https://batterypayback.co.uk/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add uk-co-batterypayback-battery-payback -t streamable-http -u 'https://batterypayback.co.uk/mcp'
```

### Other

```json
{
  "mcpServers": {
    "uk-co-batterypayback-battery-payback": {
      "type": "http",
      "url": "https://batterypayback.co.uk/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-21 (score 69)

First indexed and scored.

## MCP tools (7)

### `calculate_payback` (~444 tokens)

Home battery payback estimate

Yearly saving and simple payback time of a home battery in the UK, from the user's own figures. Same model as the calculator on batterypayback.co.uk. Rates in pence per kWh.

Input parameters:

- `annual_use_kwh` (number, required)
- `battery_price_gbp` (number, required): Installed price.
- `battery_usable_kwh` (number, required)
- `charge_from_grid` (boolean): Fill the battery at the cheap rate. Default true.
- `charge_power_kw` (number): Optional battery charging power, kW. With cheap_window_hours it caps grid charging at power x hours a night.
- `cheap_hours_share` (number): Share of use already in cheap-rate hours, 0-1. Default 0.
- `cheap_rate_p` (number): Cheap-hours rate, p/kWh. Omit for a single-rate tariff.
- `cheap_window_hours` (number): Optional length of the cheap-rate window, hours.
- `daytime_share` (number): Share of use between 8am and 4pm, 0-1. Default: the measured London profile (about 0.34, Low Carbon London smart meters).
- `export_rate_p` (number): Export (SEG) rate, p/kWh. Default 0.
- `loan_rate` (number): Optional yearly loan interest rate, 0-0.5 (charged monthly).
- `loan_years` (number): Optional loan term in years (with loan_rate).
- `peak_rate_p` (number, required): Normal or peak unit rate, p/kWh.
- `round_trip_efficiency` (number): 0-1, from the datasheet. Default 0.9 (assumption).
- `shiftable_evening_share` (number): Optional share (0-1) of evening use the household moves to cheap hours itself, without a battery. The saving is then only what the battery adds on top.
- `solar_kwh_per_year` (number): Yearly solar generation. 0 = no panels.
- `yearly_saving_decline` (number): Optional yearly reduction of the saving, 0-0.2.

### `get_export_rates` (~28 tokens)

Smart Export Guarantee rates

Export rates by UK supplier with quote, source and read date, plus suppliers still being verified.

### `get_rules` (~51 tokens)

UK rules for home batteries

Quoted official facts on VAT, SEG, MCS, planning, network (DNO) notification, typical costs, solar yield, self-consumption and the Boiler Upgrade Scheme.

Input parameters:

- `topic` (string)

### `get_tariff_facts` (~37 tokens)

Price cap and smart tariffs

Ofgem price cap, smart time-of-use tariffs and export tariffs, quoted with read dates.

Input parameters:

- `topic` (string)

### `list_batteries` (~26 tokens)

List home batteries

Batteries we track, with which specifications are checked and which are not yet verified.

### `get_battery` (~46 tokens)

Get one battery

Specifications from the manufacturer's datasheet and warranty, each with quote and read date.

Input parameters:

- `id` (string, required): e.g. givenergy-all-in-one (see list_batteries).

### `get_methodology` (~26 tokens)

How Battery Payback calculates

The calculator model, its simplifications, sourced defaults and how to cite the site.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback#diagnostics

## Score history

- 2026-11-21: 69

## Common questions

### What is the Battery Payback MCP server?

Battery Payback is an MCP server listed in the public MCP registry as uk.co.batterypayback/battery-payback. UK home battery payback estimates, tariffs and sourced battery specifications. This page covers its hosted endpoint (https://batterypayback.co.uk/mcp).

### Is the Battery Payback MCP server safe to use?

Battery Payback scores 69 out of 100 on VerifyMCP. 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 Battery Payback MCP server expose?

Battery Payback exposes 7 tools: calculate_payback, get_export_rates, get_rules, get_tariff_facts, list_batteries, and 2 more. Their descriptions and schemas cost roughly 658 tokens of context every time the server is loaded.

### Does the Battery Payback MCP server require authentication?

No. We connected to Battery Payback without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Battery Payback MCP server still maintained?

Battery Payback is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Battery Payback MCP server?

VerifyMCP ran 12 checks on Battery Payback, covering TLS certificate, Authorization, HTTPS, HSTS header and 8 more. One item could not be completed, a gap on our side rather than a finding about Battery Payback: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://batterypayback.co.uk/mcp
- Website: https://batterypayback.co.uk/agents/
- Changelog RSS feed: https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback.xml
- Changelog JSON feed: https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback.json
- HTML version of this page: https://verifymcp.io/servers/uk-co-batterypayback-battery-payback/batterypayback
