Taiwan Patent MCP
PYPI · TW-PATENT-MCP
Patent search via Taiwan IPO GPSS and EPO OPS: legal status, families, full text, PDFs
Available components
Last scanned (5 hours ago)
Scores higher than 63% of PyPI servers
Category Education and Research
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security50
- Malware scan not yet available for this package.Unverified
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
- 1 of 32 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to aa0101181514/tw-patent-mcp). View diagnostics → Pass
- License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 14 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability60
- AI-judged instruction clarity (fair).Partial
- Context-footprint check failed: tool/resource definitions use about 1382 tokens (~115/item across 12 items; 12 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 Management53
- Stability observed for 16 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 13 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
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.
- 5 Nov 26 −14
- Malware scan: pass → unverified ▼ security
- 3 Nov 26 +16
- Malware scan: unverified → pass ▲ security
- 2 Nov 26 −15
- Malware scan: pass → unverified ▼ security
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.
- 29 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 27 Oct 26 +1
- Security disclosure: unverified → fail ▼ functional
- 26 Oct 26 0
- Security disclosure: fail → unverified ▼ functional
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 5 Nov 2026 · Analysed pypi/tw-patent-mcp@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | pypi |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | aa0101181514/tw-patent-mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/aa0101181514/tw-patent-mcp/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3353578121 |
| Predicate type | PyPI publish attestation https://docs.pypi.org/attestations/publish/v1 |
| Subject digest | sha256:96665f2c3a8fd6fb0102a183b44bd8bccfb60d6bd1e43e2aad07c1c6881a1241 |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 32 packages
| Packages resolved | 32 |
|---|---|
| No linked repository | 1 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
gpss_build_url ~83
只組出 GPSS API 網址不送出（驗證碼以 *** 取代），用來檢查條件寫法。
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | object | yes | – |
| databases | – | – | – |
| kind | – | – | – |
| output | – | – | – |
| qty | integer | – | – |
| skip | integer | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
gpss_codes ~38
列出 GPSS 資料庫代碼、檢索欄位代碼與輸出欄位代碼。
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
gpss_get ~70
用公開/公告號（PN）或申請號（AN）取單筆 GPSS 資料，含摘要與請求項。例：number="TW201644272A"。
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | – |
| databases | – | – | – |
| number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
gpss_search ~207
智慧局 GPSS 檢索。conditions 是 {欄位代碼: 條件}，例如 {"TI/AB": "固態電池 or solid state battery", "AX": "台灣積體電路", "ID": "20200101:"}；欄位代碼前加 + 表示跨欄位 OR、加 - 表示 NOT。databases 例如 ["TWA","TWB"]，空＝全部 23 庫。status：A 公開／B 公告；kind：I 發明／M 新型／D 設計。output 預設 PN,ID,AN,AD,TI,PA,IN,IC,AB，要請求項加 CL。
| Name | Type | Req | Description |
|---|---|---|---|
| conditions | object | yes | – |
| databases | – | – | – |
| kind | – | – | – |
| output | – | – | – |
| qty | integer | – | – |
| skip | integer | – | – |
| status | – | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_biblio ~135
EPO OPS 書目資料（標題、申請人、發明人、優先權、IPC/CPC、引證、摘要、家族 id）。number 照公報號寫即可，例：EP1000000、TW201644272A、TWI700000B、TWM600000U、US10000000B2；程式自動轉成 docdb 格式。預設回壓平摘要，raw=true 回原始 JSON。
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | string | – | – |
| number | string | yes | – |
| raw | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_download_pdf ~168
下載 EPO OPS 影像 PDF。link 用 ops_images 回傳的 link（如 published-data/images/EP/1000000/A1/fullimage），pages 如 '1-5' 或 'all'（需給 max_pages）。每頁一次呼叫並算入每週 4GB，先用 ops_images 看頁數再決定範圍。檔案存到 TW_PATENT_MCP_DOWNLOAD_DIR（預設 ~/.tw-patent-mcp/downloads），多頁自動合併。呼叫間隔依 OPS 節流燈號自動調整。
| Name | Type | Req | Description |
|---|---|---|---|
| link | string | yes | – |
| max_pages | integer | – | – |
| merge | boolean | – | – |
| pages | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_family ~89
EPO OPS INPADOC 專利家族成員（各國公開／公告號、申請號、優先權）；constituent 可為 biblio 或 legal。預設回壓平摘要，raw=true 回原始 JSON。
| Name | Type | Req | Description |
|---|---|---|---|
| constituent | – | – | – |
| fmt | string | – | – |
| number | string | yes | – |
| raw | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_fulltext ~59
EPO OPS 全文：part 為 claims、description 或 abstract。全文只有 EP、WO 與部分歐洲國家。
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | string | – | – |
| number | string | yes | – |
| part | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_images ~76
EPO OPS 影像清單：某件有哪些 PDF 文件（FullDocument 全件、Drawing 圖式、FirstPageClipping 首頁）與頁數。台灣、美國、歐洲等公報原件多數可取得。
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | string | – | – |
| number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_legal_status ~91
EPO OPS INPADOC 法律狀態（有效、撤回、屆期、年費等事件），依家族成員列出事件日期、代碼、說明與明細。預設回壓平摘要，raw=true 回原始 JSON。
| Name | Type | Req | Description |
|---|---|---|---|
| fmt | string | – | – |
| number | string | yes | – |
| raw | boolean | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_register ~59
歐洲專利註冊簿（EP 案）：constituent 為 biblio、events 或 procedural-steps。
| Name | Type | Req | Description |
|---|---|---|---|
| constituent | string | – | – |
| fmt | string | – | – |
| number | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
ops_search ~138
EPO OPS CQL 檢索（全球書目）。例：'ti=battery and pa=tsmc'、'pn=TW201644272'、'ipc=H01M10 and pd within "2022 2024"'。constituent 可為 biblio（含書目）或 abstract。一次最多 100 筆。預設回壓平的命中清單，raw=true 回原始 JSON。
| Name | Type | Req | Description |
|---|---|---|---|
| constituent | – | – | – |
| cql | string | yes | – |
| end | integer | – | – |
| raw | boolean | – | – |
| start | integer | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| result | string | yes | – |
No examples provided.
How do I install the Taiwan Patent MCP server?
Taiwan Patent MCP runs locally as a PyPI package, launched with uvx tw-patent-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · tw-patent-mcp
claude mcp add aa0101181514-tw-patent-mcp -- uvx tw-patent-mcp
What is the Taiwan Patent MCP server?
Taiwan Patent MCP is listed in the public MCP registry as io.github.aa0101181514/tw-patent-mcp. Patent search via Taiwan IPO GPSS and EPO OPS: legal status, families, full text, PDFs. This page covers its PyPI package (tw-patent-mcp).
Is the Taiwan Patent MCP server safe to use?
Taiwan Patent MCP scores 66 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. 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 Patent MCP server expose?
Taiwan Patent MCP exposes 12 tools: gpss_codes, gpss_search, gpss_get, gpss_build_url, ops_search, and 7 more. Their descriptions and schemas cost roughly 1,213 tokens of context every time the server is loaded.
Is the Taiwan Patent MCP server still maintained?
Taiwan Patent MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Taiwan Patent MCP server under?
Taiwan Patent MCP declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.