leadgreen-mcp 0.3.0__tar.gz

leadgreen_mcp-0.3.0/.gitignore

@@ -0,0 +1,26 @@
+# Python
+__pycache__/
+*.py[cod]
+*.egg-info/
+.pytest_cache/
+.venv/
+venv/
+env/
+build/lib/
+build/out/
+
+# Node
+node_modules/
+
+# Secrets and local config
+.env
+.env.*
+*.pem
+*.key
+
+# Editor / OS
+.vscode/
+.idea/
+.DS_Store
+Thumbs.db
+

leadgreen_mcp-0.3.0/LICENSE

@@ -0,0 +1,202 @@
+
+                                 Apache License
+                           Version 2.0, January 2004
+                        http://www.apache.org/licenses/
+
+   TERMS AND CONDITIONS FOR USE, REPRODUCTION, AND DISTRIBUTION
+
+   1. Definitions.
+
+      "License" shall mean the terms and conditions for use, reproduction,
+      and distribution as defined by Sections 1 through 9 of this document.
+
+      "Licensor" shall mean the copyright owner or entity authorized by
+      the copyright owner that is granting the License.
+
+      "Legal Entity" shall mean the union of the acting entity and all
+      other entities that control, are controlled by, or are under common
+      control with that entity. For the purposes of this definition,
+      "control" means (i) the power, direct or indirect, to cause the
+      direction or management of such entity, whether by contract or
+      otherwise, or (ii) ownership of fifty percent (50%) or more of the
+      outstanding shares, or (iii) beneficial ownership of such entity.
+
+      "You" (or "Your") shall mean an individual or Legal Entity
+      exercising permissions granted by this License.
+
+      "Source" form shall mean the preferred form for making modifications,
+      including but not limited to software source code, documentation
+      source, and configuration files.
+
+      "Object" form shall mean any form resulting from mechanical
+      transformation or translation of a Source form, including but
+      not limited to compiled object code, generated documentation,
+      and conversions to other media types.
+
+      "Work" shall mean the work of authorship, whether in Source or
+      Object form, made available under the License, as indicated by a
+      copyright notice that is included in or attached to the work
+      (an example is provided in the Appendix below).
+
+      "Derivative Works" shall mean any work, whether in Source or Object
+      form, that is based on (or derived from) the Work and for which the
+      editorial revisions, annotations, elaborations, or other modifications
+      represent, as a whole, an original work of authorship. For the purposes
+      of this License, Derivative Works shall not include works that remain
+      separable from, or merely link (or bind by name) to the interfaces of,
+      the Work and Derivative Works thereof.
+
+      "Contribution" shall mean any work of authorship, including
+      the original version of the Work and any modifications or additions
+      to that Work or Derivative Works thereof, that is intentionally
+      submitted to Licensor for inclusion in the Work by the copyright owner
+      or by an individual or Legal Entity authorized to submit on behalf of
+      the copyright owner. For the purposes of this definition, "submitted"
+      means any form of electronic, verbal, or written communication sent
+      to the Licensor or its representatives, including but not limited to
+      communication on electronic mailing lists, source code control systems,
+      and issue tracking systems that are managed by, or on behalf of, the
+      Licensor for the purpose of discussing and improving the Work, but
+      excluding communication that is conspicuously marked or otherwise
+      designated in writing by the copyright owner as "Not a Contribution."
+
+      "Contributor" shall mean Licensor and any individual or Legal Entity
+      on behalf of whom a Contribution has been received by Licensor and
+      subsequently incorporated within the Work.
+
+   2. Grant of Copyright License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      copyright license to reproduce, prepare Derivative Works of,
+      publicly display, publicly perform, sublicense, and distribute the
+      Work and such Derivative Works in Source or Object form.
+
+   3. Grant of Patent License. Subject to the terms and conditions of
+      this License, each Contributor hereby grants to You a perpetual,
+      worldwide, non-exclusive, no-charge, royalty-free, irrevocable
+      (except as stated in this section) patent license to make, have made,
+      use, offer to sell, sell, import, and otherwise transfer the Work,
+      where such license applies only to those patent claims licensable
+      by such Contributor that are necessarily infringed by their
+      Contribution(s) alone or by combination of their Contribution(s)
+      with the Work to which such Contribution(s) was submitted. If You
+      institute patent litigation against any entity (including a
+      cross-claim or counterclaim in a lawsuit) alleging that the Work
+      or a Contribution incorporated within the Work constitutes direct
+      or contributory patent infringement, then any patent licenses
+      granted to You under this License for that Work shall terminate
+      as of the date such litigation is filed.
+
+   4. Redistribution. You may reproduce and distribute copies of the
+      Work or Derivative Works thereof in any medium, with or without
+      modifications, and in Source or Object form, provided that You
+      meet the following conditions:
+
+      (a) You must give any other recipients of the Work or
+          Derivative Works a copy of this License; and
+
+      (b) You must cause any modified files to carry prominent notices
+          stating that You changed the files; and
+
+      (c) You must retain, in the Source form of any Derivative Works
+          that You distribute, all copyright, patent, trademark, and
+          attribution notices from the Source form of the Work,
+          excluding those notices that do not pertain to any part of
+          the Derivative Works; and
+
+      (d) If the Work includes a "NOTICE" text file as part of its
+          distribution, then any Derivative Works that You distribute must
+          include a readable copy of the attribution notices contained
+          within such NOTICE file, excluding those notices that do not
+          pertain to any part of the Derivative Works, in at least one
+          of the following places: within a NOTICE text file distributed
+          as part of the Derivative Works; within the Source form or
+          documentation, if provided along with the Derivative Works; or,
+          within a display generated by the Derivative Works, if and
+          wherever such third-party notices normally appear. The contents
+          of the NOTICE file are for informational purposes only and
+          do not modify the License. You may add Your own attribution
+          notices within Derivative Works that You distribute, alongside
+          or as an addendum to the NOTICE text from the Work, provided
+          that such additional attribution notices cannot be construed
+          as modifying the License.
+
+      You may add Your own copyright statement to Your modifications and
+      may provide additional or different license terms and conditions
+      for use, reproduction, or distribution of Your modifications, or
+      for any such Derivative Works as a whole, provided Your use,
+      reproduction, and distribution of the Work otherwise complies with
+      the conditions stated in this License.
+
+   5. Submission of Contributions. Unless You explicitly state otherwise,
+      any Contribution intentionally submitted for inclusion in the Work
+      by You to the Licensor shall be under the terms and conditions of
+      this License, without any additional terms or conditions.
+      Notwithstanding the above, nothing herein shall supersede or modify
+      the terms of any separate license agreement you may have executed
+      with Licensor regarding such Contributions.
+
+   6. Trademarks. This License does not grant permission to use the trade
+      names, trademarks, service marks, or product names of the Licensor,
+      except as required for reasonable and customary use in describing the
+      origin of the Work and reproducing the content of the NOTICE file.
+
+   7. Disclaimer of Warranty. Unless required by applicable law or
+      agreed to in writing, Licensor provides the Work (and each
+      Contributor provides its Contributions) on an "AS IS" BASIS,
+      WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or
+      implied, including, without limitation, any warranties or conditions
+      of TITLE, NON-INFRINGEMENT, MERCHANTABILITY, or FITNESS FOR A
+      PARTICULAR PURPOSE. You are solely responsible for determining the
+      appropriateness of using or redistributing the Work and assume any
+      risks associated with Your exercise of permissions under this License.
+
+   8. Limitation of Liability. In no event and under no legal theory,
+      whether in tort (including negligence), contract, or otherwise,
+      unless required by applicable law (such as deliberate and grossly
+      negligent acts) or agreed to in writing, shall any Contributor be
+      liable to You for damages, including any direct, indirect, special,
+      incidental, or consequential damages of any character arising as a
+      result of this License or out of the use or inability to use the
+      Work (including but not limited to damages for loss of goodwill,
+      work stoppage, computer failure or malfunction, or any and all
+      other commercial damages or losses), even if such Contributor
+      has been advised of the possibility of such damages.
+
+   9. Accepting Warranty or Additional Liability. While redistributing
+      the Work or Derivative Works thereof, You may choose to offer,
+      and charge a fee for, acceptance of support, warranty, indemnity,
+      or other liability obligations and/or rights consistent with this
+      License. However, in accepting such obligations, You may act only
+      on Your own behalf and on Your sole responsibility, not on behalf
+      of any other Contributor, and only if You agree to indemnify,
+      defend, and hold each Contributor harmless for any liability
+      incurred by, or claims asserted against, such Contributor by reason
+      of your accepting any such warranty or additional liability.
+
+   END OF TERMS AND CONDITIONS
+
+   APPENDIX: How to apply the Apache License to your work.
+
+      To apply the Apache License to your work, attach the following
+      boilerplate notice, with the fields enclosed by brackets "[]"
+      replaced with your own identifying information. (Don't include
+      the brackets!)  The text should be enclosed in the appropriate
+      comment syntax for the file format. We also recommend that a
+      file or class name and description of purpose be included on the
+      same "printed page" as the copyright notice for easier
+      identification within third-party archives.
+
+   Copyright [yyyy] [name of copyright owner]
+
+   Licensed under the Apache License, Version 2.0 (the "License");
+   you may not use this file except in compliance with the License.
+   You may obtain a copy of the License at
+
+       http://www.apache.org/licenses/LICENSE-2.0
+
+   Unless required by applicable law or agreed to in writing, software
+   distributed under the License is distributed on an "AS IS" BASIS,
+   WITHOUT WARRANTIES OR CONDITIONS OF ANY KIND, either express or implied.
+   See the License for the specific language governing permissions and
+   limitations under the License.

