Bragproof

← Reports

@pipeworx/mcp-epo-ops

Starts with no setup0.2.1npm

Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.

Needs to start: nothing
Contacts while installing and starting: gateway.pipeworx.io

6tools listed
1host contacted
0files written
0.3 sto start
0dependencies

What it contacted

Hosts it looked up or connected to while installing and starting with no input, watched from outside its sandbox. The npm registry is left out. Says nothing about what its tools contact when called.

Starting it

npx -y @pipeworx/mcp-epo-ops@0.2.1

Installing a package runs its code. Use a sandbox for anything you have not read.

What its tools tell an agent

In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.

Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.

Tools

epo_ops_search_patents query, range
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).
get_biblio number
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.
get_family number, raw
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.
epo_ops_get_abstract number
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.
get_claims number
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.
get_legal_status number
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.

Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.

Install facts

LicenseMIT
Needsnode >=18
Sourcegithub.com/pipeworx-io/mcp-epo-ops
Install scriptsNone declared by it or anything installed with it.
Tarballsha512-2oSN2jmjVDfR/oJ84PVX5LjhlDrqnEa/CUZ9bZvlcoyg/vdLOTLMQvafYUu0jN9xnA3HYB59PF5aoQVQ6HEyKA==

Check this report yourself

This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.

Show it on your README

Bragproof: Starts with no setup

[![Bragproof](https://bragproof.smaverk.com/badge/@pipeworx/mcp-epo-ops.svg)](https://bragproof.smaverk.com/r/%40pipeworx/mcp-epo-ops)

New version out? Ask for a fresh report.