Epo Publication Server
NPM · @PIPEWORX/MCP-EPO-PUBLICATION-SERVER · 2 COMPONENTS
EPO European Publication Server (EPS) MCP
Available components
Last scanned (17 hours ago)
Scores higher than 72% of npm servers
Category Health and Science
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-publication-server). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 3 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 784 tokens (~261/item across 3 items; 3 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 Management20
- Stability observed for 6 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
- Tool safety: pass → unverified ▼ security
- Stability: Stability not yet verified: we do not have a sandbox capture of the MCP schema this version of the package serves yet. security
- Security disclosure: unverified → fail ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Capabilities: pass → unverified ▼ functional
- Stability: unverified → 0.07 ▲ functional
- First check of Schema quality: unverified functional
- Package version: 0.2.0 → 0.2.1 functional
- 30 Oct 26 79
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-epo-publication-server@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-publication-server |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-epo-publication-server/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3635925750 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:d037dcb537ac1615831d1f86603a524dc1476b3676c29f4c596b81446223bade3f4672550857686af33657cd20ef6eb926cf9a00b225b018925587b62 |
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 →
eps_get_document ~271
Fetch one EP patent publication as published by the EPO — bibliographic data, or the full text of its abstract, claims or description. Give "number" as a full id from eps_list_publications (e.g. "EP4819826NWA1", recommended) or a bare publication number ("EP4819826") plus "kind" ("A1", "B1", ...). Full claims/description text is reliably present for GRANTED (B-kind) patents and directly-filed (non-PCT) applications; a Euro-PCT national-phase entry (the common case) carries only the bibliographic record here because its full text was already published as a WIPO pamphlet — the response says which case it hit rather than returning an empty result.
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | – | Kind code, e.g. "A1", "B1". Required if "number" is a bare publication number without one. |
| number | string | yes | Full publication-server id (e.g. "EP4819826NWA1") or bare publication number (e.g. "EP4819826"). |
| part | string | – | Which part to return: "biblio" (default — title, applicants, dates, classifications), "abstract", "claims", or "description". |
No output schema declared.
No examples provided.
eps_list_publications ~271
List every EP patent publication issued on one EPO publication date, with publication number, kind code, title and applicant(s). Returns the real total on that date before any filtering. "date" must be a real EPO publication date (get one from eps_publication_dates) — an arbitrary date fails loudly rather than silently returning nothing. "kind" filters to a kind code ("A1" newly-published application, "A2" application without search report, "A3" search report, "B1"/"B2"/"B3" granted-patent stages) or a bare letter ("A" or "B") for either family.
| Name | Type | Req | Description |
|---|---|---|---|
| date | string | yes | EPO publication date, YYYYMMDD or YYYY-MM-DD, e.g. "2026-10-14". Must be a real EPO publication date. |
| kind | string | – | Kind-code filter: "A1", "A2", "A3", "B1", "B2", "B3", or bare "A" / "B". |
| limit | number | – | Max publications to return with title/applicant detail (default 20, max 50). "total_on_date" and "total_matching_filter" always report the real counts regardless of this limit. |
No output schema declared.
No examples provided.
eps_publication_dates ~185
List EPO European Publication Server publication dates (almost always Thursdays, weekly since 1978) with a real document count per date. Filter by "year" (e.g. "2026") or a "from"/"to" range (YYYYMMDD or YYYY-MM-DD); omit both to get the most recent dates. Use a returned date with eps_list_publications to see what was published that day.
| Name | Type | Req | Description |
|---|---|---|---|
| from | string | – | Start of a date range, inclusive, YYYYMMDD or YYYY-MM-DD. |
| limit | number | – | Max dates to return, newest first (default 20, max 100). |
| to | string | – | End of a date range, inclusive, YYYYMMDD or YYYY-MM-DD. |
| year | string | – | Four-digit year, e.g. "2026". Filters to publication dates in that year. |
No output schema declared.
No examples provided.
How do I install the Epo Publication Server MCP server?
Epo Publication Server runs locally as an npm package, launched with npx -y @pipeworx/mcp-epo-publication-server. 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-publication-server
claude mcp add pipeworx-io-epo-publication-server -- npx -y @pipeworx/mcp-epo-publication-server
What is the Epo Publication Server MCP server?
Epo Publication Server is an MCP server listed in the public MCP registry as io.github.pipeworx-io/epo-publication-server. EPO European Publication Server (EPS) MCP. This page covers its npm package (@pipeworx/mcp-epo-publication-server).
Is the Epo Publication Server MCP server safe to use?
Epo Publication Server 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 Epo Publication Server MCP server expose?
Epo Publication Server exposes 3 tools: eps_publication_dates, eps_list_publications, eps_get_document. Their descriptions and schemas cost roughly 727 tokens of context every time the server is loaded.
Is the Epo Publication Server MCP server still maintained?
Epo Publication Server 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 Epo Publication Server MCP server under?
Epo Publication Server 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 Publication Server MCP server?
VerifyMCP ran 16 checks on Epo Publication Server, 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.