# EcoCompute Should-I-Quantize Estimator (remote · ecocompute-estimator.zhanghongping1982.workers.dev)

Energy impact of LLM quantization, calibrated to measured GPU data. Every answer states its basis.

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

## Components

- remote · `ecocompute-estimator.zhanghongping1982.workers.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator.md), [page](https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator)

## Channel facts

- Endpoint: `https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 4 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 515 tokens (~128/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 93/100
  - Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the EcoCompute Should-I-Quantize Estimator MCP server?

EcoCompute Should-I-Quantize Estimator is a hosted endpoint at https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp, so there is nothing to install locally. 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 --transport http hongping-zh-ecocompute-estimator 'https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "hongping-zh-ecocompute-estimator": {
      "url": "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "hongping-zh-ecocompute-estimator": {
      "type": "http",
      "url": "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.hongping-zh-ecocompute-estimator]
url = "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "hongping-zh-ecocompute-estimator": {
      "type": "remote",
      "url": "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add hongping-zh-ecocompute-estimator --url 'https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  hongping-zh-ecocompute-estimator:
    url: "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "hongping-zh-ecocompute-estimator": {
      "Transport": "http",
      "Url": "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add hongping-zh-ecocompute-estimator -t streamable-http -u 'https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "hongping-zh-ecocompute-estimator": {
      "type": "http",
      "url": "https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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 73, +1)

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

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

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

### 2026-11-17 (score 71, +1)

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

### 2026-11-15 (score 70, +1)

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

### 2026-11-13 (score 69, +1)

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

### 2026-11-10 (score 68, +1)

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

### 2026-11-08 (score 67, +1)

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

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

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

## MCP tools (4)

### `estimate_quantization_energy` (~184 tokens)

Estimate the task-level energy change (ΔE% vs FP16) of weight-only quantization (NF4 or INT8) for a model of a given size on a GPU architecture class, from measured-anchored curves. The answer carries basis (measured/interpolated/estimated), confidence and evidence boundaries.

Input parameters:

- `arch` (string): GPU architecture class
- `batch` (integer): batch size (default 1; >1 shrinks savings — modelled, not measured)
- `ctx` (integer): context length (default 2048)
- `params_b` (number): model size in billions of parameters, e.g. 7
- `precision` (string): quantization format (default NF4)
- `q` (string): alternative: plain-English query, e.g. '13B on A100 int8 batch 32'

### `get_quantization_crossover` (~68 tokens)

Get the model-size crossover for NF4/INT8 per architecture: below it quantization costs energy, above it saves. Crossovers belong to a card + software stack, not an architecture — the answer says so.

Input parameters:

- `arch` (string): optional: limit to one architecture

### `list_data_coverage` (~65 tokens)

List what is actually measured (GPU architecture × precision × size range, NVML direct), what is borrowed/estimated, and where the gaps are. Use this before trusting an estimate at the edges of coverage, and to answer 'is there data for my GPU?' honestly.

### `search_measurements` (~71 tokens)

Search the measured anchors by model name, GPU name, architecture or size. Returns ΔE% vs FP16 per anchor with run counts — the raw evidence behind the curves.

Input parameters:

- `query` (string, required): model ('TinyLlama'), GPU ('4090'), architecture ('ampere') or size ('7')

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator#diagnostics

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 71
- 2026-11-17: 71
- 2026-11-16: 70
- 2026-11-15: 70
- 2026-11-14: 69
- 2026-11-13: 69
- 2026-11-12: 68
- 2026-11-11: 68
- 2026-11-10: 68
- 2026-11-09: 67
- 2026-11-08: 67
- 2026-11-07: 66
- 2026-11-06: 66
- 2026-11-05: 65
- 2026-11-04: 65
- 2026-11-03: 64
- 2026-11-02: 64
- 2026-11-01: 63
- 2026-10-31: 63
- 2026-10-30: 62
- 2026-10-29: 62
- 2026-10-28: 61
- 2026-10-27: 61
- 2026-10-26: 61
- 2026-10-25: 60
- 2026-10-24: 60

## Common questions

### What is the EcoCompute Should-I-Quantize Estimator MCP server?

EcoCompute Should-I-Quantize Estimator is an MCP server listed in the public MCP registry as io.github.hongping-zh/ecocompute-estimator. Energy impact of LLM quantization, calibrated to measured GPU data. Every answer states its basis. This page covers its hosted endpoint (https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp).

### Is the EcoCompute Should-I-Quantize Estimator MCP server safe to use?

EcoCompute Should-I-Quantize Estimator scores 73 out of 100 on VerifyMCP. 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 EcoCompute Should-I-Quantize Estimator MCP server expose?

EcoCompute Should-I-Quantize Estimator exposes 4 tools: estimate_quantization_energy, get_quantization_crossover, list_data_coverage, search_measurements. Their descriptions and schemas cost roughly 388 tokens of context every time the server is loaded.

### Does the EcoCompute Should-I-Quantize Estimator MCP server require authentication?

No. We connected to EcoCompute Should-I-Quantize Estimator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the EcoCompute Should-I-Quantize Estimator MCP server still maintained?

EcoCompute Should-I-Quantize Estimator 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 did VerifyMCP test on the EcoCompute Should-I-Quantize Estimator MCP server?

VerifyMCP ran 11 checks on EcoCompute Should-I-Quantize Estimator, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about EcoCompute Should-I-Quantize Estimator: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp
- Repository: https://github.com/hongping-zh/quant-energy
- Website: https://quantenergy.tech/
- Changelog RSS feed: https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator.xml
- Changelog JSON feed: https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator.json
- HTML version of this page: https://verifymcp.io/servers/hongping-zh-ecocompute-estimator/ecocompute-estimator
