mcpbeat Sign in

Greencalculus MCP Server

by greencalculus Your server? Claim it
answering

Greencalculus is answering right now. Last checked 10 min ago. It exposes 12 tools.

Sourced carbon emission factors + audit-traced calculations an AI can cite.

Uptime history 20 days of history
20 days agonow
100.0%
Uptime 24h
91 of 91 checks
12
Tools
read from the server
130 ms
Response time
average over 24h
open, no key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Greencalculus every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 10 min ago.

run in your terminal
claude mcp add api --transport http https://mcp.greencalculus.com
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "api": {
      "url": "https://mcp.greencalculus.com"
    }
  }
}
~/.codex/config.toml
[mcp_servers.api]
url = "https://mcp.greencalculus.com"
.cursor/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://mcp.greencalculus.com"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "api": {
      "url": "https://mcp.greencalculus.com"
    }
  }
}

Available tools 12

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

calculate
calculate_activity
Turn activity data into greenhouse-gas emissions: emissions = activity × factor. Give an amount + unit and a factor key; the unit engine converts to the factor basis (MWh→kWh, tonne→kg, gallon→litre, mile→km) and returns the emissions with the working, the GHG Protocol scope, and the source. Use search_factors / lookup_factor to find the factor key.
calculate_business_travel
Business travel emissions (Scope 3 Cat 6), distance method: emissions = km × passengers × factor. Air factors come in with_rf / without_rf (radiative forcing) variants. Find factors via search_factors (section "business_travel").
calculate_electricity
GHG Protocol Scope 2 for purchased electricity, both methods. Always returns location-based (grid-average) emissions; also returns market-based when you supply a contractual supplier_factor (e.g. a green tariff / REC = 0) or a market_factor_key (residual mix). Find grid keys via search_factors (section "grid").
calculate_embodied
Whole-life embodied carbon for materials, per EN 15978. Give a material key + quantity (+ optional boundary A1-A3 / A1-A4 / A1-A5 / A1-C); it assembles the declared lifecycle modules (A1-A3, B, C1-C4, D) into stages, totals the boundary, reports module D separately, and flags any missing stage as not-assessed (never zero). Find material keys via search_factors (section "materials").
calculate_freight
Freight & logistics emissions (Scope 3 Cat 4 & 9), GLEC tonne-km method: emissions = tonnes × km × factor. Find mode factors via search_factors (section "freight" or "freight_detailed"), e.g. freight.road_hgv.tonne_km.
calculate_pcaf
Compute PCAF Part A financed emissions for a portfolio. Returns each holding's attribution factor and financed emissions, the portfolio total, the outstanding-weighted data-quality score, and the audit trail (formula + PCAF source).
calculate_spend
Spend-based (EEIO) Scope 3 screening: emissions = spend × economic-intensity factor. Spend must be in the factor's own currency/year (no FX). Find sector factors via search_factors (section "spend_based"), e.g. spend_based.us.naics6.541511.custom_computer_programming_services.
lookup
lookup_factor
Look up a single greenhouse-gas emission factor by its canonical key. Returns the value plus an audit envelope: provenance (publisher, exact source cell, retrieval date, LICENCE and whether it may be redistributed, with the attribution the licence requires) and verification (whether the per-gas components sum to the headline, the GWP set, and the source note stating what the publisher did NOT provide). If the key does not exist you get candidate keys back rather than a dead end. Use search_factors first if you do not know the key.
lookup_factors
Look up SEVERAL emission factors by key in one call, each with the same audit envelope lookup_factor returns — provenance (publisher, exact source cell, retrieval date, licence, redistribution) and verification. Use this instead of calling lookup_factor in a loop: a portfolio or a multi-country comparison is one call, not one per factor. Keys that do not exist come back in `not_found` rather than failing the batch.
explain
explain_absence
Ask why a factor is NOT in the corpus. The reasoned counterpart to coverage: where a country reports zero rows for an inventory family, this says whether that is the world's limit or our backlog. Five classifications: "structural" (no publisher issues this anywhere — stop looking, and do not silently substitute another country), "not_yet_sourced" (a publisher exists and is named; it is our backlog), "refused" (we found it and declined — the reason is stated), "held_not_counted" (we DO hold it — see we_hold for the key), "coupled" (empty only because another family is empty). Each record names the publisher checked, the route tried, a confidence and a review date, and reports stale:true once past review. These are authored judgements about what the world publishes, not values derived from our data. Call this before concluding that a gap is permanent, and before telling a user to look elsewhere.
factors
search_factors
Find emission factors by section, key prefix, or free text. Returns each match with its key, name, section, VALUE, unit and gas — enough to choose between them or read a few numbers without a second call. For one factor's full audit envelope (publisher, exact source cell, retrieval date, licence, verification) call lookup_factor; for several, call lookup_factors.
resolve
resolve_factor
Find the best emission-factor key(s) for a plain-language description — the hardest step is picking the right key out of ~16,000. Returns ranked candidates; feed the chosen key to a calculate_* tool or lookup_factor. Prefer this over guessing a key. PUT THE COUNTRY IN THE DESCRIPTION. Geography is read from the description text itself, not from a separate field — "diesel per litre" and "diesel per litre France" resolve differently, and omitting the country will quietly return a factor from somewhere else marked "geo_match":"proxy". ACT ON THE LABEL. Every candidate carries label: "accept" or "review", plus "why". "accept" means confidence >= 0.85 and no demotion applied — right about nine times in ten. "review" means the answer may be usable but something is off (low confidence, only one term matched, a proxy country, or a gate demoted it); confirm it before adopting the number rather than using it silently. Roughly half of CORRECT answers are also flagged "review" — that is the intended trade, so treat "review" as "check this", not "discard this". A MISS MAY EXPLAIN ITSELF. When nothing matches, or the only matches are from the wrong country, the response may carry an "absence" object saying WHY. classification "structural" means no publisher issues this anywhere — STOP, do not retry with reworded queries and do not substitute a different country without saying so. "not_yet_sourced" means a publisher exists and we have not ingested it (the publisher is named). "refused" means we found the data and declined it, with the reason. "coupled" means this reads empty only because a related family is empty. Use explain_absence to ask the same question directly.