leadgreen_mcp-0.3.0/PKG-INFO

@@ -0,0 +1,123 @@
+Metadata-Version: 2.5
+Name: leadgreen-mcp
+Version: 0.3.0
+Summary: MCP server for the Lead Green index: GPU energy per million output tokens, by model, GPU and configuration, with grid carbon.
+Project-URL: Homepage, https://leadgreen.ai/
+Project-URL: Documentation, https://leadgreen.ai/mcp/
+Project-URL: Data API, https://leadgreen.ai/api/
+Project-URL: Changes, https://leadgreen.ai/index/#changes
+Project-URL: Source, https://github.com/katonic-dev/leadgreen-ai
+Project-URL: Issues, https://github.com/katonic-dev/leadgreen-ai/issues
+Author-email: Prem Naraindas <hello@leadgreen.ai>
+Maintainer-email: "Lead Green, a Katonic project" <hello@leadgreen.ai>
+License-Expression: Apache-2.0
+License-File: LICENSE
+Keywords: b200,carbon,energy,gpu,h100,inference,leadgreen,llm,mcp,ml-energy,model-context-protocol,sustainability,tokens,watt-hours
+Classifier: Development Status :: 4 - Beta
+Classifier: Intended Audience :: Developers
+Classifier: Intended Audience :: Science/Research
+Classifier: License :: OSI Approved :: Apache Software License
+Classifier: Operating System :: OS Independent
+Classifier: Programming Language :: Python :: 3
+Classifier: Programming Language :: Python :: 3.10
+Classifier: Programming Language :: Python :: 3.11
+Classifier: Programming Language :: Python :: 3.12
+Classifier: Programming Language :: Python :: 3.13
+Classifier: Programming Language :: Python :: 3.14
+Classifier: Topic :: Scientific/Engineering
+Classifier: Topic :: Scientific/Engineering :: Information Analysis
+Requires-Python: >=3.10
+Requires-Dist: httpx>=0.27
+Requires-Dist: mcp>=1.2
+Description-Content-Type: text/markdown
+
+# leadgreen-mcp
+
+Lead Green is a public index of the GPU energy it takes to serve a million output tokens (watt-hours per million output tokens), by model, GPU and configuration, with grid carbon intensity to price it anywhere, published as open data with a JSON API and an MCP server under CC BY 4.0. Every figure comes from a named public source with a retrieval date; it is a Katonic project, run and paid for by Katonic, and takes no money from hardware, cloud or model vendors.
+
+Lead Green is run and paid for by Katonic, which sells a sovereign AI platform; it takes no money from hardware, cloud or model vendors.
+
+This package is the MCP server for that index: GPU watt-hours per million output tokens by model, GPU and configuration, with grid carbon intensity by country and GPU hardware reference data. Every answer names its source and carries the caveat that the figures are GPU-only floors measured on a busy server.
+
+## Install
+
+```
+pip install leadgreen-mcp
+```
+
+or, without installing, `uvx leadgreen-mcp`.
+
+The same wheel is served from the site, with its SHA-256 printed on <https://leadgreen.ai/mcp/>:
+
+```
+pip install https://leadgreen.ai/dist/leadgreen_mcp-0.3.0-py3-none-any.whl
+```
+
+and the source installs with `pip install "git+https://github.com/katonic-dev/leadgreen-ai#subdirectory=leadgreen-mcp"`.
+
+Python 3.10 or later. Works with the `mcp` Python SDK 1.x and 2.x.
+
+## Versions
+
+Two things are versioned separately. The **package** is 0.3.0 (this file, `pyproject.toml`, the wheel name). The **data** is a dated release of the Lead Green API; the copy bundled in the package is the release named in `leadgreen_mcp/data/manifest.json` (`data_version`), and the server reads the live API first, so a session normally answers from the current release whatever package version is installed. Every response says which it used in `data_source` and `data_updated`.
+
+## Tools
+
+| Tool | What it answers |
+|---|---|
+| `list_models` | Which models are on the index and on which GPUs |
+| `energy_per_million_tokens(model, gpu?, itl_deadline_ms?)` | The best row per GPU for a model |
+| `estimate(model, output_tokens, gpu?, country?, running_batch?, num_gpus?, itl_deadline_ms?, pue?, system_power_ratio?)` | GPU energy in Wh and kWh for a token count, kg CO2e for a grid, and optionally energy at the meter |
+| `compare_gpus(model, itl_deadline_ms?)` | H100 versus B200 for a model |
+| `concurrency_curve(model, gpu)` | Energy per token at every measured running batch |
+| `grid_intensity(country)` | Annual average gCO2e per kWh for a country or World |
+| `gpu_hardware(gpu?)` | Max TDP, memory, MIG profiles and whole-system ceilings |
+| `sources` | Every source, version, retrieval date and licence |
+
+Resource: `leadgreen://manifest`.
+
+### Parameters
+
+- `running_batch`: the average running batch the server holds, meaning how many requests it decodes at once (vLLM `num_requests_running`). The estimate then uses the measured configuration nearest to it, on the same GPU count as the best row (for example 2 x H100 for Qwen 3 32B), and widens to every GPU count only when that count has no measurements. `requests_in_flight` is the old name and is still accepted; giving both with different values is an error. Responses carry both `avg_running_batch` and `avg_requests_in_flight` (the same number).
+- `num_gpus`: use configurations on exactly this many GPUs.
+- `itl_deadline_ms`: the latency ceiling for choosing the best row. Rows whose median inter-token latency is at or under it are kept, and the lowest energy wins. Default 500 ms, the leaderboard's own default.
+- `pue` and `system_power_ratio` (each at least 1.0): when either is given, `estimate` also returns energy at the meter, GPU energy x system_power_ratio x pue, labelled as such and shown beside the GPU figure. These are your assumptions, not measurements. For scale, a DGX B200 at its 14.3 kW maximum over 8 x 1.0 kW of GPU power is a ratio of about 1.79.
+- `country`: a country name, the site's short name, an ISO 3166 alpha-3 or alpha-2 code, or `World`. Common names work: UK, GB, Britain, US, USA, America, Turkey, Korea, South Korea, Russia. Exact matches win over partial ones, and queries of three characters or fewer must match exactly, so `US` never lands on Australia. Grid figures are the 2024 annual average; `years` and `latest_year` show the other years available. They are lifecycle, location-based figures for comparing places, not a Scope 2 figure to file.
+
+### Fields on every response
+
+- `caveat`: the same sentence on every tool, taken from the API's `index.json`. Pass it on.
+- `boundary`: `gpu_only` for the measured figures.
+- `data_source`: `live` (fetched from the API), `bundled snapshot` (the copy shipped in the package) or `local folder` (when `LEADGREEN_API_BASE` is a folder).
+- `data_updated` and `data_version`: how current the data is.
+
+## What the server sends, and where
+
+- Only HTTP GET requests to `https://leadgreen.ai/api/v1` (or the base you set), for the published JSON files: at most once per file per session, then cached in memory.
+- Your questions, prompts and tool arguments never leave your machine. No request carries them; lookups and arithmetic happen locally.
+- If a fetch fails, the server prints one line on stderr and uses the bundled snapshot for the rest of the session without trying the network again.
+- For no network at all, set `LEADGREEN_API_BASE` to a local folder holding the API files (for example a copy of `leadgreen_mcp/data`). Any other URL works too.
+
+## Client configuration
+
+Claude Desktop or Cursor (`claude_desktop_config.json` / `.cursor/mcp.json`):
+
+```json
+{ "mcpServers": { "leadgreen": { "command": "leadgreen-mcp" } } }
+```
+
+With no network:
+
+```json
+{ "mcpServers": { "leadgreen": { "command": "leadgreen-mcp", "env": { "LEADGREEN_API_BASE": "/path/to/api/v1" } } } }
+```
+
+Claude Code: `claude mcp add leadgreen -- leadgreen-mcp`
+
+### If Claude Desktop cannot find `leadgreen-mcp`
+
+Claude Desktop started from Finder, the Dock or the Start menu does not see the PATH your terminal uses, so a bare `leadgreen-mcp` can fail to start. Use the full path instead: run `which leadgreen-mcp` (macOS, Linux) or `where leadgreen-mcp` (Windows) and put the result in `command`. Alternatively, point `command` at the full path of your Python and set `"args": ["-m", "leadgreen_mcp.server"]`.
+
+## Licence
+
+Apache 2.0 for the code (see `LICENSE`). The data keeps the licences of its sources, listed in the manifest.

