io.github.CloudCorpRecords/carboncalc
NPM · @RENETURCIOS/CARBONCALC · 2 COMPONENTS
Sourced emission factors and carbon calculations: activity, freight, spend, travel, PCAF.
Available components
Last scanned (19 hours ago)
Scores higher than 39% of npm servers
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 11 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2328 tokens (~194/item across 12 items; 12 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 97% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Checks we ran (15)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: not enough scan history yet (needs a 30-day window).
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 11 Nov 26 +15
- Malware scan: unverified → pass ▲ security
- Security disclosure: unverified → fail ▼ functional
- 10 Nov 26 53
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Analysed npm/@reneturcios/carboncalc@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
calculate_activity ~140
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.
| Name | Type | Req | Description |
|---|---|---|---|
| activity | object | yes | { "value": <number>, "unit": "<unit e.g. kWh, MWh, litres, tonne, km>" }. |
| factor_key | string | yes | Canonical emission-factor key. |
No output schema declared.
No examples provided.
calculate_business_travel ~113
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").
| Name | Type | Req | Description |
|---|---|---|---|
| distance | object | yes | { "value": <number>, "unit": "km|mi" }. |
| factor_key | string | yes | Per-passenger-km travel factor key. |
| passengers | number | – | Optional, defaults to 1. |
No output schema declared.
No examples provided.
calculate_electricity ~173
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").
| Name | Type | Req | Description |
|---|---|---|---|
| consumption | object | yes | { "value": <number>, "unit": "kWh|MWh|GWh" }. |
| location_factor_key | string | yes | Grid-average factor key, e.g. grid.gbr.electricity.location_based. |
| market_factor_key | string | – | Optional: residual-mix / supplier grid factor key. |
| supplier_factor | object | – | Optional contractual factor { value, unit } (wins over market_factor_key). |
No output schema declared.
No examples provided.
calculate_embodied ~142
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").
| Name | Type | Req | Description |
|---|---|---|---|
| materials | array | yes | Each: { material_key, quantity:{value,unit e.g. m3/kg/tonne/m2}, boundary? }. |
No output schema declared.
No examples provided.
calculate_freight ~332
Freight & logistics emissions (Scope 3 Cat 4 & 9), GLEC framework. THE FACTOR'S DENOMINATOR PICKS THE METHOD — check the factor's unit before choosing the input. Per tonne-km: emissions = tonnes × km × factor, send "mass". Per TEU-km (the sea-container family, e.g. freight_detailed.sea.container.trans_suez.dry): emissions = TEU × km × factor, send "teu" — a TEU is a twenty-foot container slot, not a mass, and a forty-foot box is 2 TEU. Sending mass against a per-TEU-km factor is refused (422), not converted. Find mode factors via search_factors (section "freight" or "freight_detailed"), e.g. freight.road_hgv.tonne_km.
| Name | Type | Req | Description |
|---|---|---|---|
| distance | object | yes | { "value": <number>, "unit": "km|mi|nmi" }. |
| factor_key | string | yes | Freight factor key. Its unit says whether to send mass (per tonne-km) or teu (per TEU-km). |
| mass | object | – | { "value": <number>, "unit": "tonne|kg|lb" }. Required for a per-tonne-km factor; omit for a per-TEU-km one. |
| teu | object | – | { "value": <number> } — container slots. Required for a per-TEU-km factor; omit for a per-tonne-km one. |
No output schema declared.
No examples provided.
calculate_pcaf ~117
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).
| Name | Type | Req | Description |
|---|---|---|---|
| asset_class | string | – | – |
| holdings | array | yes | Each: { outstanding_amount, denominator:{type:"evic"|"equity_plus_debt", value}, company_emissions:{value,unit?} OR estimate_from_spend:{amount_usd, sector_key}, data_quality_score? }. |
No output schema declared.
No examples provided.
calculate_spend ~121
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.
| Name | Type | Req | Description |
|---|---|---|---|
| factor_key | string | yes | Spend-based (EEIO) sector factor key. |
| spend | object | yes | { "value": <number>, "currency": "USD|GBP|EUR|SGD" }. |
No output schema declared.
No examples provided.
explain_absence ~280
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.
| Name | Type | Req | Description |
|---|---|---|---|
| classification | string | – | Filter: structural | not_yet_sourced | refused | held_not_counted | coupled. |
| country | string | – | ISO-3166 alpha-3 code, e.g. "can". |
| family | string | – | Inventory family, e.g. "water", "wtt", "travel", "spend", "heat". |
No output schema declared.
No examples provided.
lookup_factor ~142
Look up a single greenhouse-gas emission factor by its canonical key. Returns the value plus an audit envelope: provenance (publisher, exact source reference, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| key | string | yes | Canonical factor key, e.g. "grid.gbr.electricity.location_based". |
No output schema declared.
No examples provided.
lookup_factors ~135
Look up SEVERAL emission factors by key in one call, each with the same audit envelope lookup_factor returns — provenance (publisher, exact source reference, 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.
| Name | Type | Req | Description |
|---|---|---|---|
| keys | array | yes | Canonical factor keys, e.g. ["grid.gbr.electricity.location_based", "grid.fra.electricity.location_based"]. Maximum 25 per call. |
No output schema declared.
No examples provided.
resolve_factor ~476
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 matches, each carrying the key, value, unit and a confidence score; 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.
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | What you need a factor for, INCLUDING the country if it matters, e.g. "UK grid electricity", "diesel per litre France", "hotel stay Japan". Geography is parsed from this string. |
| limit | number | – | Optional, default 5. |
| section | string | – | Optional section filter, e.g. "fuels", "grid", "freight". |
No output schema declared.
No examples provided.
search_factors ~157
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 reference, retrieval date, licence, verification) call lookup_factor; for several, call lookup_factors.
| Name | Type | Req | Description |
|---|---|---|---|
| key_prefix | string | – | Restrict to keys starting with this prefix. |
| limit | number | – | Max results (default 20). |
| query | string | – | Free-text search over factor names/keys. |
| section | string | – | Restrict to a section, e.g. "grid", "fuels", "freight". |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/carboncalc MCP server?
io.github.CloudCorpRecords/carboncalc runs locally as an npm package, launched with npx -y @reneturcios/carboncalc mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/carboncalc
claude mcp add cloudcorprecords-carboncalc -- npx -y @reneturcios/carboncalc mcp
What is the io.github.CloudCorpRecords/carboncalc MCP server?
io.github.CloudCorpRecords/carboncalc is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/carboncalc. Sourced emission factors and carbon calculations: activity, freight, spend, travel, PCAF. This page covers its npm package (@reneturcios/carboncalc).
Is the io.github.CloudCorpRecords/carboncalc MCP server safe to use?
io.github.CloudCorpRecords/carboncalc scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/carboncalc MCP server expose?
io.github.CloudCorpRecords/carboncalc exposes 12 tools: lookup_factor, search_factors, lookup_factors, calculate_activity, calculate_embodied, and 7 more. Their descriptions and schemas cost roughly 2,328 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/carboncalc MCP server still maintained?
io.github.CloudCorpRecords/carboncalc 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 licence is the io.github.CloudCorpRecords/carboncalc MCP server under?
io.github.CloudCorpRecords/carboncalc declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.
What did VerifyMCP test on the io.github.CloudCorpRecords/carboncalc MCP server?
VerifyMCP ran 15 checks on io.github.CloudCorpRecords/carboncalc, covering Malware scan, Known CVEs, Install scripts, Dependency health and 11 more. One item could not be completed, a gap on our side rather than a finding about io.github.CloudCorpRecords/carboncalc: Stability. One category scores 0 for that reason, because we only credit what we can confirm. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.