Wipo Pearl
NPM · @PIPEWORX/MCP-WIPO-PEARL · 2 COMPONENTS
WIPO Pearl MCP — scientific, technical and IP legal terminology database.
Available components
Last scanned (4 hours ago)
Scores higher than 72% of npm 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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wipo-pearl). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability62
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 678 tokens (~226/item across 3 items; 3 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 Management23
- Stability observed for 7 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
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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 +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.
- 3 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.
- 31 Oct 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.
- 29 Oct 26 79
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-wipo-pearl@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 | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-wipo-pearl |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-wipo-pearl/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561134076 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:2ce87c7a416530f405a32da158c8522418c5cff4cc1a68ca9985f6542346dbafabe7ac5ce81135ce0e699e8dd6e551b16735f1c334b32d5c3b8bc7a34 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
pearl_concept ~182
Retrieve the full WIPO Pearl database record for one concept_id (from pearl_search_terms): validated term equivalents grouped by language, each with a reliability rating, a defining context, a usage note, and its source. Example: pearl_concept({ concept_id: "8818607" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional. Pipeworx supplies a WIPO Business Partner Portal credential automatically. Pass your own as JSON: '{"client_id":"...","client_secret":"..."}' to use a dedicated subscription instead. |
| concept_id | string | yes | The record id returned by pearl_search_terms, e.g. "8818607". |
| lang_code | string | – | Optional: restrict the record to one ISO 639-1 language (AR, DE, EN, ES, FR, JA, KO, PT, RU, ZH). |
| Name | Type | Req | Description |
|---|---|---|---|
| concept_id | string | yes | – |
| found | boolean | yes | – |
| groups | array | yes | – |
| source | string | yes | – |
No examples provided.
pearl_search_terms ~372
Search WIPO Pearl for a scientific, technical, or IP legal term and get back matching concept records (concept id, the matched term text, subject field). Use `pearl_concept` on a returned concept_id to get the full record: validated equivalents in other languages, reliability rating, defining context and source. Example: pearl_search_terms({ term: "inter partes review", target_languages: ["FR", "JA"], subject_field: "LEGL" }).
| Name | Type | Req | Description |
|---|---|---|---|
| _apiKey | string | – | Optional. Pipeworx supplies a WIPO Business Partner Portal credential automatically. Pass your own as JSON: '{"client_id":"...","client_secret":"..."}' to use a dedicated subscription instead. |
| abbreviation | boolean | – | Search only for abbreviations. |
| exact_search | boolean | – | Match the search term exactly rather than fuzzily. |
| limit | number | – | Maximum concept records to return (default 10, max 50). |
| source_language | string | – | ISO 639-1 language the term itself is in: AR, DE, EN, ES, FR, JA, KO, PT, RU, ZH. Omit to search across all languages. |
| subject_field | string | – | Restrict to one WIPO Pearl subject-field code (see pearl_subject_fields for the full list), e.g. "LEGL", "CHEM", "ELEC". Omit to search every field. |
| target_languages | array | – | ISO 639-1 languages to return equivalents in (subset of AR, DE, EN, ES, FR, JA, KO, PT, RU, ZH). Omit for all available. |
| term | string | yes | The word or phrase to search for, e.g. "circuit" or "inter partes review". |
| Name | Type | Req | Description |
|---|---|---|---|
| hits | number|null | – | – |
| note | string|null | – | – |
| results | array | yes | – |
| returned | number | yes | – |
| source | string | yes | – |
| source_language | string|null | – | – |
| subject_field | string|null | – | – |
| target_languages | array | – | – |
| term | string | yes | – |
No examples provided.
pearl_subject_fields ~68
List the 29 WIPO Pearl subject-field codes (e.g. "LEGL" = Legal Matters, "CHEM" = Chemical & Materials Technology) and the 10 supported language codes, for use with pearl_search_terms' subject_field/source_language/target_languages arguments. No arguments.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| languages | array | yes | – |
| source | string | yes | – |
| subject_fields | array | yes | – |
No examples provided.
How do I install the Wipo Pearl MCP server?
Wipo Pearl runs locally as an npm package, launched with npx -y @pipeworx/mcp-wipo-pearl. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-wipo-pearl
claude mcp add pipeworx-io-wipo-pearl -- npx -y @pipeworx/mcp-wipo-pearl
What is the Wipo Pearl MCP server?
Wipo Pearl is an MCP server listed in the public MCP registry as io.github.pipeworx-io/wipo-pearl. WIPO Pearl MCP, scientific, technical and IP legal terminology database. This page covers its npm package (@pipeworx/mcp-wipo-pearl).
Is the Wipo Pearl MCP server safe to use?
Wipo Pearl scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 Wipo Pearl MCP server expose?
Wipo Pearl exposes 3 tools: pearl_search_terms, pearl_concept, pearl_subject_fields. Their descriptions and schemas cost roughly 622 tokens of context every time the server is loaded.
Is the Wipo Pearl MCP server still maintained?
Wipo Pearl 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 Wipo Pearl MCP server under?
Wipo Pearl declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.