Taiwan Carbon Open Data (Unofficial)
REMOTE · CARBON.TAUX.IO
Unofficial. Taiwan government emission factors for AI: electricity, fuels, refrigerants, inventory.
Available components
Last scanned (22 hours ago)
Scores higher than 65% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Health and Science
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
- No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 3443 tokens (~264/item across 13 items; 13 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 Management27
- Stability observed for 8 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 13 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 72
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 · Probed https://carbon.taux.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=taux.io | CN=WE1,O=Google Trust Services,C=US | 13 Nov 2026 | 11 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | b843fa3541ff1e4138cdd0accd2e589 |
| SANs: taux.io, carbon.taux.io, *.carbon.taux.io | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of carbon.taux.io. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| taux.io. | DS published | 2371 | 13 | Verified |
| carbon.taux.io. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://carbon.taux.io/mcp | Verified | 200 | |
| http (plaintext) | http://carbon.taux.io/mcp | HTTPS enforced | 301 | https://carbon.taux.io/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 →
build_inventory Build GHG inventory summary ~396
Calculate several activities and arrange the results as a greenhouse gas inventory: grouped into Scope 1 (direct), Scope 2 (purchased energy) and Scope 3 (other indirect), with a subtotal per scope, Scope 1 by gas, and a Scope 1+2 total. Subtotals and totals are withheld, with the reason, when items mix CO2 and CO2e, when an item could not be calculated, or when Scope 3 holds product carbon footprints that may overlap Scopes 1 and 2. The scope assignment is this service's default by factor type and can be overridden per item. Covers only the activities supplied; it is not a complete or verified inventory. 計算多筆活動並整理成溫室氣體盤查清冊的形式:分為範疇一(直接排放)、範疇二(能源間接)、範疇三(其他間接),提供各範疇小計、範疇一依氣體分列,以及範疇一加二的合計。項目混用 CO2 與 CO2e、有項目算不出來、或範疇三含可能與範疇一、二重疊的產品碳足跡時,不提供對應的小計或合計並說明原因。範疇分類是本服務依係數類型的預設,可逐筆覆寫。只涵蓋你提供的活動,不是完整或經查證的盤查。
| Name | Type | Req | Description |
|---|---|---|---|
| inventory_year | integer | – | 盤查年度(西元)。會套用到沒有自己指定 year 的項目,係數年度不符的項目會回報錯誤。 |
| items | array | yes | 要列入清冊的活動,最多 50 筆。 |
No output schema declared.
No examples provided.
calculate_batch Calculate batch ~229
Calculate several activities at once, each with its own factor and source. A total is given only when every item succeeded and the items share a gas basis and boundary type; otherwise the reason is stated. An item may be a refrigerant blend such as R-410A: pass refrigerant_blend with the user-supplied composition instead of factor_id; it stays one row in the results, and its components count toward the total. 批次計算多筆活動,逐筆回傳結果與來源。只有全部成功、氣體基礎與邊界類型一致時才提供合計,否則說明不提供的原因。混合冷媒(如 R-410A)的項目可不給 factor_id,改以 refrigerant_blend 提供使用者確認過的成分比例;結果仍是一筆一列,合計時以各成分計入。
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | 要計算的活動,最多 50 筆。每筆用 factor_id 或 refrigerant_blend 擇一。 |
No output schema declared.
No examples provided.
calculate_emissions Calculate emissions ~609
Calculate emissions for one activity: activity data × an official factor from the database. Checks units, the applicable year and whether the factor may be used for calculation, and returns the formula, kg and tonnes, the factor version and the source URL. Returns a clear error instead of guessing when the unit is incompatible, the year does not match or required data is missing (fuel factors need a user-supplied lower heating value; refrigerants need the basis of the quantity). A refrigerant blend such as R-410A can be calculated by passing refrigerant_blend with the user-supplied composition instead of factor_id. 計算單一活動的排放量:活動數據 × 資料庫中的官方係數。會檢查單位、適用年度與係數是否可用於計算,回傳公式、公斤與公噸、係數版本與來源網址。單位不相容、年度不符或缺少必要資料時(燃料係數需要使用者提供低位熱值,冷媒需要說明數量的依據)回傳明確錯誤,不會猜測。混合冷媒(如 R-410A)可不給 factor_id,改以 refrigerant_blend 提供使用者確認過的成分比例。
| Name | Type | Req | Description |
|---|---|---|---|
| factor_id | string | – | 係數 ID,來自 search_emission_factors 或 get_electricity_factor 的結果。請勿自行猜測。 |
| factor_version | integer | – | 指定係數版本,用來重現過去的計算。不給就用目前版本。混合冷媒(refrigerant_blend)不適用,給了會回錯誤。 |
| optional_context | object | – | 補充資料。燃料燃燒係數需要 lower_heating_value;冷媒等含氟氣體的逸散需要 refrigerant。 |
| quantity | number|string | yes | 活動數據,不小於零。可用數字或十進位字串(字串可避免精度問題),例如 12000 或 "17.495"。 |
| quantity_unit | string | yes | 活動數據的單位,例如 kWh、度、L、公秉、kg、t、m3。「度」在電是 kWh、在水是 m³。 |
| refrigerant_blend | object | – | 混合冷媒(例如 R-410A)。成分比例必須來自使用者或設備、冷媒的規格文件;本服務沒有內建任何冷媒的成分,請勿憑記憶填寫,不確定時請向使用者確認。 |
| year | integer | – | 活動發生的年度(西元)。有給就必須與係數的適用年度相符,不會自動以其他年度代替。 |
No output schema declared.
No examples provided.
check_factor_updates Check factor updates ~106
Show the sync status of each official source: when it was last checked, whether the data may be stale, and whether a difference from the official data is waiting for review. Read-only; it cannot trigger a sync or write anything. 查看各官方來源的同步狀態:最近檢查時間、資料是否可能過期、是否有與官方資料不一致而待審核的項目。唯讀,不能觸發同步或寫入。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
compare_emissions Compare emissions ~315
Compare two calculations (for example two years). Separates the effect of changed activity data from the effect of a changed factor, and flags when the calculation method differs so the difference is not read as an actual reduction. Either side may be a refrigerant blend such as R-410A (refrigerant_blend with the user-supplied composition instead of factor_id). Two blends with the same components are split component by component; blends with different components, or a blend against a single factor, get only the difference, because a blend has no official factor of its own. 比較兩筆計算(例如不同年度)。區分活動量改變與排放係數改變的影響;計算方法不同時會標示,避免把差異誤讀為實際減碳成效。兩邊都可以是混合冷媒(如 R-410A,以 refrigerant_blend 提供使用者確認過的成分比例,不給 factor_id)。成分相同的兩個混合冷媒逐成分拆解;成分不同,或單一係數對混合冷媒,只回差額,因為混合冷媒沒有官方公布的單一係數。
| Name | Type | Req | Description |
|---|---|---|---|
| baseline | object | yes | 基準(例如去年)。用 factor_id 或 refrigerant_blend 擇一。 |
| comparison | object | yes | 比較對象(例如今年)。用 factor_id 或 refrigerant_blend 擇一。 |
No output schema declared.
No examples provided.
get_electricity_factor Get electricity factor ~234
Get Taiwan's official electricity emission factor (kgCO2e/kWh) for a given year, published by the Energy Administration. From the 2025 factor year there are three values by usage; earlier years have one. Never substitutes another year: if the year is missing it says so and lists the years available. 查詢經濟部能源署公布的指定年度電力排碳係數(公斤CO2e/度)。114 年度(2025)起依用途有三個數值,之前每年一個。不會以其他年度代替:該年度沒有資料時會明說並列出可用年度。
| Name | Type | Req | Description |
|---|---|---|---|
| usage_type | string | – | 用途別(114 年度起才有劃分):industry_inventory 產業盤查使用;residential_tariff 表燈非營業與包燈用戶;utility_average 公用售電業整體平均。不給就回該年度全部數值。 |
| year | integer | yes | 適用年度(西元),例如 2025。 |
No output schema declared.
No examples provided.
get_emission_factor Get emission factor ~150
Get one factor in full by ID: the original government record, unit, applicable year, boundary, official source, version, whether it can be used for calculation directly, and usage limits. Find the ID with search_emission_factors first. 依係數 ID 取得完整資訊:官方原始紀錄、單位、適用年度、計算邊界、官方來源、版本、是否可直接計算與使用限制。請先用 search_emission_factors 找到 ID。
| Name | Type | Req | Description |
|---|---|---|---|
| factor_id | string | yes | 係數 ID,來自 search_emission_factors。 |
| version | integer | – | 指定版本;不給就是目前版本。 |
No output schema declared.
No examples provided.
get_methodology Get methodology ~88
Explain the calculation methods, scope, data limits and official references. Read this before interpreting results or combining different kinds of factors. 說明計算方法、適用範圍、資料限制與官方依據。解讀結果或合併不同類型的係數之前請先閱讀。
| Name | Type | Req | Description |
|---|---|---|---|
| topic | string | – | 主題;不給就回全部。 |
No output schema declared.
No examples provided.
list_data_sources List data sources ~68
List the official Taiwan government sources behind this service, with dataset codes, URLs, licence, sync status and how many factors each holds. 列出本服務整合的官方資料來源:資料集代碼、網址、授權、同步狀態與係數數量。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_factor_versions List factor versions ~84
List every recorded version of one factor, newest first. Old versions are kept so past calculations can be reproduced. 列出指定係數的所有歷史版本(新的在前)。舊版本會保留,讓過去的計算可以重現。
| Name | Type | Req | Description |
|---|---|---|---|
| factor_id | string | yes | 係數 ID,來自 search_emission_factors。 |
No output schema declared.
No examples provided.
match_activity Match activity to candidate factors ~341
Map an activity or ledger-account description (for example an electricity bill, fleet fuel, or a plastic resin purchase) plus an optional unit to candidate official factors. Returns candidates with unit compatibility, applicability conditions and the questions the user must answer; it never picks one. Use this when the user's wording is not an official factor name, then confirm with the user before calling calculate_emissions. The term mapping is curated by this service, not official. 把活動或會計科目的描述(例如電費、公務車加油、塑膠原料採購)與單位對到候選的官方係數,回傳每筆的單位相容性、適用條件與需要使用者回答的問題;不會代為選定。使用者的說法不是官方係數名稱時用這個工具,並在呼叫 calculate_emissions 之前先向使用者確認。用詞對照是本服務整理的,不是官方資料。
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | yes | 活動或會計科目的描述,例如「10 月電費」「公務車加油」「塑膠原料採購」。 |
| limit | integer | – | 回傳的候選筆數,預設 10,上限 25。 |
| unit | string | – | 活動數據的單位,例如 kWh、度、L、kg。有給就會檢查每筆候選的單位是否相容。 |
| year | integer | – | 活動發生的年度(西元)。不給時,逐年公布的係數只列最新年度。 |
No output schema declared.
No examples provided.
ping Ping ~51
Check that the service is up. Returns status, service name, version and server time. 確認服務狀態,回傳狀態、服務名稱、版本與伺服器時間。
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
search_emission_factors Search emission factors ~461
Search official Taiwan emission factors by keyword, category, type, year or unit. Returns factor IDs to pass to get_emission_factor and calculate_emissions. Covers electricity, tap water, fuel combustion, refrigerants and other fluorinated gases (GWP values), and product carbon footprint factors; returns an explicit not-found message rather than a near match. Refrigerant blends such as R-410A are not listed: pass their components as refrigerant_blend to calculate_emissions, calculate_batch, compare_emissions or build_inventory. 以關鍵字、類別、類型、年度或單位搜尋台灣官方排放係數,回傳的係數 ID 可交給 get_emission_factor 與 calculate_emissions。目前收錄電力、自來水、燃料燃燒、冷媒等含氟氣體(溫暖化潛勢)與產品碳足跡;查不到會明確說明,不會給相近的替代品。R-410A 這類混合冷媒不在表內,請把成分以 refrigerant_blend 交給 calculate_emissions、calculate_batch、compare_emissions 或 build_inventory 計算。
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 類別:electricity 電力、water 自來水、fuel_combustion 燃料燃燒、refrigerant 冷媒等含氟氣體、product_footprint 產品碳足跡。 |
| factor_type | string | – | 係數類型,用來區分固定燃燒與移動燃燒等。 |
| limit | integer | – | 回傳筆數,預設 10,上限 50。 |
| offset | integer | – | 略過前幾筆(分頁用)。 |
| query | string | – | 關鍵字,繁體中文或英文,例如 電力、柴油、自來水、gasoline。多個關鍵字以空白分隔。 |
| unit | string | – | 係數分母的單位,例如 kWh、m3、TJ。 |
| year | integer | – | 適用年度(西元)。 |
No output schema declared.
No examples provided.
How do I install the Taiwan Carbon Open Data (Unofficial) MCP server?
Taiwan Carbon Open Data (Unofficial) is a hosted endpoint at https://carbon.taux.io/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 · carbon.taux.io
claude mcp add --transport http taux-io-carbon-mcp 'https://carbon.taux.io/mcp'
What is the Taiwan Carbon Open Data (Unofficial) MCP server?
Taiwan Carbon Open Data (Unofficial) is an MCP server listed in the public MCP registry as io.github.taux-io/carbon-mcp. Unofficial. Taiwan government emission factors for AI: electricity, fuels, refrigerants, inventory. This page covers its hosted endpoint (https://carbon.taux.io/mcp).
Is the Taiwan Carbon Open Data (Unofficial) MCP server safe to use?
Taiwan Carbon Open Data (Unofficial) 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 Taiwan Carbon Open Data (Unofficial) MCP server expose?
Taiwan Carbon Open Data (Unofficial) exposes 13 tools: ping, list_data_sources, search_emission_factors, match_activity, get_emission_factor, and 8 more. Their descriptions and schemas cost roughly 3,132 tokens of context every time the server is loaded.
Does the Taiwan Carbon Open Data (Unofficial) MCP server require authentication?
No. We connected to Taiwan Carbon Open Data (Unofficial) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Taiwan Carbon Open Data (Unofficial) MCP server still maintained?
Taiwan Carbon Open Data (Unofficial) 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 did VerifyMCP test on the Taiwan Carbon Open Data (Unofficial) MCP server?
VerifyMCP ran 13 checks on Taiwan Carbon Open Data (Unofficial), covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.