@pipeworx/mcp-epo-publication-server 0.0.0-stage → 0.1.0

package/LICENSE

@@ -0,0 +1,21 @@
+MIT License
+
+Copyright (c) 2026 Mojibake Inc.
+
+Permission is hereby granted, free of charge, to any person obtaining a copy
+of this software and associated documentation files (the "Software"), to deal
+in the Software without restriction, including without limitation the rights
+to use, copy, modify, merge, publish, distribute, sublicense, and/or sell
+copies of the Software, and to permit persons to whom the Software is
+furnished to do so, subject to the following conditions:
+
+The above copyright notice and this permission notice shall be included in all
+copies or substantial portions of the Software.
+
+THE SOFTWARE IS PROVIDED "AS IS", WITHOUT WARRANTY OF ANY KIND, EXPRESS OR
+IMPLIED, INCLUDING BUT NOT LIMITED TO THE WARRANTIES OF MERCHANTABILITY,
+FITNESS FOR A PARTICULAR PURPOSE AND NONINFRINGEMENT. IN NO EVENT SHALL THE
+AUTHORS OR COPYRIGHT HOLDERS BE LIABLE FOR ANY CLAIM, DAMAGES OR OTHER
+LIABILITY, WHETHER IN AN ACTION OF CONTRACT, TORT OR OTHERWISE, ARISING FROM,
+OUT OF OR IN CONNECTION WITH THE SOFTWARE OR THE USE OR OTHER DEALINGS IN THE
+SOFTWARE.

package/README.md

@@ -1,3 +1,170 @@
-# Temporary Holding Version
+# @pipeworx/epo-publication-server
 
