Ext Ops Panel
Open dashboard
Comparison

co2-tracker vs io.github.ByteOverDev/peak-window

co2-tracker is a plugin bundle for AI coding tools published by gwittebolle. Marketplaces we read that list it: 1 (Claude Code: claude-plugins-community). io.github.ByteOverDev/peak-window is an MCP server published by ByteOverDev. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-10-14. This pair was picked by a reader, not by our comparison rule, so search engines are asked not to index the page.

Where each is published

Where each is published
Marketplaceco2-trackerio.github.ByteOverDev/peak-window
Claude Code: claude-plugins-community Listed
Version: 1.1.2
Forks (GitHub): 18
Stars (GitHub): 211
Not marked · First seen
Not listed
Official MCP Registry Not listed Listed
Version: 1.0.2
Downloads/month (npm): 174
Downloads/week (npm): 33
Forks (GitHub): 0
Stars (GitHub): 3
Not marked · First seen

Each figure is the marketplace's own and is never added up across marketplaces. A marketplace that publishes no figure shows none: no number is not zero.

The facts side by side

co2-tracker vs io.github.ByteOverDev/peak-window
Factco2-trackerio.github.ByteOverDev/peak-window
Marketplaces that list it11
Stars (GitHub) (differs)211 (better)3 (worse)
Forks (GitHub) (differs)18 (better)0 (worse)
Last releaseNot publishedNot published
Where it runs (differs)Installs as a plugin bundleOn your machine (peak-window)
Transport (differs)Not statedstdio
Tools it declaresNot publishedNot published
Environment variables it asks forNot publishedNot published
Hooks it runs (differs)2Not published
Parts of the bundle (differs)5Not a bundle
Licence (differs)MITNot stated
Repository (differs)github.com/gwittebolle/claude-carbongithub.com/byteoverdev/peak-window-mcp-app
Changes in the last 7 days00
First seen2026-10-112026-10-11

Lines where the two differ have a tinted background and bold values. Where the data itself says which value is better (more marketplaces, a larger figure of the same marketplace, a fresher release, a verified mark on a marketplace that lists both), the better one is also marked green with ▲ and the worse one red with ▼. Where it runs, the transport, the tools, the settings, hooks, the bundle's parts, the licence and the week's changes are marked only as different: more or fewer is not better in itself.

What each says it does

co2-tracker

In its own words, on Claude Code: claude-plugins-community:

Track the carbon footprint of your Claude Code sessions. Adds a live CO2 estimate to the status line, persists sessions to a local SQLite database, and generates shareable PNG report cards. Based on peer-reviewed emission factors from Jegham et al. 2025.

io.github.ByteOverDev/peak-window

In its own words, on Official MCP Registry:

Ranks the best weather windows to climb any peak worldwide, on the sharpest regional model.

How to run each

co2-tracker As a Claude Code plugin

Claude Code
/plugin marketplace add anthropics/claude-plugins-community
/plugin install co2-tracker@claude-community

io.github.ByteOverDev/peak-window As a local MCP server: npm package

Claude Code
claude mcp add --transport stdio peak-window -- npx -y peak-window

Commands built only from what the marketplaces declare; the full set for every client is on each card.

Tools each declares

Neither one's marketplaces publish a list of tools, so there is nothing to compare.

Settings each asks for

Neither one's marketplaces publish the settings it asks for.

What it can do: co2-tracker · What it can do: io.github.ByteOverDev/peak-window · Compare two other plugins

Data comes from the public marketplace file https://github.com/anthropics/claude-plugins-community/blob/HEAD/.claude-plugin/marketplace.json. Data comes from the Official MCP Registry (registry.modelcontextprotocol.io), CC0 1.0. Figures come from our own regular passes over the marketplaces, last read on . We publish no contact details for plugin publishers.

Where the data comes from: how the catalog is built