Execute chiller-cop-efficiency-mcp vs io.github.ezumba/exergynet
Execute chiller-cop-efficiency-mcp is an MCP server published by Evozim. Marketplaces we read that list it: 1 (Official MCP Registry). io.github.ezumba/exergynet is an MCP server published by ezumba. Marketplaces we read that list it: 1 (Official MCP Registry). As of our marketplace pass on 2026-11-07. 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
| Marketplace |  io.github.ezumba/exergynet | |
|---|---|---|
| Official MCP Registry | Listed Version: 2.0.0 No figure published Not marked · First seen |
Listed Version: 0.2.6 Downloads/month (npm): 183 Downloads/week (npm): 77 Forks (GitHub): 0 Stars (GitHub): 0 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
| Fact | Execute chiller-cop-efficiency-mcp | io.github.ezumba/exergynet |
|---|---|---|
| Marketplaces that list it | 1 | 1 |
| Stars (GitHub) (differs) | No figure on GitHub | 0 |
| Forks (GitHub) (differs) | No figure on GitHub | 0 |
| Last release | Not published | Not published |
| Where it runs (differs) | Remote server (api.m2mcent.com/chiller-cop-efficiency-mcp/sse) | On your machine (exergynet-mcp-server) |
| Transport (differs) | SSE | stdio |
| Tools it declares | Not published | Not published |
| Environment variables it asks for (differs) | Not published | 1, secrets among them: 0 |
| Licence | Not stated | Not stated |
| Repository (differs) | Not stated | github.com/ezumba/exergynet-mcp-server |
| Changes in the last 7 days | 0 | 0 |
| First seen | 2026-10-11 | 2026-10-11 |
| Endpoint at the last check (differs) | Status out of date: last check 2 days ago returned HTTP 402 | no remote endpoint we check |
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
Execute chiller-cop-efficiency-mcp
Premium agentic endpoint for chiller-cop-efficiency-mcp.
io.github.ezumba/exergynet
Read-only ExergyNet MCP lookups and compute-cost estimates; write settlement is disabled.
How to run each
Execute chiller-cop-efficiency-mcp As a remote MCP server
claude mcp add --transport sse chiller-cop-efficiency-mcp https://api.m2mcent.com/chiller-cop-efficiency-mcp/sse --header "Payment-Signature: <YOUR_PAYMENT_SIGNATURE>"Requires: Payment-Signature header
io.github.ezumba/exergynet As a local MCP server: npm package
claude mcp add --transport stdio exergynet -- npx -y exergynet-mcp-serverCommands built only from what the marketplaces declare; the full set for every client is on each card.
Only Execute chiller-cop-efficiency-mcp has a remote endpoint we check. How we check endpoints
Tools each declares
Neither one's marketplaces publish a list of tools, so there is nothing to compare.
Settings each asks for
The marketplaces of Execute chiller-cop-efficiency-mcp publish no settings it asks for, so we do not compare settings.
What it can do: Execute chiller-cop-efficiency-mcp · What it can do: io.github.ezumba/exergynet · Compare two other plugins
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.