CBAM Data
REMOTE · CBAMDATA.EU
EU CBAM engine (Reg (EU) 2023/956): scope, default emissions, certificates and cost per CN code.
Available components
Last scanned (5 hours ago)
Scores higher than 70% of remote servers
Reachable. Last reached 24 Oct 2026.
Category Finance and Payments
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token. See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability74
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 631 tokens (~105/item across 6 items; 6 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management13
- Stability observed for 4 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
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 7 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
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.
- 24 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 23 Oct 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 22 Oct 26 +1
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 21 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Oct 26 75
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 24 Oct 2026 · Probed https://cbamdata.eu/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=cbamdata.eu | CN=YE2,O=Let's Encrypt,C=US | 15 Sept 2026 | 14 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 61275a90a9673ae681cabf2e7f98c550d5f |
| SANs: *.cbamdata.eu, cbamdata.eu | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| 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 cbamdata.eu. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| eu. | present | 35926 | 8 | Verified |
| cbamdata.eu. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://cbamdata.eu/mcp | Verified | 200 | |
| http (plaintext) | http://cbamdata.eu/mcp | HTTPS enforced | 301 | https://cbamdata.eu/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 →
cbam_certificate_price Get CBAM Certificate Price ~50
Get the latest published European Commission CBAM certificate price based on European Energy Exchange (EEX) EU ETS auction averages.
| Name | Type | Req | Description |
|---|---|---|---|
| all | boolean | – | Set true to retrieve the complete historical price series. |
No output schema declared.
No examples provided.
cbam_changes Get Dataset Change Feed ~74
Retrieve the CBAM Data dataset change feed tracking amendments and updates to Annex I scope and default emissions benchmarks.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Changes per page (default 50, max 200). |
| page | integer | – | Page number (default 1). |
| since | string | – | Filter changes since this dataset version. |
No output schema declared.
No examples provided.
cbam_defaults Lookup Default Values ~95
Search the European Commission default emission values dataset under Regulation (EU) 2025/2621 as corrected by Regulation (EU) 2026/1740 by CN code prefix, country of origin, or sector.
| Name | Type | Req | Description |
|---|---|---|---|
| cn | string | – | Filter by CN prefix (digits only). |
| origin | string | – | Two-letter ISO origin or ROW for rest-of-world fallback. |
| sector | string | – | CBAM sector. |
No output schema declared.
No examples provided.
cbam_resolve Calculate CBAM Obligations ~229
Calculate EU Carbon Border Adjustment Mechanism (Reg (EU) 2023/956) embedded direct and indirect emissions, the Art. 31 free allocation adjustment (CBAM factor times the Reg (EU) 2025/2620 CBAM benchmark), required CBAM certificates, and total euro cost for an imported product given CN code, country of origin, quantity in metric tonnes, and import year (2026-2034).
| Name | Type | Req | Description |
|---|---|---|---|
| carbonPricePaid | number | – | Optional verified carbon price effectively paid in the country of origin (EUR/tCO2e) under Art. 9. |
| cn | string | yes | Combined Nomenclature (CN) or TARIC code at 4, 6, 8, or 10 digits. |
| origin | string | yes | Two-letter ISO 3166-1 alpha-2 country of origin code (e.g. TR, CN, IN, US). |
| tonnes | number | yes | Net mass in metric tonnes (or MWh for electricity). |
| year | integer | yes | Import year (2026 to 2034). |
No output schema declared.
No examples provided.
cbam_scope Check Annex I Scope ~90
Check whether a Combined Nomenclature (CN) code falls within Annex I of Regulation (EU) 2023/956, and inspect sector coverage, direct/indirect rules, or child sub-headings.
| Name | Type | Req | Description |
|---|---|---|---|
| cn | string | yes | CN or TARIC code at 4, 6, 8, or 10 digits (e.g. 7208, 72083900). |
No output schema declared.
No examples provided.
cbam_status Check CBAM Data Status ~31
Retrieve the active CBAM dataset version, build date, total scope and default rows, and latest price period.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the CBAM Data MCP server?
CBAM Data is a hosted endpoint at https://cbamdata.eu/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 · cbamdata.eu
claude mcp add --transport http eu-cbamdata-cbam 'https://cbamdata.eu/mcp'
What is the CBAM Data MCP server?
CBAM Data is an MCP server listed in the public MCP registry as eu.cbamdata/cbam. EU CBAM engine (Reg (EU) 2023/956): scope, default emissions, certificates and cost per CN code. This page covers its hosted endpoint (https://cbamdata.eu/mcp).
Is the CBAM Data MCP server safe to use?
CBAM Data scores 76 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 CBAM Data MCP server expose?
CBAM Data exposes 6 tools: cbam_resolve, cbam_scope, cbam_certificate_price, cbam_defaults, cbam_changes, cbam_status. Their descriptions and schemas cost roughly 569 tokens of context every time the server is loaded.
Does the CBAM Data MCP server require authentication?
Yes. CBAM Data asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the CBAM Data MCP server still maintained?
CBAM Data is still listed as active in the MCP registry. We last reached this channel on 24 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.