com.greencalculus/api

Est-ce que com.greencalculus/api est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.greencalculus/api » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 12 outils

• calculate_activity≈ 176 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • activity · object · requis
    { "value": <number>, "unit": "<unit e.g. kWh, MWh, litres, tonne, km>" }.
  • factor_key · string · requis
    Canonical emission-factor key.

  Exemple d'appel

  {"name": "calculate_activity", "arguments": {"activity": {}, "factor_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_business_travel≈ 160 tokens

  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").

  Paramètres, retour & exemple (3)

  Paramètres

  • distance · object · requis
    { "value": <number>, "unit": "km|mi" }.
  • factor_key · string · requis
    Per-passenger-km travel factor key.
  • passengers · number · optionnel
    Optional, defaults to 1.

  Exemple d'appel

  {"name": "calculate_business_travel", "arguments": {"distance": {}, "factor_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_electricity≈ 236 tokens

  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").

  Paramètres, retour & exemple (4)

  Paramètres

  • consumption · object · requis
    { "value": <number>, "unit": "kWh|MWh|GWh" }.
  • supplier_factor · object · optionnel
    Optional contractual factor { value, unit } (wins over market_factor_key).
  • market_factor_key · string · optionnel
    Optional: residual-mix / supplier grid factor key.
  • location_factor_key · string · requis
    Grid-average factor key, e.g. grid.gbr.electricity.location_based.

  Exemple d'appel

  {"name": "calculate_electricity", "arguments": {"consumption": {}, "location_factor_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_embodied≈ 168 tokens

  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").

  Paramètres, retour & exemple (1)

  Paramètres

  • materials · array · requis
    Each: { material_key, quantity:{value,unit e.g. m3/kg/tonne/m2}, boundary? }.

  Exemple d'appel

  {"name": "calculate_embodied", "arguments": {"materials": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_freight≈ 332 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • teu · object · optionnel
    { "value": <number> } — container slots. Required for a per-TEU-km factor; omit for a per-tonne-km one.
  • mass · object · optionnel
    { "value": <number>, "unit": "tonne|kg|lb" }. Required for a per-tonne-km factor; omit for a per-TEU-km one.
  • distance · object · requis
    { "value": <number>, "unit": "km|mi|nmi" }.
  • factor_key · string · requis
    Freight factor key. Its unit says whether to send mass (per tonne-km) or teu (per TEU-km).

  Exemple d'appel

  {"name": "calculate_freight", "arguments": {"distance": {}, "factor_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_pcaf≈ 164 tokens

  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).

  Paramètres, retour & exemple (2)

  Paramètres

  • holdings · array · requis
    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? }.
  • asset_class · string · optionnel

  Exemple d'appel

  {"name": "calculate_pcaf", "arguments": {"holdings": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• calculate_spend≈ 152 tokens

  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.

  Paramètres, retour & exemple (2)

  Paramètres

  • spend · object · requis
    { "value": <number>, "currency": "USD|GBP|EUR|SGD" }.
  • factor_key · string · requis
    Spend-based (EEIO) sector factor key.

  Exemple d'appel

  {"name": "calculate_spend", "arguments": {"spend": {}, "factor_key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• explain_absence≈ 339 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • family · string · optionnel
    Inventory family, e.g. "water", "wtt", "travel", "spend", "heat".
  • country · string · optionnel
    ISO-3166 alpha-3 code, e.g. "can".
  • classification · string · optionnel
    Filter: structural | not_yet_sourced | refused | held_not_counted | coupled.

  Exemple d'appel

  {"name": "explain_absence", "arguments": {"family": "texte", "country": "texte", "classification": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_factor≈ 192 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • key · string · requis
    Canonical factor key, e.g. "grid.gbr.electricity.location_based".

  Exemple d'appel

  {"name": "lookup_factor", "arguments": {"key": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• lookup_factors≈ 187 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • keys · array · requis
    Canonical factor keys, e.g. ["grid.gbr.electricity.location_based", "grid.fra.electricity.location_based"]. Maximum 25 per call.

  Exemple d'appel

  {"name": "lookup_factors", "arguments": {"keys": []}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• resolve_factor≈ 579 tokens

  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.

  Paramètres, retour & exemple (3)

  Paramètres

  • limit · number · optionnel
    Optional, default 5.
  • section · string · optionnel
    Optional section filter, e.g. "fuels", "grid", "freight".
  • description · string · requis
    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.

  Exemple d'appel

  {"name": "resolve_factor", "arguments": {"description": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• search_factors≈ 208 tokens

  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.

  Paramètres, retour & exemple (4)

  Paramètres

  • limit · number · optionnel
    Max results (default 20).
  • query · string · optionnel
    Free-text search over factor names/keys.
  • section · string · optionnel
    Restrict to a section, e.g. "grid", "fuels", "freight".
  • key_prefix · string · optionnel
    Restrict to keys starting with this prefix.

  Exemple d'appel

  {"name": "search_factors", "arguments": {"limit": 1, "query": "texte", "section": "texte", "key_prefix": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.greencalculus.com