Carbonara freight CO2e

Measured conclusion: Deep-tested. L2 outcome: tools_ok.

Freight CO2e by road, rail, sea, inland waterway and air (GLEC, ISO 14083), every step shown

Add to your agent

Copy this into your MCP client config:

{
  "mcpServers": {
    "Carbonara freight CO2e": {
      "url": "https://carbonara-co2.org/mcp",
      "transport": "streamable-http"
    }
  }
}

Measured tools (8)

• calculate_shipment read-only

  Calculates one shipment's greenhouse gas emissions (kg CO2e: well-to-wheel, tank-to-wheel, well-to-tank) following the GLEC Framework v3.2 and ISO 14083. Routes each leg's distance from its coordinates or codes. Returns the result per leg (distance and how it was found, method, data type, emission factor and its source, distance adjustment, notes on legs Sootcase added) and a step-by-step calculation sheet with the arithmetic and the GLEC page and ISO 14083 clause behind each step.

  Parameters:

  • legs (required) — array — The legs in order, from where the shipper hands the goods over to where the consignee receives them.
  • id — string — Your reference for the shipment
  • teu — number — Containers in TEU, instead of weight_kg; with teu_net_tonnes, or alone for GLEC's average of 10 t per TEU
  • hubs — array — Hub stops (transhipment, storage); needs a dataset with hub factors.
  • weight_kg — number — Cargo weight in kg (or give teu instead)
  • add_road_legs — boolean — Add road legs where the legs don't join up (gaps over 5 km), and to a port or terminal when a sea, rail or river leg starts or ends off its network (default true). Added legs are marked in the result.
  • container_load — string — With teu, instead of teu_net_tonnes: average (10 t), light (6 t) or heavy (14.5 t) per TEU, from the GLEC Framework
  • teu_net_tonnes — number — With teu: net cargo tonnes per TEU (container tare is not added)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• calculate_shipments read-only

  Calculates several shipments at once, each like calculate_shipment. A failing shipment doesn't stop the others; each failure says why and whether sending it again can help. Set explain to add calculation sheets (first 25 shipments).

  Parameters:

  • shipments (required) — array — The shipments. Without an API key the public service takes up to 100 per call; with one, up to 10,000.
  • explain — boolean — Add the step-by-step calculation sheet of each shipment (up to 25)
  • add_road_legs — boolean — Add road legs where the legs don't join up (gaps over 5 km), and to a port or terminal when a sea, rail or river leg starts or ends off its network (default true). Added legs are marked in the result.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• emissions_report read-only

  Calculates shipments and returns a report with the basic content ISO 14083 asks for at the level of transport services (GLEC v3.2 Section 2 Ch.1): coverage and failures, totals split into TTW and WTT, intensity, per mode and hub type, energy carriers, data quality (primary/modelled/default shares, sources, models), distance adjustments, and notes. Returned as Markdown and as structured data.

  Parameters:

  • shipments (required) — array — The shipments. Without an API key the public service takes up to 100 per call; with one, up to 10,000.
  • title — string — Report title
  • period_to — string — End of the period covered, YYYY-MM-DD
  • reference — string — Where supporting information can be found
  • declare_iso — boolean — Add the ISO 14083:2023 conformity statement. Only when the user explicitly confirms that their data collection and boundaries conform.
  • period_from — string — Start of the period covered, YYYY-MM-DD
  • organisation — string — Organisation the report is for
  • add_road_legs — boolean — Add road legs where the legs don't join up (gaps over 5 km), and to a port or terminal when a sea, rail or river leg starts or ends off its network (default true). Added legs are marked in the result.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• compare_scenario read-only

  Calculates the shipments as they are and with changes, with the same method (GLEC v3.2, ISO 14083), and returns both totals (TTW, WTT, WTW), the difference, per change how many shipments and legs it affected and the sources of its values, and per shipment notes. Changes: road_to_rail (defaults: road legs over 300 km, 30% of the cargo, from the EU Transport White Paper 2011; rail part over 100 km in a straight line, from Directive 92/106/EEC), electrify (needs the user's kwh_per_tkm, a grid country and the source), fuel_switch (hvo, b100, biomethane, biomethane_lng, cng, lng for diesel trucks), load. Results are scenarios, not reported emissions: say so to the user.

  Parameters:

  • shipments (required) — array — The shipments. Without an API key the public service takes up to 100 per call; with one, up to 10,000.
  • plan (required) — object
  • add_road_legs — boolean — Add road legs where the legs don't join up (gaps over 5 km), and to a port or terminal when a sea, rail or river leg starts or ends off its network (default true). Added legs are marked in the result.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• recommend_routes read-only

  For each shipment, tries road legs on rail, inland waterway and short sea, air legs by sea or rail, other sea ports and (when a load is given) fuller loads; calculates each alternative with the same method as the shipment (GLEC v3.2, ISO 14083) and returns those lower than now, best first, with totals per kind and per lane, the sources of the rules and the limitations. Rules (defaults, settable): road legs over 300 km (EU Transport White Paper 2011); rail, waterway or sea part over 100 km in a straight line, road to a waterway or sea port within 150 km, nearest rail terminal (Directive 92/106/EEC). It knows nothing about transit times, costs or whether a service runs: tell the user, and that results are scenarios, not reported emissions. The website's Recommendations page (/recommend) lets the user filter and pick interactively.

  Parameters:

  • shipments (required) — array — The shipments. Without an API key the public service takes up to 100 per call; with one, up to 10,000.
  • settings — object

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• find_places read-only

  Finds cities, sea and inland ports, rail and road terminals, inland depots, border crossings and airports by name, UN/LOCODE or IATA code, with coordinates, from an embedded list (GeoNames, UN/LOCODE, OurAirports). Use it to fill a leg's from and to.

  Parameters:

  • query (required) — string — Place name, UN/LOCODE (NLRTM) or IATA code (CPH)
  • kinds — array — Only places of these kinds: port (sea or inland port), rail and road (terminals), airport, inland (inland clearance depot), border (crossing), city. E.g. ["port"] for a sea or river leg, ["airport"] for an air leg
  • limit — integer — Most results (default 10)

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• list_vehicle_types read-only

  Lists the vehicle types (and their short aliases) with their emission factors: g CO2e per tonne-km tank-to-wheel and well-to-tank, the distance type they are per, source and year, and for trucks the load model's payload (what load_factor 1 means). Optionally the fuels for the fuel method.

  Parameters:

  • mode — string
  • search — string — Only vehicle types whose id, alias or source contains this, e.g. "container" or "refrigerated"
  • include_fuels — boolean — Also list fuels and their factors

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

• get_methodology read-only

  Explains the whole method: scope (WTW, TTW, WTT), inputs, the four calculation methods with formulas, how distances are routed, distance adjustment factors, added road legs, the emission factor datasets and their sources and limitations, data quality, what every result field means, errors, and how to present results.

  Hints: read-only yes · destructive not declared · idempotent yes · open-world no

Publisher website

Measured by MCPYP probing. Untested fields are omitted, never estimated. Listing is always free; MCPYP never proxies calls or stores user tokens.