Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

tw.org.legaltech/taiwan-law

REMOTE · LEGALTECH.ORG.TW

Taiwan legal research MCP: 判決書、全國法規、釋字/憲判與立法歷程查詢,12 個工具,回應均附官方出處 URL。

Available components

−1 this week 76 Trust /100

Last scanned (12 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Education and Research

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability66
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 3445 tokens (~229/item across 15 items; 15 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 Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage95
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 85% 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 15 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 15 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
What we tested

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 15 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 →

Changelog

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
    • Tool “search_taiwan_judgments” rewrote its description, which is the text the model reads security
    • Schema quality: 169 → 229 ▼ functional
    • New tool “get_taiwan_judgment_relations” functional
    • “search_taiwan_judgments” added an optional parameter “cited_for” cosmetic
    • “search_taiwan_judgments” added an optional parameter “sort” cosmetic
  • 11 Nov 26 0
    • Stability: 0.97 → pass security
  • 10 Nov 26 0
    • Stability: pass → 0.97 functional
  • 6 Nov 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 5 Nov 26 0
    • Stability: 0.97 → pass security
  • 4 Nov 26 0
    • Stability: pass → 0.97 functional
  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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://legaltech.org.tw/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=legaltech.org.tw CN=WE1,O=Google Trust Services,C=US 8 Nov 2026 6 Feb 2027 ECDSA 256 ECDSA-SHA256 c7ff78e370c9ae6813fe4ee35d617464
SANs: legaltech.org.tw, *.legaltech.org.tw
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 insecure

Validation of legaltech.org.tw. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
tw. DS published 46902 13 Verified
org.tw. DS published 50029 13 Verified
legaltech.org.tw. No DS 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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://legaltech.org.tw/mcp Verified 200
http (plaintext) http://legaltech.org.tw/mcp HTTPS enforced 301 https://legaltech.org.tw/mcp
MCP tools · 15 exposed · ~3,445 tokens

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 →

Tool Tokens
analyze_legal_intent ~74

將使用者輸入初步分為案例事實、法律問題或引註研究,並標示領域、隱私風險與建議檢索詞。不做法律結論。

NameTypeReqDescription
textstringyes使用者的案例事實或法律問題

No output schema declared.

No examples provided.

get_moj_draft_announcements ~99

取得法務部主管法規系統的法規草案預告清單(含官方網址);可一併回傳近期法規訊息(修正條文、行政規則發布等)。涵蓋範圍限法務部。

NameTypeReqDescription
include_all_newsboolean–一併回傳近期所有法規訊息
limitinteger––

No output schema declared.

No examples provided.

get_taiwan_interpretation ~249

取得釋字(第 1-813 號)或憲判字(111 年起)內容,來自官方公告文書的本地快照,即時回應。預設回傳字號/日期/爭點/解釋文等精簡層;理由書與意見書需 opt-in:優先用 reasoning_keyword / opinions_keyword 取關鍵字片段(省 token),確有需要才用 include_* 取全文(超過 15000 字會截斷並警告)。

NameTypeReqDescription
case_idstringyes字號,例如:釋字第748號、釋字748、111年憲判字第1號、111憲判1
include_opinionsboolean–回傳意見書全文
include_reasoningboolean–回傳理由書全文
opinions_keywordstring–在意見書中搜尋關鍵字並回片段
reasoning_keywordstring–在理由書中搜尋關鍵字並回片段(優先於 include_reasoning)

No output schema declared.

No examples provided.

get_taiwan_interpretation_citations ~99

從釋字/憲判字理由書中抽取引用的其他釋字與憲判字字號(往前追溯),可附引用處前後 80 字片段。

NameTypeReqDescription
case_idstringyes字號,格式同 get_taiwan_interpretation
include_contextboolean–每個引用附上原文片段

No output schema declared.

No examples provided.

get_taiwan_judgment ~119

依司法院 JID 取得裁判全文與官方網址。回應得經至多 6 小時邊緣快取(cached/retrieved_at 標示);需最新狀態或裁判疑似已下架時,設 fresh=true 強制向官方重抓。

NameTypeReqDescription
freshboolean–略過邊緣快取,強制向司法院取得最新內容
jidstringyes司法院裁判書 JID

No output schema declared.

No examples provided.

get_taiwan_judgment_relations ~711

查詢台灣法院裁判之間的「被引用、引用、審級」關係(只含法院裁判,不含法條、釋字)。適用問題:這則判決被多少判決引用、下級法院還在不在用、上級審或下級審是哪一份、同一案件的歷審。 使用前先用 search_taiwan_judgments 取得 jid。若使用者給的是案號(如 110年度台上字第5660號),用 court、year_from、year_to、case_word、case_number 參數搜尋;有多筆時請使用者選擇或全部列出。不可自行組 jid。 一次最多 20 個 jid。include=summary 只回次數與最新被引用日;include=full 另回清單,最多 3 個 jid。 解讀規則: 1. citedByCount 是本站收錄判決中,寫出「法院名稱+案號」引用此判決的不同判決數(countScope=named_court_only)。它不代表見解被採納或推翻,不是權威分數,也不分爭點,所以不能直接當成某主題最常被引用的判決。次數含少量程序沿革描述,扣除快照後刪除的判決時也只做部分修正,屬近似值。 2. 最高法院引用自己的判決時多寫「本院」,不計入次數(約漏掉 85%)。本工具能看出下級法院是否仍在引用,不能看出最高法院本身是否仍在引用。 3. citedBy 清單只列最新 20 份(order=date_desc),shown 可能小於 count。 4. upperNote=final_court 表示終審法院沒有上級審;not_found_in_corpus_does_not_mean_no_appeal 表示本站沒收錄上級審,不代表未上訴。上級審的裁判結果請用 get_taiwan_judgment 查主文。 5. status:ok;deleted=已撤回;missing=無可用內容;not_in_corpus=本站未收錄,請告知資料涵蓋期間 corpus.monthsFrom 至 monthsThrough;invalid=格式錯誤。 6. coverage:in_snapshot=有資料;no_relations=已收錄,但快照時沒有任何具名關係,可說截至 snapshot.builtAt 為 0;newer_than_snapshot=判決比引用快照新,無法判斷,不可說成 0。 7. versionSubstituted=true 表示指定版本不存在,已改用同案的現行版本。 回答時請附 url 讓使用者查證,並註明資料日期 snapshot.builtAt。

NameTypeReqDescription
includestring–summary:只回次數。full:另回清單,最多 3 個 jid。只傳 1 個 jid 時預設為 full
jidsarrayyessearch_taiwan_judgments 回傳的 jid,例如 TPSM,110,台上,5660,20220427,1

No output schema declared.

No examples provided.

get_taiwan_law_progress ~170

查立法院開放資料平台(data.ly.gov.tw 官方直連)取得法律的立法歷程:該法所有修法提案的提案人、連署人、議案狀態與官方關係文書(PDF/DOC)連結。補「修法沿革」上游的立法過程(誰提案、審到哪裡)。資料授權:政府資料開放授權條款第 1 版(與 CC-BY-4.0 相容)。

NameTypeReqDescription
lawstringyes法律名稱(如:勞動基準法)
max_billsinteger–回傳提案數上限(依最近會議日期排序)

No output schema declared.

No examples provided.

get_taiwan_law_versions ~145

查立法院開放資料平台(官方直連)取得法律的三讀通過紀錄與附帶決議:三讀屆會次、三讀通過條文 PDF、附帶決議內容。涵蓋近年(2023 起)三讀紀錄;完整修正沿革請併用 search_taiwan_laws 查全國法規資料庫。資料授權:政府資料開放授權條款第 1 版。

NameTypeReqDescription
lawstringyes法律名稱(如:道路交通管理處罰條例)
limitinteger––

No output schema declared.

No examples provided.

get_taiwan_pcode ~83

將法規名稱(含常見簡稱如勞基法、個資法)轉換為全國法規資料庫 pcode 代碼,支援模糊比對與建議。

NameTypeReqDescription
law_namestringyes法規名稱,例如:民法、勞基法、消保法

No output schema declared.

No examples provided.

search_moj_interpretations ~143

在法務部主管法規查詢系統(mojlaw.moj.gov.tw)以關鍵字搜尋行政函釋、法規諮詢意見、法律問題座談等文書,回傳發文字號、日期、要旨與官方網址。涵蓋範圍限法務部主管文書;即時查詢、不保存副本。

NameTypeReqDescription
doc_typesarray–文書類型(可多選)
keywordstringyes關鍵字(例:消滅時效、借名登記)
limitinteger––

No output schema declared.

No examples provided.

search_taiwan_bills ~193

搜尋立法院議案提案(官方直連 data.ly.gov.tw):以提案名稱關鍵字、提案人、屆期、議案狀態查詢。回傳議案編號、名稱、提案單位、提案人與連署人、議案狀態與官方關係文書 PDF/DOC 連結。資料授權:政府資料開放授權條款第 1 版。

NameTypeReqDescription
bill_statusstring–議案狀態(例:交付審查、三讀)
keywordstring–關鍵字(例:勞動基準法、最低工資)
limitinteger––
proposerstring–提案人姓名
terminteger–屆期(例:11)

No output schema declared.

No examples provided.

search_taiwan_interpretations ~238

列舉或全文搜尋釋字與憲判字(搜標題、爭點/案由與理由書全文)。每筆結果帶 case_id,可直接傳給 get_taiwan_interpretation。

NameTypeReqDescription
deepboolean–同時全文搜尋理由書(較慢);預設僅搜字號/標題/爭點索引
include_newboolean–包含新制憲判字
include_oldboolean–包含舊制釋字
keywordstring–關鍵字(標題/字號/爭點/理由書全文匹配),例如:集會自由
max_resultsinteger––
number_frominteger–起始號次(含),0=不篩選
number_tointeger–截止號次(含),0=不篩選
yearinteger–篩選民國年度(僅憲判字),0=不篩選

No output schema declared.

No examples provided.

search_taiwan_judgments ~753

使用司法院開放資料自建裁判庫搜尋。排序用 sort:court(預設,法院層級最高→高等→地方,再依日期新到舊)、relevance(關鍵詞相關度)、cited(在相關度最高的前 5000 筆中依被引用次數排序,每筆附 cited_by_count)。cited_by_count 為 named_court_only 總數,不分爭點,最高法院以「本院」自引者不計入,不能直接當成某爭點最常被引用的判決;要找有影響力的判決時,用 cited 篩出候選,再以 get_taiwan_judgment_relations 與全文確認被引用的原因。要找「為某爭點被引用最多」的判決,加 cited_for(例:「對價關係 賄賂|職務」;空白=且、|=或,每詞 2–20 字,自動 sort=cited),每筆附 issue_cited_count 與引用原文 issue_examples;只計候選池內判決,次數是引用頻率,不代表見解仍有效或為多數說。每筆含法院、案件類型、日期、案由。查特定案號請用 case_word + case_number(例:114年度上易字第503號 → case_word=上易, case_number=503, year_from=114),不要放進 query。main_text 以裁判主文措辭篩選輸贏方(例:「被告應給付」= 被告敗訴、「原告之訴駁回」= 原告敗訴、「上訴駁回」= 維持原審),可與 query 併用。若同時使用語意/概念式檢索工具,建議兩軌並行後以司法院 JID 合併去重,JID 皆命中者優先;沒有 JID 的候選結果僅供瀏覽,不得直接引為法院見解。query 的關鍵詞以空白分隔、全部同時符合(且);不支援 & + - 括號等布林語法,需要「或」時請分次查詢。

NameTypeReqDescription
case_numberstring–案號數字
case_typestring––
case_wordstring–字別,例如:台上、上易、重訴
cited_forstring–依爭點排序(選用):其他判決引用此判決時談的爭點,例「對價關係 賄賂|職務」;空白=且、|=或;會自動 sort=cited
courtstring–法院名稱,例如:最高法院、臺灣臺北地方法院
limitinteger––
main_textstring–裁判主文關鍵字(輸贏方篩選)
querystring–全文檢索關鍵字,例如:預售屋 遲延交屋
sortstring–排序:court(預設)、relevance、cited(依被引用次數)
year_frominteger–起始年度(民國年)
year_tointeger–截止年度(民國年)

No output schema declared.

No examples provided.

search_taiwan_laws ~244

即時查詢法務部全國法規資料庫,回傳官方網址與相關條文。可附修法沿革。回答時必須附上 source_url,並提醒使用者核對最新版本。與其他法規檢索途徑併用時,請以 pcode/法律編號合併去重;無官方識別碼的候選結果不得作為引用依據。

NameTypeReqDescription
article_numberstring–可選條號,例如 19 或 247-1
freshboolean–略過邊緣快取,強制向官方資料庫取得最新內容(例如剛公布的修正條文)
include_historyboolean–附上修法沿革(歷次公布/修正紀錄,來自本地官方資料快照)
limitinteger––
querystringyes法規名稱或法律爭點,例如:個人資料保護法 蒐集。支援常見簡稱(勞基法、個資法…)

No output schema declared.

No examples provided.

search_taiwan_regulations ~125

在 11,700+ 部法規(法律+命令)名稱中做關鍵字搜尋,回傳法規名稱、pcode 與現行/已廢止狀態。離線資料快照,即時回應。

NameTypeReqDescription
exclude_abolishedboolean–排除已廢止法規
keywordstringyes搜尋關鍵字,例如:勞動、消費、智慧財產
offsetinteger–分頁偏移,每頁 50 筆

No output schema declared.

No examples provided.

Install

How do I install the tw.org.legaltech/taiwan-law MCP server?

tw.org.legaltech/taiwan-law is a hosted endpoint at https://legaltech.org.tw/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 · legaltech.org.tw

# add to Claude Code
claude mcp add --transport http tw-org-legaltech-taiwan-law 'https://legaltech.org.tw/mcp'
Common questions

What is the tw.org.legaltech/taiwan-law MCP server?

tw.org.legaltech/taiwan-law is an MCP server listed in the public MCP registry as tw.org.legaltech/taiwan-law. Taiwan legal research MCP: 判決書、全國法規、釋字/憲判與立法歷程查詢,12 個工具,回應均附官方出處 URL。 This page covers its hosted endpoint (https://legaltech.org.tw/mcp).

Is the tw.org.legaltech/taiwan-law MCP server safe to use?

tw.org.legaltech/taiwan-law 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 tw.org.legaltech/taiwan-law MCP server expose?

tw.org.legaltech/taiwan-law exposes 15 tools: analyze_legal_intent, search_taiwan_laws, search_taiwan_judgments, get_taiwan_judgment, search_taiwan_regulations, and 10 more. Their descriptions and schemas cost roughly 3,445 tokens of context every time the server is loaded.

Does the tw.org.legaltech/taiwan-law MCP server require authentication?

No. We connected to tw.org.legaltech/taiwan-law without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the tw.org.legaltech/taiwan-law MCP server still maintained?

tw.org.legaltech/taiwan-law 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 tw.org.legaltech/taiwan-law MCP server?

VerifyMCP ran 12 checks on tw.org.legaltech/taiwan-law, 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 tw.org.legaltech/taiwan-law: 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.