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.

Battery Payback

REMOTE · BATTERYPAYBACK.CO.UK

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

69 Trust /100

Last scanned (11 hours ago)

Scores higher than 53% of remote servers

Reachable. Last reached 21 Nov 2026.

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security80
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability61
  • AI-judged instruction clarity (fair).Partial
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

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.

What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

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.

  • 21 Nov 26 69

    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 21 Nov 2026 · Probed https://batterypayback.co.uk/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=batterypayback.co.uk CN=YE1,O=Let's Encrypt,C=US 19 Oct 2026 17 Jan 2027 ECDSA 256 ECDSA-SHA384 6554d0914ce1b7dd8400d852f1ed2098374
SANs: batterypayback.co.uk
CN=YE1,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 5ddd70dd31f801c85c186a7a04b80afe
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of batterypayback.co.uk. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
uk. DS published 43876 8 Verified
co.uk. DS published 11810 8 Verified
batterypayback.co.uk. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains
content-security-policy frame-ancestors 'self'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests
x-content-type-options nosniff
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://batterypayback.co.uk/mcp Verified 200
http (plaintext) http://batterypayback.co.uk/mcp HTTPS enforced 308 https://batterypayback.co.uk/mcp
MCP tools · 7 exposed · ~658 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
calculate_payback ~444

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.

NameTypeReqDescription
annual_use_kwhnumberyes–
battery_price_gbpnumberyesInstalled price.
battery_usable_kwhnumberyes–
charge_from_gridboolean–Fill the battery at the cheap rate. Default true.
charge_power_kwnumber–Optional battery charging power, kW. With cheap_window_hours it caps grid charging at power x hours a night.
cheap_hours_sharenumber–Share of use already in cheap-rate hours, 0-1. Default 0.
cheap_rate_pnumber–Cheap-hours rate, p/kWh. Omit for a single-rate tariff.
cheap_window_hoursnumber–Optional length of the cheap-rate window, hours.
daytime_sharenumber–Share of use between 8am and 4pm, 0-1. Default: the measured London profile (about 0.34, Low Carbon London smart meters).
export_rate_pnumber–Export (SEG) rate, p/kWh. Default 0.
loan_ratenumber–Optional yearly loan interest rate, 0-0.5 (charged monthly).
loan_yearsnumber–Optional loan term in years (with loan_rate).
peak_rate_pnumberyesNormal or peak unit rate, p/kWh.
round_trip_efficiencynumber–0-1, from the datasheet. Default 0.9 (assumption).
shiftable_evening_sharenumber–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_yearnumber–Yearly solar generation. 0 = no panels.
yearly_saving_declinenumber–Optional yearly reduction of the saving, 0-0.2.

No output schema declared.

No examples provided.

get_battery ~46

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

NameTypeReqDescription
idstringyese.g. givenergy-all-in-one (see list_batteries).

No output schema declared.

No examples provided.

get_export_rates ~28

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_methodology ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

get_rules ~51

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

NameTypeReqDescription
topicstring––

No output schema declared.

No examples provided.

get_tariff_facts ~37

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

NameTypeReqDescription
topicstring––

No output schema declared.

No examples provided.

list_batteries ~26

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

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.

remote · batterypayback.co.uk

# add to Claude Code
claude mcp add --transport http uk-co-batterypayback-battery-payback 'https://batterypayback.co.uk/mcp'
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.