EcoCompute Should-I-Quantize Estimator MCP server
io.github.hongping-zh/ecocompute-estimatorhongping-zhstreamable-httpv1.0.0Scanned
Energy impact of LLM quantization, calibrated to measured GPU data. Every answer states its basis.
4 tools: 1 change things and 3 only read.
- Reads private data · 0
- Reads text others write · 0
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the EcoCompute Should-I-Quantize Estimator MCP server can do
The EcoCompute Should-I-Quantize Estimator MCP server is published by the GitHub account hongping-zh. It has 4 tools. It can create or change data (1 tool: estimate_quantization_energy), but cannot delete data. 3 tools only read.
None of its tools reads private data, brings in text other people write, or sends data out.
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 8, 2026, version 1.0.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
4 tools
Changes things 1Claude Code: ask
estimate_quantization_energyEstimate 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…No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
Description, as the server wrote it 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.
Only reads 3Show 3 read-only tools
get_quantization_crossoverGet the model-size crossover for NF4/INT8 per architecture: below it quantization costs energy, above it saves.No findings
Why it is in this group
- The name "get_quantization_crossover" says "get": a word for reading.
Description, as the server wrote it 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.
list_data_coverageList what is actually measured (GPU architecture × precision × size range, NVML direct), what is borrowed/estimated, and where the gaps are.No findings
Why it is in this group
- The name "list_data_coverage" says "list": a word for reading.
Description, as the server wrote it 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_measurementsSearch the measured anchors by model name, GPU name, architecture or size.No findings
Why it is in this group
- The name "search_measurements" says "search": a word for reading.
Description, as the server wrote it 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.
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or untrusted-input or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write0
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 15, 2026, 13:22 UTC, unchanged since Oct 24, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://ecocompute-estimator.zhanghongping1982.workers.dev/mcp: tools/list returned 4 tools to an anonymous client, including estimate_quantization_energy (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.0.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http ecocompute-estimator https://ecocompute-estimator.zhanghongping1982.workers.dev/mcpclaude mcp add --transport http ecocompute-estimator https://ecocompute-estimator.zhanghongping1982.workers.dev/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__ecocompute-estimator__get_quantization_crossover",
"mcp__ecocompute-estimator__list_data_coverage",
"mcp__ecocompute-estimator__search_measurements"
],
"ask": [
"mcp__ecocompute-estimator__estimate_quantization_energy"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as ecocompute-estimator. Review it before you use it.
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.hongping-zh/ecocompute-estimator/verify?hash=9f83ecf3183fc06bf1cf00d54a789995bb3fbda149c4712266fc013f65cf44e7" | jq -e '.changed == false'Pinned hash 9f83ecf3183f, from Nov 8, 2026, 23:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.hongping-zh/ecocompute-estimator/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.hongping-zh/ecocompute-estimator)Source: MCP Registry · repository. Synced Oct 24, 2026, 04:17 UTC.
EcoCompute Should-I-Quantize Estimator MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the EcoCompute Should-I-Quantize Estimator MCP server safe?
- No scan can promise that. What its definitions show: 4 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the EcoCompute Should-I-Quantize Estimator MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the EcoCompute Should-I-Quantize Estimator MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the EcoCompute Should-I-Quantize Estimator MCP server have?
- 4 tools: 1 write, 3 read. estimate_quantization_energy, get_quantization_crossover, list_data_coverage and search_measurements.
Does the EcoCompute Should-I-Quantize Estimator MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the EcoCompute Should-I-Quantize Estimator MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the EcoCompute Should-I-Quantize Estimator MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.