Endpoints

URLTransportStateLatencyChecked
https://mcp.greencalculus.com streamable-http answering 117 ms 10 min ago

Alternatives to Greencalculus

same job, measured the same way
Legend Saju
by sihyeonjeon

Source-traceable Saju, Zi Wei, Qimen, Daliuren, Tieban, naming, and related calculations

13 tools answering
Agent Observability
by kryptosai

Trace AI agent execution: every tool call, every error, every dollar. Open source, local-first.

90 installs/wk local only
Hypathesis
by predme

Variable relationships from research papers with causal direction and source traceback.

4 tools answering
Modelforge
by whatsonyourmind

Bulge-tier financial model factory — live formulas, source-traced cells, 14 templates.

126 installs/wk local only
Chron
by sirinivask

Timestamped audit log for every AI conversation — stored locally in SQLite, owned by you.

286 installs/wk local only
Scholar Feed
by ygao2005

Rank CS/AI/ML papers by citations, forecast impact, or code adoption; trace 23.2M citation edges.

370 installs/wk local only
Trace Forge
by mdfifty50-boop

Structured execution trace and span logging for AI agents

49 installs/wk local only
Agentsnap
by mukundakatta

Snapshot tests for AI tool-call traces: diff, validate, and catch silent regressions.

72 installs/wk local only

Greencalculus — questions

Answers built from our own checks of this server.

What can Greencalculus do?
It exposes 12 tools, read directly from the server on our last check. Among them: calculate_activity, calculate_business_travel, calculate_electricity, calculate_embodied, calculate_freight, calculate_pcaf and 6 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is Greencalculus mostly used for?
Its tools cluster around calculate and lookup. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is Greencalculus working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 130 ms. The bar chart above shows every period we have measured.
How do I connect Greencalculus?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Greencalculus need an API key?
No. Greencalculus completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 12 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Greencalculus?
It answers our handshake in 130 ms on average, which is faster than 85% of all working MCP servers we measure. That puts it in the quick quarter of the ecosystem. The comparison comes from our own checks across the whole registry, every 15 minutes.