# Australian Heat Pump Hot Water Rebate & Payback (remote · heatpump.sourcemill.ai)

Heat pump vs gas hot water (AU): rebate stack, net outlay and payback verdict by postcode.

- Trust score: 56/100 (low)
- Change this week: +2
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `heatpump.sourcemill.ai`: 56/100 (this document), [markdown](https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump.md), [page](https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump)

## Channel facts

- Endpoint: `https://heatpump.sourcemill.ai/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

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

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS not yet verified: we couldn't determine whether a plaintext access path exists.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 63/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 400 tokens (~400/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 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.
- **Capabilities**: 20/100
  - Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http ai-sourcemill-au-hot-water-payback https://heatpump.sourcemill.ai/mcp
```

### Codex

```toml
[mcp_servers.ai-sourcemill-au-hot-water-payback]
url = "https://heatpump.sourcemill.ai/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ai-sourcemill-au-hot-water-payback": {
      "type": "remote",
      "url": "https://heatpump.sourcemill.ai/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ai-sourcemill-au-hot-water-payback --url https://heatpump.sourcemill.ai/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  ai-sourcemill-au-hot-water-payback:
    url: "https://heatpump.sourcemill.ai/mcp"
```

### Other

```json
{
  "mcpServers": {
    "ai-sourcemill-au-hot-water-payback": {
      "type": "http",
      "url": "https://heatpump.sourcemill.ai/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-08-03 (score 56, +1)

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

### 2026-07-31 (score 55, −1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 56, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 56, +1)

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

### 2026-07-28 (score 55, +1)

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

### 2026-07-27 (score 54, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 54)

First indexed and scored.

## MCP tools (1)

### `check_hot_water_switch` (~400 tokens)

Use when someone asks whether a heat pump hot water system is worth it in Australia, which rebates they can stack, how much a heat pump costs after rebates, or how long it takes to pay off — including "can I combine the STC rebate with Victorian Energy Upgrades or Solar Victoria", "do I qualify", and "is a heat pump cheaper to run than gas". Given a postcode, the current hot water system and a few household facts, returns the rebates actually stackable at that postcode (with each scheme's eligibility gates and source), the net-of-rebate outlay, the payback period, and which term — rebates, the avoidable gas supply charge, the energy saving, or a replacement you were buying anyway — is really carrying the decision. Modelled estimate, not financial advice.

Input parameters:

- `building_age_years` (number): age of the building; Victorian Energy Upgrades requires at least 2 years
- `current_system` (string, required): what you have now
- `gas_only_for_hot_water` (boolean): true if hot water is your last gas appliance, so the daily supply charge can be avoided
- `household_income` (number): combined owner taxable income, for means-tested schemes (Solar Victoria caps at $150,000)
- `locally_made` (boolean): an eligible locally made unit, which raises the Victorian caps
- `owner_occupier` (boolean): tenure — gates the means-tested state rebates
- `people` (number): household size (drives hot water demand)
- `postcode` (string, required): AU postcode — rebate eligibility is postcode-gated
- `property_value` (number): property value — Solar Victoria requires under $3,000,000
- `replacement_due` (boolean): true if the existing system is failing and you were replacing it anyway
- `system_age_years` (number): age of the system being replaced; Solar Victoria requires at least 3 years

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump#diagnostics

## Score history

- 2026-08-03: 56
- 2026-08-02: 55
- 2026-08-01: 55
- 2026-07-31: 55
- 2026-07-30: 56
- 2026-07-29: 56
- 2026-07-28: 55
- 2026-07-27: 54
- 2026-07-26: 54

## Links

- Remote endpoint: https://heatpump.sourcemill.ai/mcp
- Website: https://heatpump.sourcemill.ai/
- Changelog RSS feed: https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ai-sourcemill-au-hot-water-payback/heatpump