# Aivy Energy (pypi · aivy-mcp)

Read and control your own home solar + battery: Sungrow, Sigenergy, FoxESS, AlphaESS, SolaX.

- Trust score: 67/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- pypi · `aivy-mcp`: 67/100 (this document), [markdown](https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp.md), [page](https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp)

## Channel facts

- Registry: `pypi`
- Package: `aivy-mcp`
- Version: `0.9.2`
- 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-21.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised build step with no custom scripting around it.
  - 1 of 31 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 43/100
  - 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 3026 tokens (~77/item across 39 items; 27 tools + 12 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 40/100
  - Stability observed for 12 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 71/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 0% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 2 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "delete_alert" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 29 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).
  - Supports UI / widget rendering.

## Install

### How do I install the Aivy Energy MCP server?

Aivy Energy runs locally as a PyPI package, launched with uvx aivy-mcp. 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 ivyenergy-aivy-mcp -- uvx aivy-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "ivyenergy-aivy-mcp": {
      "command": "uvx",
      "args": [
        "aivy-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "ivyenergy-aivy-mcp": {
      "command": "uvx",
      "args": [
        "aivy-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add ivyenergy-aivy-mcp -- uvx aivy-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ivyenergy-aivy-mcp": {
      "type": "local",
      "command": [
        "uvx",
        "aivy-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ivyenergy-aivy-mcp --command uvx --arg aivy-mcp
```

### Hermes

```yaml
mcp_servers:
  ivyenergy-aivy-mcp:
    command: "uvx"
    args: ["aivy-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "ivyenergy-aivy-mcp": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "aivy-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add ivyenergy-aivy-mcp -t stdio -c uvx -a aivy-mcp
```

### Other

```json
{
  "mcpServers": {
    "ivyenergy-aivy-mcp": {
      "command": "uvx",
      "args": [
        "aivy-mcp"
      ]
    }
  }
}
```

## 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 67, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-20 (score 51, −15)

- [security regression] Malware scan: pass → unverified

### 2026-11-19 (score 66, +1)

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

### 2026-11-17 (score 65, +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-11-15 (score 64, +1)

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

### 2026-11-13 (score 63, +2)

- [functional improvement] Stability: unverified → 0.13

### 2026-11-12 (score 61, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-11 (score 46, −15)

- [security regression] Malware scan: pass → unverified

## MCP tools (27)

### `get_registration_terms` (~120 tokens)

Whether sign-up is open and the terms of use / privacy policy a new account accepts (version, hash and
a link). Show the link to the person and ask whether they accept BEFORE register_account. Hosts that
support cards render a sign-up / sign-in form here instead: the person types email and password into the
card, which calls register_account / verify_registration / sign_in itself, so nothing passes through the
chat. When the card is shown, wait for the person to say they are done.

Input parameters:

- `locale` (string)

### `list_sites` (~50 tokens)

List the user's solar + battery sites across vendors. Returns id (vendor:station_id, used by every other
tool), vendor, name, online and the vendor's headline power in W. Start here.

### `get_status` (~81 tokens)

Live reading: SOC (%), pv_w, load_w, grid_w (>0 exporting), battery_w (>0 charging). A null channel is one
the vendor does not report, not zero. `source` is vendor (fresh) or stored (last kept reading).
Hosts that support cards render this as a status card.

Input parameters:

- `site_id` (string, required)

### `get_curve` (~96 tokens)

Power and SOC history. range 1d = 5-minute points for one local day (day = YYYY-MM-DD, default today);
7d / 30d = daily values. Returns times (UTC), local_times, and series per channel (pv, load, battery, grid,
soc). Large: summarise before quoting.

Input parameters:

- `day`
- `range` (string)
- `site_id` (string, required)

### `get_earnings` (~109 tokens)

Energy bought, sold and self-consumed for a day (YYYY-MM-DD, 'today' or 'yesterday'), priced at the actual
Amber half-hourly prices when Amber is linked. Optional HH:MM window for part of the day. An estimate from
vendor power samples, not the bill; read `coverage` and say so when it is partial.

Input parameters:

- `date`
- `site_id` (string, required)
- `window_end`
- `window_start`

### `get_operations` (~69 tokens)

What the platform did to the site and why, newest first: each automatic (Ai+) and manual command with its
reason and the prices at the time. Use it to explain 'why did it charge at 3am'.

Input parameters:

- `limit` (integer)
- `site_id` (string, required)

### `get_prices` (~110 tokens)

Amber Electric prices for the site: the current interval and the forecast as import price and feed-in earn
(c/kWh incl. GST), with a summary of cheapest/dearest periods. resolution 30 (up to 24 h) or 5 (up to 4 h).
Fails with 409 when no Amber account is linked to the site. Hosts that support cards render a price chart.

Input parameters:

- `hours` (integer)
- `resolution` (integer)
- `site_id` (string, required)

### `list_vendors` (~68 tokens)

Every inverter / battery brand Aivy can connect, whether it is available on this deployment, what
connecting one needs (`connect`: serial + NMI, a system id, or an OAuth sign-in at the vendor) and how much
of it can be controlled. Use before connect_site.

### `list_alerts` (~61 tokens)

The account's alert rules on a site: what each watches (soc %, import/export price c/kWh, forecast
temperature °C), above/below which threshold, whether it emails, and when it last fired.

Input parameters:

- `site_id` (string, required)

### `get_energy_mode` (~67 tokens)

Current energy mode (selfConsumption | amber_smart = Ai+ | forced), its forced windows, the SOC floor, the
Ai+ variant and settings when on Ai+, and any pending timed hand-back (reverts_at / reverts_to).

Input parameters:

- `site_id` (string, required)

### `get_ai_plus` (~62 tokens)

Ai+ (amber_smart) configuration: active or not, engine variant and options, effective settings, and
\`tunable`: every lever with type, min, max, unit and default. Read before update_ai_plus.

Input parameters:

- `site_id` (string, required)

### `plan_best_price_discharge` (~153 tokens)

Propose when to sell: picks the best-paid Amber intervals in the window (HH:MM) for the battery's usable
energy above reserve_soc, optionally only above min_sell_c c/kWh. Returns intervals, expected revenue, the
average it beats and proposed time_slots. Nothing is applied; apply with set_energy_mode(mode='forced',
time_slots=...) after the user agrees. Hosts that support cards show the plan with an Apply button; a click
on it is the user's yes.

Input parameters:

- `battery_capacity_kwh`
- `min_sell_c`
- `reserve_soc`
- `site_id` (string, required)
- `window_end`
- `window_start`

### `plan_discharge_to_target` (~90 tokens)

Propose a steady discharge that lands on target_soc at end (HH:MM, site local), from the real capacity, SOC
and power limits. Returns power_w and proposed time_slots. Nothing is applied.

Input parameters:

- `battery_capacity_kwh`
- `end` (string, required)
- `site_id` (string, required)
- `start`
- `target_soc` (integer, required)

### `register_account` (~134 tokens)

Create an Aivy account from the chat, step 1 of 2: a verification code is emailed to `email`. Needs no API
key. Ask the person to choose the password (8+ characters; it is also their Aivy app password); do not invent
one. Then ask them for the code and call verify_registration. The reply looks the same whether or not the
address already has an account: a code that never arrives means check spam or use sign_in instead.

Input parameters:

- `display_name`
- `email` (string, required)
- `locale` (string)
- `password` (string, required)

Output parameters:

- `result` (string)

### `verify_registration` (~173 tokens)

Create an Aivy account from the chat, step 2 of 2: confirms the emailed code, accepts the terms (only pass
accept_terms=true after the person said yes), creates the account and an API key, and stores that key on this
computer (~/.aivy/credentials.json) so every other tool works from now on, in this and future sessions.
scope read (observe) or control (may change settings; only if the person asked). Never repeat the key back;
say it is saved and can be managed at https://bridge.ivyenergy.com.au/account.

Input parameters:

- `accept_terms` (boolean, required)
- `code` (string, required)
- `key_name` (string)
- `registration_id` (string, required)
- `registration_session` (string, required)
- `scope` (string)

Output parameters:

- `result` (string)

### `sign_in` (~117 tokens)

Use an existing Aivy account from the chat: creates an API key with the account's username (or email)
and password, stores it on this computer (~/.aivy/credentials.json) and uses it from now on. Needs no
existing key. scope read or control (control only if the person asked). The password is used once and not
stored; never repeat the key back.

Input parameters:

- `key_name` (string)
- `password` (string, required)
- `scope` (string)
- `username` (string, required)

Output parameters:

- `result` (string)

### `get_agent_guide` (~98 tokens)

The Aivy agent playbook: which tools answer which questions, the rules for writes (confirm first, forced
mode is time-boxed, never guess numbers, do not poll), the step-by-step workflows (status, diagnosis, prices,
earnings, selling tonight, keeping a reserve, charging now, connecting a system, Ai+ tuning) and what each
error code means. Read it once at the start of a conversation.

Output parameters:

- `result` (string)

### `whoami` (~56 tokens)

Check the API key: who it belongs to and whether it may control (scope read or control). Without a key
it says so: then register_account (new) or sign_in (existing account) sets one up from the chat.

Output parameters:

- `result` (string)

### `get_site` (~82 tokens)

Facts about one site: timezone, battery capacity (kWh) and where that figure came from, max charge/discharge
power (W), export limit (W), the SOC floor Ai+ keeps, live SOC and usable kWh, current energy mode and
forced windows, today's energy and income when the vendor reports them.

Input parameters:

- `site_id` (string, required)

Output parameters:

- `result` (string)

### `connect_site` (~144 tokens)

CHANGES THE ACCOUNT (control scope). Confirm with the user before calling.

Link the user's system to their Aivy account. Serial-number vendors (Sungrow and FoxESS need sn + nmi,
Sigenergy needs system_id, most others sn) return `connected` site ids. OAuth vendors (AlphaESS, SolaX)
return an `authorize_url`: give it to the user to open in a browser and approve; the site then appears in
list_sites within a minute. Demo sites need no connecting.

Input parameters:

- `nmi`
- `region` (string)
- `sn`
- `system_id`
- `vendor` (string, required)

Output parameters:

- `result` (string)

### `disconnect_site` (~64 tokens)

CHANGES THE ACCOUNT (control scope). Confirm with the user before calling.

Remove a site from the user's account. The vendor-side link and history are left alone; the account just
stops seeing it. Demo sites cannot be removed.

Input parameters:

- `site_id` (string, required)

Output parameters:

- `result` (string)

### `create_alert` (~188 tokens)

Set up a threshold alert: metric soc | import_price | export_price | temperature, operator above | below.
Every firing goes to the app inbox (and the phone when the app is installed); email=True also mails the
account's verified address (whoami.email_alerts says whether that works). Quiet for cooldown_minutes after
each firing (min 15). An alert only tells the person something; it never changes what the battery does.
Confirm the rule with the user before creating it.

Input parameters:

- `active_end` (string)
- `active_start` (string)
- `cooldown_minutes` (integer)
- `email` (boolean)
- `locale` (string)
- `message` (string)
- `metric` (string, required)
- `name` (string, required)
- `operator` (string, required)
- `site_id` (string, required)
- `threshold` (number, required)

Output parameters:

- `result` (string)

### `delete_alert` (~44 tokens)

Retire an alert rule (past firings stay in the inbox). Confirm with the user first.

Input parameters:

- `rule_id` (integer, required)
- `site_id` (string, required)

Output parameters:

- `result` (string)

### `get_alert_events` (~65 tokens)

What fired on the site, newest first: the rule, the value that tripped it, when, how it was delivered and
whether it was emailed. Use for 'did anything happen overnight?'.

Input parameters:

- `limit` (integer)
- `site_id` (string, required)

Output parameters:

- `result` (string)

### `send_test_alert_email` (~40 tokens)

Send one test alert email to the account's verified address so the person sees what an alert looks like.
409 when the account has no verified email.

Output parameters:

- `result` (string)

### `set_energy_mode` (~243 tokens)

CHANGES THE SITE (control scope). Confirm with the user before calling.

mode: selfConsumption (inverter default), amber_smart (Ai+, price-driven trading) or forced (manual windows).
forced is always time-boxed: duration_minutes (default 240, max 1440); afterwards the server returns the site
to the mode it had before. Shorthand for forced: action=charge|discharge with power_w and target_soc (charge)
or stop_soc (discharge) builds one window starting now. Or pass explicit time_slots:
[{type, start 'HH:MM', end 'HH:MM', target_soc|stop_soc, power, pace}] in site local time.
variant picks the Ai+ engine when mode is amber_smart. The SOC floor and export limits cannot be overridden.
Takes effect on the engine's next tick (about a minute).

Input parameters:

- `action`
- `duration_minutes`
- `mode` (string, required)
- `power_w`
- `site_id` (string, required)
- `stop_soc`
- `target_soc`
- `time_slots`
- `variant`

Output parameters:

- `result` (string)

### `update_ai_plus` (~110 tokens)

CHANGES THE SITE (control scope). Confirm with the user before calling.

Set Ai+ levers (names and ranges from get_ai_plus `tunable`) and/or switch engine variant. Validated against
the variant that will run; if any value is rejected nothing changes and `rejected` says why. Does not switch
the mode: use set_energy_mode(mode='amber_smart') for that.

Input parameters:

- `settings`
- `site_id` (string, required)
- `variant`

Output parameters:

- `result` (string)

## Diagnostics

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

## Score history

- 2026-11-21: 67
- 2026-11-20: 51
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 63
- 2026-11-13: 63
- 2026-11-12: 61
- 2026-11-11: 46
- 2026-11-10: 61
- 2026-11-09: 46

## Common questions

### What is the Aivy Energy MCP server?

Aivy Energy is an MCP server listed in the public MCP registry as io.github.IVYEnergy/aivy-mcp. Read and control your own home solar + battery: Sungrow, Sigenergy, FoxESS, AlphaESS, SolaX. This page covers its PyPI package (aivy-mcp).

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

Aivy Energy scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. 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 Aivy Energy MCP server expose?

Aivy Energy exposes 27 tools: get_registration_terms, list_sites, get_status, get_curve, get_earnings, and 22 more. Their descriptions and schemas cost roughly 2,694 tokens of context every time the server is loaded.

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

Aivy Energy 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 licence is the Aivy Energy MCP server under?

Aivy Energy declares the Apache-2.0 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 Aivy Energy MCP server?

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

## Links

- PyPI project: https://pypi.org/project/aivy-mcp/
- Socket report: https://socket.dev/pypi/package/aivy-mcp
- Repository: https://github.com/IVYEnergy/aivy-mcp
- Website: https://bridge.ivyenergy.com.au/developers
- Changelog RSS feed: https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp.json
- HTML version of this page: https://verifymcp.io/servers/ivyenergy-aivy-mcp/aivy-mcp
