# Jpo Patent Info (npm · @pipeworx/mcp-jpo-patent-info)

JPO patent information: Japanese patent, utility model and trademark status from the Japan Patent…

- Trust score: 83/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`: 79/100, [markdown](https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/jpo-patent-info-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/jpo-patent-info-mcp)
- npm · `@pipeworx/mcp-jpo-patent-info`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/pipeworx-mcp-jpo-patent-info.md), [page](https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/pipeworx-mcp-jpo-patent-info)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-jpo-patent-info`
- Version: `0.2.1`
- 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-jpo-patent-info).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 2 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 331 tokens (~165/item across 2 items; 2 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Jpo Patent Info MCP server?

Jpo Patent Info runs locally as an npm package, launched with npx -y @pipeworx/mcp-jpo-patent-info. 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-jpo-patent-info -- npx -y @pipeworx/mcp-jpo-patent-info
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-jpo-patent-info -- npx -y @pipeworx/mcp-jpo-patent-info
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-jpo-patent-info --command npx --arg -y --arg @pipeworx/mcp-jpo-patent-info
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-jpo-patent-info:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-jpo-patent-info"]
```

### Netclaw

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

### Vellum

```bash
assistant mcp add pipeworx-io-jpo-patent-info -t stdio -c npx -a -y @pipeworx/mcp-jpo-patent-info
```

### Other

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

## 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-03 (score 83, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 67, −15)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 82, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 81, +1)

No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.

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

First indexed and scored.

## MCP tools (2)

### `jp_patent_status` (~152 tokens)

Look up a Japanese patent or utility model by number and get its legal status: current stage (filing, examination, grant, refused, ceased), the latest status event, application/publication/registration numbers and dates, title, applicant or right holder, and FI classifications. Source: Japan Patent Office public register. Examples: application number 2020-000001, registration number 6770223.

Input parameters:

- `number` (string, required): Japanese number, e.g. "2020-000001" (application or publication, year-serial) or "6770223" (registration). Prefixes like 特願 are accepted.
- `number_type` (string): What the number is. Default: application.

### `jp_trademark_status` (~119 tokens)

Look up a Japanese trademark by application or registration number: mark text (word marks), kana reading, goods/services classes, owner, application and registration dates, mark type and status code. Source: Japan Patent Office public trademark register. Examples: application 2020-000001, registration 6316886.

Input parameters:

- `number` (string, required): Trademark application number ("2020-000001" or "2020000001") or registration number ("6316886").
- `number_type` (string): What the number is. Default: application.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Jpo Patent Info MCP server?

Jpo Patent Info is an MCP server listed in the public MCP registry as io.github.pipeworx-io/jpo-patent-info. JPO patent information: Japanese patent, utility model and trademark status from the Japan Patent… This page covers its npm package (@pipeworx/mcp-jpo-patent-info).

### Is the Jpo Patent Info MCP server safe to use?

Jpo Patent Info scores 83 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 Jpo Patent Info MCP server expose?

Jpo Patent Info exposes 2 tools: jp_patent_status, jp_trademark_status. Their descriptions and schemas cost roughly 271 tokens of context every time the server is loaded.

### Is the Jpo Patent Info MCP server still maintained?

Jpo Patent Info 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 Jpo Patent Info MCP server under?

Jpo Patent Info 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-jpo-patent-info
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-jpo-patent-info
- Repository: https://github.com/pipeworx-io/mcp-jpo-patent-info
- Website: https://pipeworx.io/packs/jpo-patent-info
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/pipeworx-mcp-jpo-patent-info.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/pipeworx-mcp-jpo-patent-info.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-jpo-patent-info/pipeworx-mcp-jpo-patent-info