Epo Ops
NPM · @PIPEWORX/MCP-EPO-OPS · 2 COMPONENTS
EPO Open Patent Services MCP
Available components
Last scanned (7 hours ago)
Scores higher than 85% 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-epo-ops). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 20 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 (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
- Stability observed for 24 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
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 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
Checks we ran (16)
- Malware scan
- Known CVEs
- Install scripts
- Dependency health
- Source repository
- Provenance
- License
- Maintenance
- Security disclosure
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this package (2)
- Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
- Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
The score does not measure everything. What the score does not measure →
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.
- 22 Nov 26 +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.
- 20 Nov 26 +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.
- 18 Nov 26 +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.
- 15 Nov 26 +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.
- 14 Nov 26 0
- Security disclosure: unverified → fail ▼ functional
- 13 Nov 26 +1
- Security disclosure: fail → unverified ▼ functional
- 11 Nov 26 +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.
- 9 Nov 26 +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.
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 22 Nov 2026 · Analysed npm/@pipeworx/mcp-epo-ops@0.2.1
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-epo-ops |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-epo-ops/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635925544 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:da848dda39a35437d1fe827ce0f557e4b8e1943aea9c46bf09467d6d9be5728ca0fef74b3932cc42f69f614bb48cdf719c0dc7601e7d3c5e5aa10550e |
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 →
get_abstract ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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… |
No output schema declared.
No examples provided.
get_biblio ~275
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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… |
No output schema declared.
No examples provided.
get_claims ~226
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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… |
No output schema declared.
No examples provided.
get_family ~406
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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. |
No output schema declared.
No examples provided.
get_legal_status ~333
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | 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… |
No output schema declared.
No examples provided.
search_patents ~440
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).
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | 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". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-epo-ops
claude mcp add pipeworx-io-epo-ops -- npx -y @pipeworx/mcp-epo-ops
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.