leadgreen_mcp-0.3.0/README.md

@@ -0,0 +1,90 @@
+# leadgreen-mcp
+
+Lead Green is a public index of the GPU energy it takes to serve a million output tokens (watt-hours per million output tokens), by model, GPU and configuration, with grid carbon intensity to price it anywhere, published as open data with a JSON API and an MCP server under CC BY 4.0. Every figure comes from a named public source with a retrieval date; it is a Katonic project, run and paid for by Katonic, and takes no money from hardware, cloud or model vendors.
+
+Lead Green is run and paid for by Katonic, which sells a sovereign AI platform; it takes no money from hardware, cloud or model vendors.
+
+This package is the MCP server for that index: GPU watt-hours per million output tokens by model, GPU and configuration, with grid carbon intensity by country and GPU hardware reference data. Every answer names its source and carries the caveat that the figures are GPU-only floors measured on a busy server.
+
+## Install
+
+```
+pip install leadgreen-mcp
+```
+
+or, without installing, `uvx leadgreen-mcp`.
+
+The same wheel is served from the site, with its SHA-256 printed on <https://leadgreen.ai/mcp/>:
+
+```
+pip install https://leadgreen.ai/dist/leadgreen_mcp-0.3.0-py3-none-any.whl
+```
+
+and the source installs with `pip install "git+https://github.com/katonic-dev/leadgreen-ai#subdirectory=leadgreen-mcp"`.
+
+Python 3.10 or later. Works with the `mcp` Python SDK 1.x and 2.x.
+
+## Versions
+
+Two things are versioned separately. The **package** is 0.3.0 (this file, `pyproject.toml`, the wheel name). The **data** is a dated release of the Lead Green API; the copy bundled in the package is the release named in `leadgreen_mcp/data/manifest.json` (`data_version`), and the server reads the live API first, so a session normally answers from the current release whatever package version is installed. Every response says which it used in `data_source` and `data_updated`.
+
+## Tools
+
+| Tool | What it answers |
+|---|---|
+| `list_models` | Which models are on the index and on which GPUs |
+| `energy_per_million_tokens(model, gpu?, itl_deadline_ms?)` | The best row per GPU for a model |
+| `estimate(model, output_tokens, gpu?, country?, running_batch?, num_gpus?, itl_deadline_ms?, pue?, system_power_ratio?)` | GPU energy in Wh and kWh for a token count, kg CO2e for a grid, and optionally energy at the meter |
+| `compare_gpus(model, itl_deadline_ms?)` | H100 versus B200 for a model |
+| `concurrency_curve(model, gpu)` | Energy per token at every measured running batch |
+| `grid_intensity(country)` | Annual average gCO2e per kWh for a country or World |
+| `gpu_hardware(gpu?)` | Max TDP, memory, MIG profiles and whole-system ceilings |
+| `sources` | Every source, version, retrieval date and licence |
+
+Resource: `leadgreen://manifest`.
+
+### Parameters
+
+- `running_batch`: the average running batch the server holds, meaning how many requests it decodes at once (vLLM `num_requests_running`). The estimate then uses the measured configuration nearest to it, on the same GPU count as the best row (for example 2 x H100 for Qwen 3 32B), and widens to every GPU count only when that count has no measurements. `requests_in_flight` is the old name and is still accepted; giving both with different values is an error. Responses carry both `avg_running_batch` and `avg_requests_in_flight` (the same number).
+- `num_gpus`: use configurations on exactly this many GPUs.
+- `itl_deadline_ms`: the latency ceiling for choosing the best row. Rows whose median inter-token latency is at or under it are kept, and the lowest energy wins. Default 500 ms, the leaderboard's own default.
+- `pue` and `system_power_ratio` (each at least 1.0): when either is given, `estimate` also returns energy at the meter, GPU energy x system_power_ratio x pue, labelled as such and shown beside the GPU figure. These are your assumptions, not measurements. For scale, a DGX B200 at its 14.3 kW maximum over 8 x 1.0 kW of GPU power is a ratio of about 1.79.
+- `country`: a country name, the site's short name, an ISO 3166 alpha-3 or alpha-2 code, or `World`. Common names work: UK, GB, Britain, US, USA, America, Turkey, Korea, South Korea, Russia. Exact matches win over partial ones, and queries of three characters or fewer must match exactly, so `US` never lands on Australia. Grid figures are the 2024 annual average; `years` and `latest_year` show the other years available. They are lifecycle, location-based figures for comparing places, not a Scope 2 figure to file.
+
+### Fields on every response
+
+- `caveat`: the same sentence on every tool, taken from the API's `index.json`. Pass it on.
+- `boundary`: `gpu_only` for the measured figures.
+- `data_source`: `live` (fetched from the API), `bundled snapshot` (the copy shipped in the package) or `local folder` (when `LEADGREEN_API_BASE` is a folder).
+- `data_updated` and `data_version`: how current the data is.
+
+## What the server sends, and where
+
+- Only HTTP GET requests to `https://leadgreen.ai/api/v1` (or the base you set), for the published JSON files: at most once per file per session, then cached in memory.
+- Your questions, prompts and tool arguments never leave your machine. No request carries them; lookups and arithmetic happen locally.
+- If a fetch fails, the server prints one line on stderr and uses the bundled snapshot for the rest of the session without trying the network again.
+- For no network at all, set `LEADGREEN_API_BASE` to a local folder holding the API files (for example a copy of `leadgreen_mcp/data`). Any other URL works too.
+
+## Client configuration
+
+Claude Desktop or Cursor (`claude_desktop_config.json` / `.cursor/mcp.json`):
+
+```json
+{ "mcpServers": { "leadgreen": { "command": "leadgreen-mcp" } } }
+```
+
+With no network:
+
+```json
+{ "mcpServers": { "leadgreen": { "command": "leadgreen-mcp", "env": { "LEADGREEN_API_BASE": "/path/to/api/v1" } } } }
+```
+
+Claude Code: `claude mcp add leadgreen -- leadgreen-mcp`
+
+### If Claude Desktop cannot find `leadgreen-mcp`
+
+Claude Desktop started from Finder, the Dock or the Start menu does not see the PATH your terminal uses, so a bare `leadgreen-mcp` can fail to start. Use the full path instead: run `which leadgreen-mcp` (macOS, Linux) or `where leadgreen-mcp` (Windows) and put the result in `command`. Alternatively, point `command` at the full path of your Python and set `"args": ["-m", "leadgreen_mcp.server"]`.
+
+## Licence
+
+Apache 2.0 for the code (see `LICENSE`). The data keeps the licences of its sources, listed in the manifest.

