Netatmo Energy
NPM · NETATMO-ENERGY-MCP
MCP server for Netatmo thermostats and radiator valves: status, history, analytics, opt-in control.
Available components
Last scanned (3 hours ago)
Scores higher than 74% of npm servers
Category IoT and Hardware
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. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 0 of 3 dependencies flagged as unhealthy. View diagnostics → Pass
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to christophe77/netatmo-energy-mcp). View diagnostics → Pass
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 6 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability80
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2402 tokens (~160/item across 15 items; 15 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 Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 16 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
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.
- 13 Oct 26 +32
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- Schema quality: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Tool coverage: 100 functional
- First check of Tool coverage: 100 functional
- 11 Oct 26 50
First indexed and scored.
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 17 Oct 2026 · Analysed npm/netatmo-energy-mcp@0.3.1
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | christophe77/netatmo-energy-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/christophe77/netatmo-energy-mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 3181094202 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:c8a965b87c634c0e630e3701ccbd262b8b94dfdbf977939f9b1a0884df5a361f11a79f29ad98923d81017dc2d6452c95c650db8650746bfc018025c93 |
Background: How many MCP packages publish verified provenance →
Dependencies 3 packages
| Packages resolved | 3 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
netatmo_compare_rooms Compare rooms ~175
Compare all rooms over a period (default: last 7 days): warmest/coolest, most variable, most time below target, largest drop and fastest cool-down after setpoint decreases. Returns per-room metrics and rankings.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| caveats | array | yes | – |
| home | object | yes | – |
| notes | array | yes | – |
| range | object | yes | – |
| rankings | array | yes | – |
| requests | number | yes | – |
| rooms | array | yes | – |
| scale | string | yes | – |
No examples provided.
netatmo_detect_anomalies Detect unusual heating behaviour ~258
Rule-based detection of unusual readings in 30-minute room data (default: last 24 h, at most 14 days): implausible values or jumps, constant readings, missing data, rapid drops at a constant setpoint, sustained deviation from the setpoint. Each finding has severity, confidence, evidence and an explanation; findings are observations, not diagnoses.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| max_anomalies | integer | – | Maximum findings returned, most severe first (default 30) |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| room_id | string | – | Room ID from netatmo_list_rooms. |
| room_name | string | – | Limit to one room (default: all rooms) |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| anomalies | array | yes | – |
| anomaly_count | number | yes | – |
| caveats | array | yes | – |
| home | object | yes | – |
| notes | array | yes | – |
| range | object | yes | – |
| requests | number | yes | – |
| rooms_analysed | array | yes | – |
| scale | string | yes | – |
| truncated | boolean | yes | – |
No examples provided.
netatmo_get_boiler_history Get boiler activity history ~266
How long the thermostat requested heat from the boiler over a period (minutes and share of time), per bucket. Requires a Netatmo thermostat. This is heat-demand time, not gas or energy consumption. Default: yesterday.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| max_points | integer | – | Maximum buckets/points returned (default 48 aggregated, 200 detailed). |
| mode | string | – | summary = statistics only; aggregated (default) = statistics + up to max_points buckets; detailed = raw values (bounded). |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| scale | string | – | Resolution. "auto" (default): 1hour up to 2 days, 1day up to 93 days, else 1week. |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| buckets | array | – | – |
| caveats | array | yes | – |
| coverage | object | yes | – |
| heat_demand_fraction | number|null | yes | Share of the covered time with heat demand (0–1) |
| home | object | yes | – |
| mode | string | yes | – |
| notes | array | yes | – |
| range | object | yes | – |
| requests | number | yes | Netatmo API requests used |
| scale | string | yes | – |
| thermostat_type | string | yes | – |
| total_heat_demand_minutes | number | yes | – |
| truncated | boolean | yes | – |
No examples provided.
netatmo_get_device_status Get device diagnostics ~87
Battery, radio/Wi-Fi signal, reachability, firmware and error codes of all devices of a home, or of one device.
| Name | Type | Req | Description |
|---|---|---|---|
| device_id | string | – | Device ID from netatmo_list_devices. Omit for all devices. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | yes | – |
| home | object | yes | – |
| observed_at | string | yes | – |
No examples provided.
netatmo_get_heating_status Get heating activity ~70
Whether the boiler is currently requested to heat, which rooms request heat (heating demand %), and anticipation. Demand is not boiler power or energy use.
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| boiler_on | boolean|null | yes | Whether the thermostat currently requests heat |
| boiler_source | string|null | yes | Thermostat type reporting boiler status |
| caveats | array | yes | – |
| heating_mode | string|null | yes | – |
| home | object | yes | – |
| observed_at | string | yes | ISO 8601 date-time with the home UTC offset |
| rooms | array | yes | – |
| rooms_requesting_heat | number | yes | – |
No examples provided.
netatmo_get_heating_summary Summarise heating over a period ~211
Per-room temperature statistics, mean setpoint, time below / within / above target, largest temperature drop and cool-down rate, plus total boiler heat-demand time. Default: yesterday. Deterministic calculations; no energy or gas figures.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| room_id | string | – | Room ID from netatmo_list_rooms. |
| room_name | string | – | Limit to one room (default: all rooms) |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| boiler | object | yes | – |
| caveats | array | yes | – |
| home | object | yes | – |
| notes | array | yes | – |
| overall | object | yes | – |
| range | object | yes | – |
| requests | number | yes | – |
| rooms | array | yes | – |
| scale | string | yes | – |
No examples provided.
netatmo_get_home Get Netatmo home details ~63
Details of one home: heating mode, schedules, rooms and devices (topology only; use the status tools for live values).
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| boiler_history_available | boolean | yes | – |
| default_manual_duration_min | number|null | yes | – |
| device_count | number | yes | – |
| device_summary | string | yes | – |
| devices | array | yes | – |
| heating_mode | string|null | yes | schedule | away | hg (frost guard) |
| id | string | yes | – |
| name | string | yes | – |
| room_count | number | yes | – |
| rooms | array | yes | – |
| schedules | array | yes | – |
| temperature_control_mode | string|null | yes | – |
| timezone | string | yes | IANA time zone of the home |
No examples provided.
netatmo_get_home_status Get current heating status of a home ~69
Current temperature, setpoint, mode and heating demand of every room, boiler on/off, and alerts (unreachable devices, low batteries, open windows).
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| alerts | array | yes | Unreachable devices, low batteries, open windows |
| boiler_on | boolean|null | yes | – |
| heating_mode | string|null | yes | – |
| home | object | yes | – |
| observed_at | string | yes | ISO 8601 date-time with the home UTC offset |
| rooms | array | yes | – |
No examples provided.
netatmo_get_room_status Get current room temperature and setpoint ~114
Current measured temperature and target temperature (setpoint) of one room, with setpoint mode, heating demand and open-window state. Identify the room by room_id or room_name.
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| room_id | string | – | Room ID from netatmo_list_rooms. |
| room_name | string | – | Room name (case- and accent-insensitive). Use room_id or room_name. |
| Name | Type | Req | Description |
|---|---|---|---|
| home | object | yes | – |
| observed_at | string | yes | – |
| room | object | yes | – |
No examples provided.
netatmo_get_schedules Get heating schedules ~87
Weekly heating schedules of a home: zones (e.g. Comfort, Night, Eco) with the setpoint of each room, away/frost-guard temperatures, and the timetable as day + time + zone. Shows which schedule is active.
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| home | object | yes | – |
| schedules | array | yes | – |
No examples provided.
netatmo_get_setpoint_history Get room setpoint history ~276
Target temperature (setpoint) history of a room, including the periods during which each setpoint applied. Default: last 24 h.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| max_points | integer | – | Maximum buckets/points returned (default 48 aggregated, 200 detailed). |
| mode | string | – | summary = statistics only; aggregated (default) = statistics + up to max_points buckets; detailed = raw values (bounded). |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| room_id | string | – | Room ID from netatmo_list_rooms. |
| room_name | string | – | Room name (case- and accent-insensitive). Use room_id or room_name. |
| scale | string | – | Measurement resolution. "auto" (default) picks the finest scale that fits the range. |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| buckets | array | – | aggregated mode |
| changes | array | – | setpoint only: periods with a constant setpoint |
| coverage | object | yes | – |
| home | object | yes | – |
| measure | string | yes | – |
| mode | string | yes | – |
| notes | array | yes | – |
| points | array | – | detailed mode |
| range | object | yes | – |
| requests | number | yes | Netatmo API requests used |
| room | object | yes | – |
| scale | string | yes | – |
| stats | – | yes | – |
| truncated | boolean | yes | – |
| unit | string | yes | – |
No examples provided.
netatmo_get_temperature_history Get room temperature history ~288
Measured temperature history of a room with statistics (min, max, mean, variability) and coverage/gaps. Default: last 24 h, aggregated. Missing data is reported, never filled in.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Range start, ISO 8601 (e.g. 2026-01-15 or 2026-01-15T07:30). Without an offset it is read in the home time zone. |
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| max_points | integer | – | Maximum buckets/points returned (default 48 aggregated, 200 detailed). |
| mode | string | – | summary = statistics only; aggregated (default) = statistics + up to max_points buckets; detailed = raw values (bounded). |
| period | string | – | Named period in the home time zone. Alternative to from/to. |
| room_id | string | – | Room ID from netatmo_list_rooms. |
| room_name | string | – | Room name (case- and accent-insensitive). Use room_id or room_name. |
| scale | string | – | Measurement resolution. "auto" (default) picks the finest scale that fits the range. |
| to | string | – | Range end, ISO 8601. Defaults to now when "from" is given. |
| Name | Type | Req | Description |
|---|---|---|---|
| buckets | array | – | aggregated mode |
| changes | array | – | setpoint only: periods with a constant setpoint |
| coverage | object | yes | – |
| home | object | yes | – |
| measure | string | yes | – |
| mode | string | yes | – |
| notes | array | yes | – |
| points | array | – | detailed mode |
| range | object | yes | – |
| requests | number | yes | Netatmo API requests used |
| room | object | yes | – |
| scale | string | yes | – |
| stats | – | yes | – |
| truncated | boolean | yes | – |
| unit | string | yes | – |
No examples provided.
netatmo_list_devices List devices ~75
List thermostats, radiator valves and relays/gateways of a home with their model, room and gateway. Use netatmo_get_device_status for battery, signal and reachability.
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| devices | array | yes | – |
| home | object | yes | – |
No examples provided.
netatmo_list_homes List Netatmo homes ~45
List the homes in the Netatmo account that have Energy devices (thermostats, radiator valves), with room and device counts and whether boiler history is available.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| homes | array | yes | – |
No examples provided.
netatmo_list_rooms List rooms ~55
List the rooms of a home with their IDs, types and the devices installed in each.
| Name | Type | Req | Description |
|---|---|---|---|
| home_id | string | – | Home ID from netatmo_list_homes. Optional when the account has a single home. |
| Name | Type | Req | Description |
|---|---|---|---|
| home | object | yes | – |
| rooms | array | yes | – |
No examples provided.
How do I install the Netatmo Energy MCP server?
Netatmo Energy runs locally as an npm package, launched with npx -y netatmo-energy-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · netatmo-energy-mcp
claude mcp add christophe77-netatmo-energy-mcp -- npx -y netatmo-energy-mcp
What is the Netatmo Energy MCP server?
Netatmo Energy is an MCP server listed in the public MCP registry as io.github.christophe77/netatmo-energy-mcp. MCP server for Netatmo thermostats and radiator valves: status, history, analytics, opt-in control. This page covers its npm package (netatmo-energy-mcp).
Is the Netatmo Energy MCP server safe to use?
Netatmo Energy scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 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 Netatmo Energy MCP server expose?
Netatmo Energy exposes 15 tools: netatmo_get_heating_summary, netatmo_compare_rooms, netatmo_detect_anomalies, netatmo_list_homes, netatmo_get_home, and 10 more. Their descriptions and schemas cost roughly 2,139 tokens of context every time the server is loaded.
Is the Netatmo Energy MCP server still maintained?
Netatmo Energy is still listed as active in the MCP registry. We last reached this channel on 17 October 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 Netatmo Energy MCP server under?
Netatmo 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.