Taiwan Road Safety Data (Unofficial)
REMOTE · ROADSAFETY.TAUX.IO
Unofficial. Taiwan road crash hotspots, school-zone crashes and speed-camera points (roadsafety.tw).
Available components
Last scanned (13 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Maps and Location
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 Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- 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 Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 3893 tokens (~204/item across 19 items; 19 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 Coverage99
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 98% 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 19 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
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 19 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
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.
- 20 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 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.
- 15 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 66
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://roadsafety.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 | 6 Nov 2026 | 4 Feb 2027 | ECDSA 256 | ECDSA-SHA256 | cfb8c344535d1e9d0eb668ae107ffa51 |
| SANs: taux.io, roadsafety.taux.io, *.roadsafety.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 roadsafety.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 |
| roadsafety.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://roadsafety.taux.io/mcp | Verified | 200 | |
| http (plaintext) | http://roadsafety.taux.io/mcp | HTTPS enforced | 301 | https://roadsafety.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 →
get_cbi_hotspots ~135
查詢指定縣市(可再限定鄉鎮)的肇事熱點排名,資料來自交通部道安總動員
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | ALL 或「縣市|鄉鎮」,例如 屏東縣|恆春鎮 |
| city | string | yes | 縣市名稱,例如 屏東縣 |
| metric | string | – | 排名依據 |
| month | string | – | ALL 或 01–12 |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_county_drunk_enforcement ~265
查詢某年各縣市(22 縣市加署所屬機關)的酒駕舉發件數(cases,酒精濃度超過規定標準者)與毒駕舉發件數(drugCases,吸食毒品迷幻藥麻醉品及其相類似之管制藥品者,資料集 39362);這些是行政舉發件數,不是事故件數,反映執法強度而非酒駕或毒駕發生率,不可與道安總動員或警政署統計查詢網的數字互比;毒駕舉發的 114 年數字與交通部草案說明差 616、與 113 年差 4.9 倍,原因不明,限制說明有寫;毒駕事故(傷亡事故層)請用 get_period_comparison 的 吸食違禁物駕駛 分類;目前只有 114 年,內建離線資料,不連上游
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | yes | 民國年,目前只有 114 |
No output schema declared.
No examples provided.
get_crosswalk_setback_count ~164
查詢首頁「行人穿越道退縮完成數」分頁各縣市的目前數量(current,照網站圖例用語),不加單位、不算合計也不判斷縣市好壞(網站沒有標示單位與統計口徑);上游給 null 的縣市(如連江縣)輸出 null 並在 notes 說明,不代表 0;刻意不公開上游圖例稱「與上月比較」的欄位(最新月份小於實際月增量,口徑不明);統計年月由網站決定,輸出的 dataPeriod 是請求用的年月
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_hotspot_detail ~97
查詢單一肇事熱點的肇因與碰撞類型分布;hotspotKeyid 與 kind 取自 get_cbi_hotspots 的結果
| Name | Type | Req | Description |
|---|---|---|---|
| hotspotKeyid | string | yes | 熱點代碼,取自 get_cbi_hotspots 的 hotspotKeyid |
| kind | string | yes | 熱點類型,取自 get_cbi_hotspots 的 kind |
No output schema declared.
No examples provided.
get_improvement_progress ~176
查詢首頁六個改善進度分頁(路口行人安全設施、人行道、減少路側障礙物、校園周邊、行人早開時相、行人專用時相)各縣市的預期改善數與實際完成數,照網站用語,不加單位也不計算完成率(網站沒有標示單位);統計年月由網站決定、各主題不同,輸出的 dataPeriod 附網站的「統計至」說明;校園周邊的說明與請求月份可能不一致,會在 notes 說明
| Name | Type | Req | Description |
|---|---|---|---|
| subject | string | yes | 網站分頁名稱;校園周邊沒有「改善進度」字尾 |
No output schema declared.
No examples provided.
get_location_accident_points ~169
查詢單一路口或路段某年度的事故位置,相同座標合併成「座標+件數」(件數多的在前);座標可能高度重複(同一路口可能落在同一點),不要當成逐案精確位置;只支援全年(不能指定月份);locationKeyid 與 kind 取自 get_cbi_hotspots 的結果
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | 熱點類型,取自 get_cbi_hotspots 的 kind |
| locationKeyid | string | yes | 地點代碼,取自 get_cbi_hotspots 的 locationKeyid(不是 hotspotKeyid) |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_location_history ~107
查詢單一路口或路段歷年(106 年起)的事故件數、死亡與受傷人數趨勢;locationKeyid 與 kind 取自 get_cbi_hotspots 的結果
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | 熱點類型,取自 get_cbi_hotspots 的 kind |
| locationKeyid | string | yes | 地點代碼,取自 get_cbi_hotspots 的 locationKeyid(不是 hotspotKeyid) |
No output schema declared.
No examples provided.
get_location_npa_cases ~164
查詢屏東縣 17 個路口某年(107–114 年)半徑 30 公尺內的警政署事故案件彙總;這是推算,未經人工標註,不是道安總動員的件數;locationKeyid 取自 get_cbi_hotspots 的結果,不在涵蓋範圍、沒有中心或 30 公尺內沒有案件時會說明,不代表 0 件或沒有事故
| Name | Type | Req | Description |
|---|---|---|---|
| locationKeyid | string | yes | 地點代碼,取自 get_cbi_hotspots 的 locationKeyid(不是 hotspotKeyid) |
| year | integer | yes | 民國年,107 到 114,例如 114 |
No output schema declared.
No examples provided.
get_location_overview ~163
一次查詢單一路口或路段的概況:熱點的肇因與碰撞類型分布、地點歷年(106 年起)件數趨勢、某年度的事故位置;只給 year 與 get_cbi_hotspots 同一列的 rowRef(已包含 kind、熱點代碼與地點代碼,不會配錯);事故位置的限制同 get_location_accident_points
| Name | Type | Req | Description |
|---|---|---|---|
| rowRef | string | yes | 列參照,取自 get_cbi_hotspots 同一列的 rowRef;已包含 kind、熱點代碼與地點代碼 |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_location_trend ~342
查詢單一路口或路段的歷年(106 年起)件數趨勢,以及指定年度(最多 5 個,省略時為上游已發布的最近 3 年)的肇因與碰撞類型;逐年說明哪些年度因未進入熱點排名而沒有肇因資料(不代表沒有事故);歷年資料的最後一年是初估值,不能單憑件數升降判斷改善成效;kind 與 locationKeyid 取自 get_cbi_hotspots 的結果,city、area 與 metric 用來掃描各年排名
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | ALL 或「縣市|鄉鎮」,例如 屏東縣|恆春鎮;用來縮小掃描排名的範圍 |
| city | string | yes | 縣市名稱,例如 屏東縣 |
| kind | string | yes | 熱點類型,取自 get_cbi_hotspots 的 kind |
| locationKeyid | string | yes | 地點代碼,取自 get_cbi_hotspots 的 locationKeyid(不是 hotspotKeyid) |
| metric | string | – | 掃描各年熱點排名用的指標;路口只進其他指標排名的年度,換指標才找得到 |
| years | array | – | 要查肇因的民國年度,1–5 個、106 起到今年、不可重複;省略時查上游已發布的最近 3 個年度 |
No output schema declared.
No examples provided.
get_period_comparison ~881
查詢縣市(或全國)某年某月累計的交通事故死傷人數,並與上游提供的比較期間(預設去年同期)比較;回傳事故總件數與指定指標(headline:事故總件數,加 30日死亡/事故受傷/事故死傷),以及依年齡、用路人、肇因等分類的 breakdown;metric 選「全部」時對死亡、受傷、死傷各查一次(3 個上游請求),輸出改依指標分組(byMetric)。酒駕、毒駕問題請用本工具。breakdown 的分類名稱(受傷、死傷版本把「死亡」換成「受傷」「死傷」):兒童(0-12歲)、少年(13-17歲)、年輕人(18-24歲)、成年人(25-64歲)、高齡者(65歲以上)、少年無照機車騎士(含大重機)、高齡者事故無照駕駛、年輕人機車騎士(含大重機)、高齡者機車騎士(含大重機)、高齡者機車騎士(含大重機)自撞、機車騎士(含大重機)自撞、高齡者行人(含代步)、高齡者使用電動代步器(含輪椅)、行人、自小客駕駛人、自行車騎士(含電自、電輔)、機車騎士(含大重機)、少年自行車騎士(含電自、電輔)、微型電動二輪車(含電輔)、大型車案件導致死亡、平交道事故總件數、平交道事故導致死亡、行人路口事故、高齡者路口事故、高齡者路段事故、大型車造成行人涉入(含代步)、大型車造成機車涉入(含大重機)、大型車造成自行車涉入(含電自、電輔)、動力機械案件導致死亡、營業用小客車案件導致死亡、追撞事故死亡人數、酒駕案件導致死亡、吸食違禁物駕駛導致死亡、外籍人士。肇因類(追撞、酒駕、毒駕)也在其中。毒駕(吸食違禁物駕駛):統計自 115 年起,115 年 7 月起定義改為納入第二當事人,所以 1–6 月與 7 月起的數字不能相加(起算年與定義變更由專案維護者提供,未核對官方公告);比較期間早於 115 年時 previous 為 null、note 為「未統計」,不是沒有發生;涵蓋月份未知。category 選填,只回傳名稱包含該字串的分類(例如 吸食違禁物駕駛),此時 headline 為空;沒帶時行為不變
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | 選填;只回傳名稱包含這個字串的分類,例如 吸食違禁物駕駛(毒駕)、酒駕;headline 會是空的;沒帶時回傳全部分類 |
| city | string | yes | 縣市名稱(如 屏東縣),或 全國、國道、其他 |
| compareWith | string | – | 比較的基準 |
| metric | string | – | 死亡人數是事故發生後 30 日內死亡;全部=死亡、受傷、死傷三組一次回 |
| month | string | yes | 累計到幾月,01–12(例如 07 表示 1–7 月累計) |
| year | integer | yes | 民國年,例如 115 |
No output schema declared.
No examples provided.
get_school_accident_points ~159
查詢學校周邊一定半徑內某年度的事故位置,相同座標合併成「座標+件數」(件數多的在前);座標高度重複(與 AccPoints 相同的行為),不要當成逐案精確位置;schoolKeyid 取自 list_schools 或 get_school_rank
| Name | Type | Req | Description |
|---|---|---|---|
| radius | – | yes | 半徑(公尺):100、150、200、500、1000 |
| schoolKeyid | string | yes | 學校代碼,取自 list_schools 或 get_school_rank 的 schoolKeyid |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_school_hotspots ~146
查詢學校周邊一定半徑內的事故熱點,依分類(地點、好發時段、年齡、車種、碰撞類型、肇因、歷年統計)分組;schoolKeyid 取自 list_schools 或 get_school_rank
| Name | Type | Req | Description |
|---|---|---|---|
| radius | – | yes | 半徑(公尺):100、150、200、500、1000 |
| schoolKeyid | string | yes | 學校代碼,取自 list_schools 或 get_school_rank 的 schoolKeyid |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_school_rank ~154
查詢指定年度、縣市(可再限定鄉鎮)與類型中,上游列出的排名前列學校(順序看起來是排名,但排名指標上游未公開,也不是完整排名),結果可接 get_school_hotspots
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | ALL 或「縣市|鄉鎮」,例如 屏東縣|屏東市;可用 list_areas 查詢 |
| city | string | yes | 縣市名稱,例如 屏東縣 |
| schoolType | string | yes | 學校類型 |
| year | integer | yes | 民國年,106 起到今年,例如 114 |
No output schema declared.
No examples provided.
get_township_drunk_ranking ~184
查詢某縣市某年各鄉鎮的酒駕事故件數與死傷,回該縣市完整的鄉鎮列表(依死傷、案件、鄉鎮名稱排序);city 不填為屏東縣;口徑是警政署的肇因研判,不是道安總動員的數字,不可互比或推算占全縣市比例,也沒有跨縣市排名;目前只有 114 年,內建離線資料,不連上游
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | 縣市名稱,22 縣市之一(寫法可用 list_areas 查),不填為屏東縣 |
| year | integer | yes | 民國年,目前只有 114 |
No output schema declared.
No examples provided.
list_areas ~75
列出可查詢的縣市與鄉鎮,供 get_cbi_hotspots 的 city、area 參數使用
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | 指定縣市時列出該縣市的鄉鎮;不填則列出所有縣市 |
No output schema declared.
No examples provided.
list_schools ~112
列出指定縣市(可再限定鄉鎮)與類型的學校,供 get_school_hotspots 的 schoolKeyid 使用
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | ALL 或「縣市|鄉鎮」,例如 屏東縣|屏東市;可用 list_areas 查詢 |
| city | string | yes | 縣市名稱,例如 屏東縣 |
| schoolType | string | yes | 學校類型 |
No output schema declared.
No examples provided.
list_speed_enforcement_points ~366
列出某縣市(或「國道」)的測速執法設置點:地址、座標、拍攝方向與速限,可用 area 再指定鄉鎮;資料來自警政署「測速執法設置點」資料集,內建離線、不連上游;資料集沒有區分固定式與移動式,也不是事故資料,不能用來判斷哪裡較危險或測速是否有效;資料集沒有連江縣的列(回空清單並說明,不代表沒有測速);少數座標明顯錯誤的列標 coordinateSuspect: true(座標原樣輸出,請勿用來定位,沒標記不代表座標正確);彰化縣、南投縣、嘉義縣、桃園市的列另併入縣資料集的「取締項目」(enforcement,原字串,座標配對不到為 null;其他縣市沒有,enforcementCoverage 標明,null 不代表沒有取締);附固定限制、免責與授權出處標示
| Name | Type | Req | Description |
|---|---|---|---|
| area | string | – | 鄉鎮名稱,須與資料集的寫法相同(例如 屏東市;查不到時 notes 會列出有列的鄉鎮);city 為「國道」時不可帶 |
| city | string | yes | 22 縣市之一(寫法可用 list_areas 查),或「國道」(國道公路警察局負責的設置點) |
No output schema declared.
No examples provided.
ping ~34
確認 roadsafety MCP server 是否運作中,原樣回傳訊息
| Name | Type | Req | Description |
|---|---|---|---|
| message | string | – | – |
No output schema declared.
No examples provided.
How do I install the Taiwan Road Safety Data (Unofficial) MCP server?
Taiwan Road Safety Data (Unofficial) is a hosted endpoint at https://roadsafety.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 · roadsafety.taux.io
claude mcp add --transport http foxhsiao-roadsafety-mcp 'https://roadsafety.taux.io/mcp'
What is the Taiwan Road Safety Data (Unofficial) MCP server?
Taiwan Road Safety Data (Unofficial) is an MCP server listed in the public MCP registry as io.github.foxhsiao/roadsafety-mcp. Unofficial. Taiwan road crash hotspots, school-zone crashes and speed-camera points (roadsafety.tw). This page covers its hosted endpoint (https://roadsafety.taux.io/mcp).
Is the Taiwan Road Safety Data (Unofficial) MCP server safe to use?
Taiwan Road Safety Data (Unofficial) scores 69 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 Road Safety Data (Unofficial) MCP server expose?
Taiwan Road Safety Data (Unofficial) exposes 19 tools: ping, get_cbi_hotspots, get_hotspot_detail, get_location_history, get_location_accident_points, and 14 more. Their descriptions and schemas cost roughly 3,893 tokens of context every time the server is loaded.
Does the Taiwan Road Safety Data (Unofficial) MCP server require authentication?
No. We connected to Taiwan Road Safety Data (Unofficial) without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Taiwan Road Safety Data (Unofficial) MCP server still maintained?
Taiwan Road Safety 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 Road Safety Data (Unofficial) MCP server?
VerifyMCP ran 12 checks on Taiwan Road Safety Data (Unofficial), covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Taiwan Road Safety Data (Unofficial): Authorization. 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.