leadgreen_mcp-0.3.0/leadgreen_mcp/__init__.py

@@ -0,0 +1,3 @@
+"""Lead Green MCP server: the Green Tokens index as tools for AI assistants."""
+
+__version__ = "0.3.0"

leadgreen_mcp-0.3.0/leadgreen_mcp/data/changes.json

@@ -0,0 +1,52 @@
+{
+  "version": "1",
+  "updated": "2026-10-19",
+  "data_version": "2026-10-19",
+  "note": "One entry per change to the published data or its description, newest last.",
+  "changes": [
+    {
+      "date": "2026-09-26",
+      "summary": "First build. 32 index rows from ML.ENERGY v3.0 (data compiled 16 February 2026), grid intensities from Ember (2024), NVIDIA specifications, AI Energy Score December 2025 round. The API, the MCP server and the first blog post.",
+      "documents": [
+        "*"
+      ],
+      "reason": "first build",
+      "source_version": "3.0 (released 2025-12-01); data compiled 2026-02-16"
+    },
+    {
+      "date": "2026-09-27",
+      "summary": "Corrections after a nine-reader review, before launch. The ML.ENERGY data is dated to its compile date, not a banner update; the latency ceiling is the leaderboard's own 500 ms (no row moved); \"requests in flight\" is renamed running batch; full concurrency ladders; all AI Energy Score December rows; a two-task table; the carbon basis, grid years and display names; seven-decimal joules; additive API fields (data_version, row_id, repeat, p95_itl_ms, avg_running_batch, boundary, years, latest_year, iso2, display_name, source_label); changes.json, measurements.json, the measurement schema, a dated release archive, CSV, zip and TypeScript types.",
+      "documents": [
+        "*"
+      ],
+      "reason": "review corrections",
+      "source_version": "3.0 (released 2025-12-01); data compiled 2026-02-16"
+    },
+    {
+      "date": "2026-10-17",
+      "summary": "Ember's October 2026 release of its yearly electricity data (file dated 6 October 2026) replaces the September 2026 release. The 2024 emissions intensity moves for 26 of the 193 grids and World, seven of them on the carbon table (United Arab Emirates 467.5 to 477.3 gCO2e per kWh, Sri Lanka 386.8 to 392.8, Australia 554.0 to 549.5, Saudi Arabia 691.9 to 689.1, Taiwan 636.2 to 635.2, Japan 483.6 to 484.3, Serbia 668.0 to 668.4), and every kilogram figure priced on them follows. 2025 rows are added for Saudi Arabia and the United Arab Emirates. The reference year stays 2024, the latest with every listed grid present. No energy figure changes.",
+      "documents": [
+        "grid.json",
+        "manifest.json"
+      ],
+      "reason": "source release",
+      "source_version": "October 2026 release (file last modified 2026-10-06)"
+    },
+    {
+      "date": "2026-10-18",
+      "summary": "The publisher's registered office is added to About and to the manifest. No change to the data or its description.",
+      "documents": [
+        "manifest.json"
+      ],
+      "reason": "publisher",
+      "source_version": "3.0 (released 2025-12-01); data compiled 2026-02-16"
+    },
+    {
+      "date": "2026-10-19",
+      "summary": "Launch. Three blog posts: how much energy an AI query uses, what watt-hours per million tokens means, and why an idle GPU wastes energy. The site now serves from GitHub Pages at leadgreen.ai. No change to the data or its description.",
+      "documents": [],
+      "reason": "launch",
+      "source_version": "3.0 (released 2025-12-01); data compiled 2026-02-16"
+    }
+  ]
+}