# Epo Ops (npm · @pipeworx/mcp-epo-ops)

EPO Open Patent Services MCP

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

## Components

- remote · `gateway.pipeworx.io`: 87/100, [markdown](https://verifymcp.io/servers/pipeworx-io-epo-ops/epo-ops-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-epo-ops/epo-ops-mcp)
- npm · `@pipeworx/mcp-epo-ops`: 90/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-epo-ops/pipeworx-mcp-epo-ops.md), [page](https://verifymcp.io/servers/pipeworx-io-epo-ops/pipeworx-mcp-epo-ops)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-epo-ops`
- 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-22.

- **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-epo-ops).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 20 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 (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1901 tokens (~316/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 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 Epo Ops MCP server?

Epo Ops runs locally as an npm package, launched with npx -y @pipeworx/mcp-epo-ops. 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-epo-ops -- npx -y @pipeworx/mcp-epo-ops
```

### Cursor

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

### VS Code

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

### Codex

```bash
codex mcp add pipeworx-io-epo-ops -- npx -y @pipeworx/mcp-epo-ops
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-epo-ops --command npx --arg -y --arg @pipeworx/mcp-epo-ops
```

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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-22 (score 90, +1)

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

### 2026-11-20 (score 89, +1)

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

### 2026-11-18 (score 88, +1)

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

### 2026-11-15 (score 87, +1)

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

### 2026-11-14 (score 86, 0)

- [functional regression] Security disclosure: unverified → fail

### 2026-11-13 (score 86, +1)

- [functional regression] Security disclosure: fail → unverified

### 2026-11-11 (score 85, +1)

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

### 2026-11-09 (score 84, +1)

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

## MCP tools (6)

### `search_patents` (~440 tokens)

Search published patents worldwide via EPO OPS and get back full bibliographic records — title, applicants, inventors, publication date, country, IPC classifications — for each hit. Searches EPO DOCDB, which indexes publications from 100+ patent offices, so Chinese, Japanese, Korean, US and PCT/WO documents are all in scope alongside European ones — PCT international applications (publications beginning "WO") are covered here and in every other tool in this pack, not just EP filings. Each hit's `kind` code tells you what stage it is: an "A"-prefixed kind (A1, A2, A3…) is a published APPLICATION, not yet granted; a "B"-prefixed kind (B1, B2…) is a GRANTED patent; a WO publication's "A1"/"A2"/"A3" marks the PCT publication itself, not a grant — PCT applications are examined and granted nationally after entering each country's national phase, which this pack does not track. Results are not filtered to grants by default — most hits from a bare keyword search will be "A" kind. To find issued/granted patents specifically, scope the query with a kind or grant-relevant field (e.g. add `AND pd>=<date>` and check `kind` on the returned rows) rather than assuming an unfiltered hit is granted. Example queries: "ta=hydrogen", "in=Tesla", "pa=apple", "txt=neural network AND pd>=2020", "pa=moderna and pn=WO" (a company's PCT filings).

Input parameters:

- `query` (string, required): EPO CQL — fields: ta (title-abstract), ti (title), ab (abstract), txt (any text), in (inventor), pa (applicant), cl (classification), pn (publication number), ap (application number), pr (priority),…
- `range` (string): Result range "start-end" (1-indexed). Max 100 per page. Default "1-25".

### `get_biblio` (~275 tokens)

Bibliographic data for one published patent — title, inventors, applicants, publication date, IPC classifications. Drawn from EPO DOCDB, which covers 100+ patent offices, so Chinese, Japanese, Korean, US and PCT/WO publications resolve as well as European ones. A PCT international application (a "WO" publication number) is answered the same as any other — this is NOT the International Search Report or Written Opinion, which EPO OPS does not carry at all; for those, go to WIPO PATENTSCOPE (patentscope.wipo.int). Give the publication number as printed on the document; a trailing kind code such as the "A" in "CN117928705A" is handled for you.

Input parameters:

- `number` (string, required): Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". Spaces, co…

### `get_family` (~406 tokens)

INPADOC family — every related patent publication worldwide covering the same underlying invention, which is how you find the Chinese, Japanese, US, European and PCT/WO members of one filing. Returns a member count and the countries covered first, then one row per family member: publication number (with kind and date), application number, and priority claims. A PCT international application is a normal member here — give its "WO" publication number, or (before it has published) a WIPO application number like "PCT/US2024/012345". This does NOT include the International Search Report or Written Opinion of a PCT application — EPO OPS does not carry that document at all; for it, go to WIPO PATENTSCOPE (patentscope.wipo.int). Give the publication number as printed on the document; a trailing kind code is handled for you.

Input parameters:

- `number` (string, required): Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". Spaces, co…
- `raw` (boolean): Include the raw OPS XML-as-JSON family payload alongside the normalised member list. Off by default — the normalised list has everything most callers need.

### `get_abstract` (~166 tokens)

Fetch the abstract text of a published patent from EPO OPS. Give the publication number as printed on the document; a trailing kind code is handled for you. Requires _apiKey=consumer_key:consumer_secret.

Input parameters:

- `number` (string, required): Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". Spaces, co…

### `get_claims` (~226 tokens)

Fetch the full claims text of a published patent from EPO OPS. EPO's full-text collection is narrower than its bibliographic one — European (EP) and PCT (WO) publications have the broadest claims coverage, and a publication outside that collection comes back as found:false naming get_biblio as the route to its title, applicants and abstract. Give the publication number as printed on the document; a trailing kind code is handled for you. Requires _apiKey=consumer_key:consumer_secret.

Input parameters:

- `number` (string, required): Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". Spaces, co…

### `get_legal_status` (~333 tokens)

INPADOC legal status for a patent family, sourced from the EPO's worldwide legal-status database — grant, lapse, opposition, withdrawal, appeal and renewal-fee events as reported by the national/regional offices that know about this filing. Answers "is this patent still in force" and "did it lapse for non-payment of a renewal fee", which get_biblio, get_family and get_claims cannot. A European patent can stay in force in some contracting states while lapsing in others, so events are grouped per publication/country rather than collapsed into one in-force flag — read each member's events to see which jurisdiction a given event applies to. Each event carries an `influence` of "negative" (lapse, withdrawal, refusal, revocation), "positive" (grant, renewal, fee paid) or "neutral" (procedural/informational). Give the publication number as printed on the document; a trailing kind code is handled for you. Requires _apiKey=consumer_key:consumer_secret.

Input parameters:

- `number` (string, required): Publication number as printed on the document, e.g. "EP1234567", "CN117928705A", "US10000000", or a PCT international publication like "WO2025028566" / "WO 2025/028566" / "WO2025028566A1". Spaces, co…

## Diagnostics

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

## Score history

- 2026-11-22: 90
- 2026-11-21: 89
- 2026-11-20: 89
- 2026-11-19: 88
- 2026-11-18: 88
- 2026-11-17: 87
- 2026-11-16: 87
- 2026-11-15: 87
- 2026-11-14: 86
- 2026-11-13: 86
- 2026-11-12: 85
- 2026-11-11: 85
- 2026-11-10: 84
- 2026-11-09: 84
- 2026-11-08: 83
- 2026-11-07: 83
- 2026-11-06: 82
- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 79

## Common questions

### What is the Epo Ops MCP server?

Epo Ops is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epo-ops. EPO Open Patent Services MCP. This page covers its npm package (@pipeworx/mcp-epo-ops).

### Is the Epo Ops MCP server safe to use?

Epo Ops scores 90 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 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 Epo Ops MCP server expose?

Epo Ops exposes 6 tools: search_patents, get_biblio, get_family, get_abstract, get_claims, get_legal_status. Their descriptions and schemas cost roughly 1,846 tokens of context every time the server is loaded.

### Is the Epo Ops MCP server still maintained?

Epo Ops is still listed as active in the MCP registry. We last reached this channel on 22 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 Epo Ops MCP server under?

Epo Ops declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Epo Ops MCP server?

VerifyMCP ran 16 checks on Epo Ops, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

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