# Wipo Pearl (npm · @pipeworx/mcp-wipo-pearl)

WIPO Pearl MCP — scientific, technical and IP legal terminology database.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-wipo-pearl/wipo-pearl-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-wipo-pearl/wipo-pearl-mcp)
- npm · `@pipeworx/mcp-wipo-pearl`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl.md), [page](https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-wipo-pearl`
- Version: `0.2.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-wipo-pearl).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 62/100
  - AI-judged instruction clarity (good).
  - 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.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add pipeworx-io-wipo-pearl -- npx -y @pipeworx/mcp-wipo-pearl
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-wipo-pearl": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wipo-pearl"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-wipo-pearl": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wipo-pearl"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-wipo-pearl -- npx -y @pipeworx/mcp-wipo-pearl
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-wipo-pearl": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-wipo-pearl"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-wipo-pearl --command npx --arg -y --arg @pipeworx/mcp-wipo-pearl
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-wipo-pearl:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-wipo-pearl"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-wipo-pearl": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-wipo-pearl"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-wipo-pearl -t stdio -c npx -a -y @pipeworx/mcp-wipo-pearl
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-wipo-pearl": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-wipo-pearl"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 82, +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.

### 2026-11-03 (score 81, +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.

### 2026-10-31 (score 80, +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.

### 2026-10-29 (score 79)

First indexed and scored.

## MCP tools (3)

### `pearl_search_terms` (~372 tokens)

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" }).

Input parameters:

- `_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, required): The word or phrase to search for, e.g. "circuit" or "inter partes review".

Output parameters:

- `hits` (number|null)
- `note` (string|null)
- `results` (array)
- `returned` (number)
- `source` (string)
- `source_language` (string|null)
- `subject_field` (string|null)
- `target_languages` (array)
- `term` (string)

### `pearl_concept` (~182 tokens)

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" }).

Input parameters:

- `_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, required): 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).

Output parameters:

- `concept_id` (string)
- `found` (boolean)
- `groups` (array)
- `source` (string)

### `pearl_subject_fields` (~68 tokens)

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.

Output parameters:

- `languages` (array)
- `source` (string)
- `subject_fields` (array)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 80
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-wipo-pearl
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-wipo-pearl
- Repository: https://github.com/pipeworx-io/mcp-wipo-pearl
- Website: https://pipeworx.io/packs/wipo-pearl
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-wipo-pearl/pipeworx-mcp-wipo-pearl