Sootcase freight CO2e
REMOTE · SOOTCASE.ORG
Freight CO2e by road, rail, sea, inland waterway and air (GLEC, ISO 14083), every step shown
Available components
Last scanned (13 hours ago)
Scores higher than 63% of remote servers
Reachable. Last reached 23 Oct 2026.
Category Data and Analytics
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability72
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1631 tokens (~233/item across 7 items; 6 tools + 1 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 Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 96% 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.
- 23 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- “calculate_shipment” reworded the description of “container_load” cosmetic
- “calculate_shipment” reworded the description of “teu” cosmetic
- 22 Oct 26 71
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 23 Oct 2026 · Probed https://sootcase.org/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=sootcase.org | CN=YE1,O=Let's Encrypt,C=US | 22 Oct 2026 | 20 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5aabd1146c6f6e76a949d8808e8711a244a |
| SANs: sootcase.org | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of sootcase.org. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| org. | present | 26974 | 8 | Verified |
| sootcase.org. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | same-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://sootcase.org/mcp | Verified | 200 | |
| http (plaintext) | http://sootcase.org/mcp | HTTPS enforced | 308 | https://sootcase.org/mcp |
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_shipment Calculate a shipment's emissions ~372
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
| hubs | array | – | Hub stops (transhipment, storage); needs a dataset with hub factors. |
| id | string | – | Your reference for the shipment |
| legs | array | yes | The legs in order, from where the shipper hands the goods over to where the consignee receives them. |
| teu | number | – | Containers in TEU, instead of weight_kg; with teu_net_tonnes, or alone for GLEC's average of 10 t per TEU |
| teu_net_tonnes | number | – | With teu: net cargo tonnes per TEU (container tare is not added) |
| weight_kg | number | – | Cargo weight in kg (or give teu instead) |
No output schema declared.
No examples provided.
calculate_shipments Calculate many shipments ~168
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).
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| explain | boolean | – | Add the step-by-step calculation sheet of each shipment (up to 25) |
| shipments | array | yes | The shipments. Without an API key the public service takes up to 100 per call; with one, up to 10,000. |
No output schema declared.
No examples provided.
emissions_report Emissions report over many shipments ~289
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
| declare_iso | boolean | – | Add the ISO 14083:2023 conformity statement. Only when the user explicitly confirms that their data collection and boundaries conform. |
| organisation | string | – | Organisation the report is for |
| period_from | string | – | Start of the period covered, YYYY-MM-DD |
| period_to | string | – | End of the period covered, YYYY-MM-DD |
| reference | string | – | Where supporting information can be found |
| shipments | array | yes | 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 |
No output schema declared.
No examples provided.
find_places Find places ~174
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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"]… |
| limit | integer | – | Most results (default 10) |
| query | string | yes | Place name, UN/LOCODE (NLRTM) or IATA code (CPH) |
No output schema declared.
No examples provided.
get_methodology How Sootcase calculates ~75
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_vehicle_types List vehicle types and emission factors ~129
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.
| Name | Type | Req | Description |
|---|---|---|---|
| include_fuels | boolean | – | Also list fuels and their factors |
| mode | string | – | – |
| search | string | – | Only vehicle types whose id, alias or source contains this, e.g. "container" or "refrigerated" |
No output schema declared.
No examples provided.
How do I install the Sootcase freight CO2e MCP server?
Sootcase freight CO2e is a hosted endpoint at https://sootcase.org/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · sootcase.org
claude mcp add --transport http majidkabir-sootcase 'https://sootcase.org/mcp'
What is the Sootcase freight CO2e MCP server?
Sootcase freight CO2e is an MCP server listed in the public MCP registry as io.github.majidkabir/sootcase. Freight CO2e by road, rail, sea, inland waterway and air (GLEC, ISO 14083), every step shown. This page covers its hosted endpoint (https://sootcase.org/mcp).
Is the Sootcase freight CO2e MCP server safe to use?
Sootcase freight CO2e scores 72 out of 100 on VerifyMCP. 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 Sootcase freight CO2e MCP server expose?
Sootcase freight CO2e exposes 6 tools: calculate_shipment, calculate_shipments, emissions_report, find_places, list_vehicle_types, get_methodology. Their descriptions and schemas cost roughly 1,207 tokens of context every time the server is loaded.
Does the Sootcase freight CO2e MCP server require authentication?
No. We connected to Sootcase freight CO2e without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Sootcase freight CO2e MCP server still maintained?
Sootcase freight CO2e is still listed as active in the MCP registry. We last reached this channel on 23 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.