-This version is a temporary placeholder for this package. An operational version to replace this has been submitted for review and is awaiting a staged release.
+As-published European patent documents — publication dates, per-date listings
+with titles and applicants, and full document text (biblio, abstract, claims,
+description) for granted patents and directly-filed applications. Keyless.
+
+Part of [Pipeworx](https://pipeworx.io) — an MCP gateway connecting AI agents to 1837+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.
+
+## Tools
+
+- `eps_publication_dates(year?, from?, to?, limit?)` — EPO publication dates
+  (weekly, almost always Thursdays, back to 1978) with a real per-date
+  document count.
+- `eps_list_publications(date, kind?, limit?)` — every EP publication issued
+  on one date, with kind code, title and applicant(s); reports the true total
+  before any filtering.
+- `eps_get_document(number, kind?, part?)` — one publication's bibliographic
+  data, abstract, claims or description text, as published.
+
+## Auth
+
+Keyless. No account, no registration.
+
+EPO states a fair-use cap of 5 GB per rolling 7-day window per calling IP,
+confirmed live via the `x-quotaperweek-remaining`/`x-quotaperweek-used`
+response headers. General EPO site terms apply; no EPS-specific
+redistribution restriction was found.
+
+## Data sources
+
+- European Patent Office (EPO), European Publication Server — the
+  as-published XML/HTML of every EP patent application and granted European
+  patent.
+
+## Notes for the next person
+
+- **The list-by-date trap**: asking for a date that is not a real EPO
+  publication date (wrong day of week, a future date, a typo) answers
+  **HTTP 200** with a tiny HTML shell and zero entries — not a 404, not an
+  error. EPO has never actually had a genuinely empty publication date in
+  2,400+ weeks of history, so `eps_list_publications` treats zero parsed
+  entries as a loud failure rather than a silent empty list. Always get a
+  real date from `eps_publication_dates` first.
+- **Most application (A-kind) publications carry NO claims/description text.**
+  The large majority of EP applications enter via the PCT route, and EPO
+  republishes only the bibliographic (SDOBI) record for those — the full
+  specification was already published as the WIPO (WO) pamphlet, so EPO does
+  not retype it. Full claims/description/drawings text is reliably present
+  for **granted (B-kind)** patents and for **directly-filed** (non-PCT)
+  applications. `eps_get_document` reports which case it hit (and names the
+  referenced WO publication when it's a PCT case) rather than returning an
+  empty part silently.
+- **Document ids aren't just the publication number + kind.** The REST path
+  segment is a longer id like `EP4819826NWA1` — the publication number, an
+  internal marker (`NW` for the overwhelming majority of documents, `W1` for
+  a minority), and the kind code. `eps_list_publications` returns these ids
+  directly; `eps_get_document` also accepts a bare number + kind and tries
+  the common id forms in order.
+- **A made-up document id does not 404 — it 500s** with a small JSON body
+  (`{"code":9000,"message":"Unhandled internal server error."}`). This is
+  actually easy to work with: `eps_get_document` tries its candidate ids and
+  reports `found:false` with the upstream status once all of them fail.
+- What this adds over `mcps/epo-ops` (EPO Open Patent Services, OAuth2): the
+  as-published document text itself, keyless. `epo-ops` keeps INPADOC
+  worldwide legal status and CQL search across DOCDB (100+ patent offices);
+  this pack only ever sees EP publications.
+
+## Quick Start
+
+Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):
+
+```json
+{
+  "mcpServers": {
+    "epo-publication-server": {
+      "url": "https://gateway.pipeworx.io/epo-publication-server/mcp"
+    }
+  }
+}
+```
+
+### What this endpoint actually serves
+
+`tools/list` at `https://gateway.pipeworx.io/epo-publication-server/mcp` returns the tools in the table
+above **plus the shared Pipeworx meta-tools** — `ask_pipeworx`,
+`discover_tools`, `search_within`, `remember`/`recall` and the rest of the
+gateway-wide set. So the tool count you see is larger than this table: a
+single-pack endpoint currently lists roughly 30 shared tools alongside the
+pack's own. The connection's `initialize` response states its exact scope, and
+is the authoritative answer for a given day.
+
+This is deliberate, not multiplexing by accident. The meta-tools are what let a
+scoped connection answer a question this pack does not cover — via
+`ask_pipeworx`, which routes across the whole catalog — without you adding a
+second MCP server. There is currently no way to mount a pack endpoint without
+them; if the extra schemas cost you more context than the routing is worth,
+connect to the full gateway once rather than to several pack endpoints.
+
+Or connect to the full Pipeworx gateway to get every pack's tools listed
+directly, instead of just this one's:
+
+```json
+{
+  "mcpServers": {
+    "pipeworx": {
+      "url": "https://gateway.pipeworx.io/mcp"
+    }
+  }
+}
+```
+
+Both URLs reach the same gateway and the same 1837+ data sources. The
+only difference is which pack's tools are listed **directly**; `ask_pipeworx`
+reaches all of them from either one.
+
+## No MCP client? Call it over HTTP
+
+```bash
+curl -X POST https://gateway.pipeworx.io/v1/tools/eps_publication_dates \
+  -H 'Content-Type: application/json' \
+  -d '{"year":"2026","limit":5}'
+```
+
+No account needed for the first calls. Inspect any tool: `GET https://gateway.pipeworx.io/v1/tools/eps_publication_dates`. Find one: `POST https://gateway.pipeworx.io/v1/tools/search_packs` with `{"query":"..."}`.
+
+## Standalone (no gateway account)
+
+This package also runs as a local stdio MCP server — no Pipeworx account, no
+gateway round-trip:
+
+```json
+{
+  "mcpServers": {
+    "epo-publication-server": {
+      "command": "npx",
+      "args": ["-y", "@pipeworx/mcp-epo-publication-server"]
+    }
+  }
+}
+```
+
+Or run it directly to confirm it starts:
+
+```bash
+npx -y @pipeworx/mcp-epo-publication-server
+```
+
+It speaks MCP over stdin/stdout and answers `initialize`/`tools/list`/`tools/call`
+for **only** this pack's tools — none of the shared meta-tools the gateway
+connection above adds. Same source, same tools, no ask_pipeworx routing.
+
+## Using with ask_pipeworx
+
+Instead of calling tools directly, you can ask questions in plain English —
+this works on the pack endpoint above as well as on the full gateway:
+
+```
+ask_pipeworx({ question: "your question about Epo Publication Server data" })
+```
+
+The gateway picks the right tool and fills the arguments automatically.
+
+## More
+
+- [Docs and guides](https://pipeworx.io/docs)
+- [pipeworx.io](https://pipeworx.io)
+
+## License
+
+MIT

package/bin/cli.js

@@ -0,0 +1,17 @@
+#!/usr/bin/env node
+//
+// Entry point for `npx @pipeworx/mcp-<slug>`.
+//
+// Packs ship as raw TypeScript (no build step — see publish-pack.sh for why:
+// tsx sidesteps every extensionless-import / bare-JSON-import edge case a
+// per-pack tsc build would have to solve one pack at a time). This file
+// registers tsx's ESM loader programmatically, then hands off to src/server.ts,
+// which wraps the pack's {tools, callTool} export in a stdio MCP server.
+//
+// Copied verbatim into every published pack repo by scripts/publish-pack.sh —
+// edit this file, not a per-pack copy.
+import { register } from 'tsx/esm/api';
+
+register();
+
+await import('../src/server.ts');

package/package.json

@@ -1,6 +1,32 @@
 {
   "name": "@pipeworx/mcp-epo-publication-server",
-  "version": "0.0.0-stage",
-  "stub": true,
-  "description": "Temporary package placeholder for staged publishing"
-}
+  "version": "0.1.0",
+  "description": "EPO European Publication Server (EPS) MCP",
+  "type": "module",
+  "main": "src/index.ts",
+  "types": "src/index.ts",
+  "bin": {
+    "mcp-epo-publication-server": "bin/cli.js"
+  },
+  "keywords": ["mcp", "mcp-server", "model-context-protocol", "pipeworx", "epo-publication-server"],
+  "license": "MIT",
+  "repository": {
+    "type": "git",
+    "url": "git+https://github.com/pipeworx-io/mcp-epo-publication-server.git"
+  },
+  "scripts": {
+    "typecheck": "tsc --noEmit"
+  },
+  "dependencies": {
+    "@modelcontextprotocol/sdk": "^1.30.0",
+    "tsx": "^4.19.0"
+  },
+  "devDependencies": {
+    "typescript": "^5.9.3",
+    "@cloudflare/workers-types": "^4.20260405.1"
+  },
+  "pipeworx": {
+    "sourceHash": "v1-8ae2b12d11a59db30b29762c0c3ac75723b549b4929344190f9ffd9a6607d1b0",
+    "sourceCommit": "0f33463aa47677f38e4f177a4b4a7160dd80819f"
+  }
+}

package/server.json

@@ -0,0 +1,18 @@
+{
+  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json",
+  "name": "io.github.pipeworx-io/epo-publication-server",
+  "title": "Epo Publication Server",
+  "description": "EPO European Publication Server (EPS) MCP",
+  "version": "0.1.0",
+  "websiteUrl": "https://pipeworx.io/packs/epo-publication-server",
+  "repository": {
+    "url": "https://github.com/pipeworx-io/mcp-epo-publication-server",
+    "source": "github"
+  },
+  "remotes": [
+    {
+      "type": "streamable-http",
+      "url": "https://gateway.pipeworx.io/epo-publication-server/mcp"
+    }
+  ]
+}