mcp-registry/tw.org.legaltech/taiwan-law · v0.3.0
Also listed as mcp-registry/io.github.hirosichen/taiwan-law-mcp · primary listing: mcp-registry/io.github.hirosichen/taiwan-law-mcp
As of 2026-10-26 17:40 UTC, the Org Legaltech Taiwan Law MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Taiwan legal research MCP: 判決書、全國法規、釋字/憲判與立法歷程查詢,12 個工具,回應均附官方出處 URL。
Point your MCP client at this streamable-http endpoint: https://legaltech.org.tw/mcp
14 of 14 tool(s) carry no readOnlyHint/destructiveHint annotations.
Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →
8 parameter(s) across 7 tool(s) have no description.
Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →
No tool declares an outputSchema.
Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →
Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 7 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law/fixes
{
"name": "analyze_legal_intent",
"description": "將使用者輸入初步分為案例事實、法律問題或引註研究,並標示領域、隱私風險與建議檢索詞。不做法律結論。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"text"
],
"properties": {
"text": {
"type": "string",
"maxLength": 12000,
"minLength": 3,
"description": "使用者的案例事實或法律問題"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "分析台灣法律研究意圖"
}{
"name": "get_moj_draft_announcements",
"description": "取得法務部主管法規系統的法規草案預告清單(含官方網址);可一併回傳近期法規訊息(修正條文、行政規則發布等)。涵蓋範圍限法務部。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"properties": {
"limit": {
"type": "integer",
"default": 15,
"maximum": 50,
"minimum": 1
},
"include_all_news": {
"type": "boolean",
"default": false,
"description": "一併回傳近期所有法規訊息"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "法務部草案預告與最新法規訊息"
}{
"name": "get_taiwan_interpretation",
"description": "取得釋字(第 1-813 號)或憲判字(111 年起)內容,來自官方公告文書的本地快照,即時回應。預設回傳字號/日期/爭點/解釋文等精簡層;理由書與意見書需 opt-in:優先用 reasoning_keyword / opinions_keyword 取關鍵字片段(省 token),確有需要才用 include_* 取全文(超過 15000 字會截斷並警告)。",
"inputSchema": {
"type": "object",
"$schema": "http://json-schema.org/draft-07/schema#",
"required": [
"case_id"
],
"properties": {
"case_id": {
"type": "string",
"maxLength": 40,
"minLength": 1,
"description": "字號,例如:釋字第748號、釋字748、111年憲判字第1號、111憲判1"
},
"include_opinions": {
"type": "boolean",
"default": false,
"description": "回傳意見書全文"
},
"opinions_keyword": {
"type": "string",
"default": "",
"maxLength": 40,
"description": "在意見書中搜尋關鍵字並回片段"
},
"include_reasoning": {
"type": "boolean",
"default": false,
"description": "回傳理由書全文"
},
"reasoning_keyword": {
"type": "string",
"default": "",
"maxLength": 40,
"description": "在理由書中搜尋關鍵字並回片段(優先於 include_reasoning)"
}
}
},
"annotations": {
"readOnlyHint": true
},
"title": "取得大法官解釋/憲法法庭裁判"
}Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:
curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/tw.org.legaltech/taiwan-law"],"email":"[email protected]"}'Agents: watch_tool({"toolId": "mcp-registry/tw.org.legaltech/taiwan-law"}) over MCP.
search_taiwan_judgments ~321 tokenssearch_taiwan_interpretations ~271 tokensget_taiwan_interpretation ~234 tokenssearch_taiwan_laws ~205 tokenssearch_taiwan_bills ~186 tokensStatic checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).
Operator? Fix these, then re-check live. Embed the readiness badge:
[](https://glimind.com/server/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law?ref=badge)
<a href="https://glimind.com/server/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law.svg" alt="MCP agent-readiness"></a>
.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law.svg :target: https://glimind.com/server/mcp-registry%2Ftw.org.legaltech%2Ftaiwan-law?ref=badge :alt: MCP agent-readiness
Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:ccc6faccbfe64c54…, first seen 2026-10-17, included at leaf 10171 of 74,486. Version history · verify what your client received.
Compare: most reliable other servers · most reliable retrieval servers · most reliable search servers
Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.
Claude Code
claude mcp add --transport http glimind https://glimind.com/mcp
Claude Desktop · Windsurf · Cline (mcpServers JSON)
{
"mcpServers": {
"glimind": {
"type": "http",
"url": "https://glimind.com/mcp"
}
}
}
As of 2026-10-26 17:40 UTC, the Org Legaltech Taiwan Law MCP server is up with a Glimind reliability score of 98/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.
Org Legaltech Taiwan Law MCP server advertises 14 tools, including analyze_legal_intent, get_moj_draft_announcements, get_taiwan_interpretation, get_taiwan_interpretation_citations, get_taiwan_judgment.
Point your MCP client at this streamable-http endpoint: https://legaltech.org.tw/mcp
Glimind scanned all 14 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.
Status page: 90-day uptime, every outage and how long it lasted.
Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.
Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.