Cipo MCP server

@pipeworx/cipo

Canadian patents and patent applications — search by owner or applicant name, or look up one record by number for its status, filing date and issue date.

Part of Pipeworx — an MCP gateway connecting AI agents to 1875+ live data sources. This is an independent, unofficial integration — not affiliated with, endorsed by, or published by the upstream provider.

Tools

applicant name and get back matching patents/applications: number, title, relevance. role is "owner" (current owner of record) or "applicant" (party that filed); these can differ after an assignment.

• searchcipopatents(name, role, limit) — search by current owner or

record: English/French title, current status, filing date, issue/grant date (blank until granted), owners, applicants, inventors, IPC classification.

• getcipopatent(number) — one patent/application's full bibliographic

Auth

Keyless. No registration, no API key.

Data sources

every patent application filed in Canada and every patent granted by Canada, Canadian-origin or foreign-origin alike. Live per-request calls against CIPO's own public search service; nothing is downloaded or mirrored.

• Canadian Intellectual Property Office (CIPO), Canadian Patents Database —

Notes

issued_date — that is CIPO's own data, not a missing field on our side.

• A patent that has only been filed, not yet granted, has an empty

record — the domestic filed date for most applications, or the PCT filing date for one that entered Canada via the PCT national phase. Both answer "when was this filed."

• filing_date is whichever CIPO calls the earliest filing event for that

prefix, spaces or dashes in the input are stripped automatically.

• Numbers are CIPO patent/application numbers, at most 7 digits. A "CA"

"Next Generation Patents" migration (their notice, not ours) — status fields on some records may lag or show as blank even when the application is active. That is upstream, and this pack surfaces whatever CIPO currently reports.

• CIPO's own CPD has had intermittent data-quality issues since its 2024

Quick Start

Add to your MCP client (Claude Desktop, Cursor, Windsurf, etc.):

{
  "mcpServers": {
    "cipo": {
      "url": "https://gateway.pipeworx.io/cipo/mcp"
    }
  }
}

What this endpoint actually serves

tools/list at https://gateway.pipeworx.io/cipo/mcp returns the tools in the table above plus the shared Pipeworx meta-tools — askpipeworx, discovertools, 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:

{
  "mcpServers": {
    "pipeworx": {
      "url": "https://gateway.pipeworx.io/mcp"
    }
  }
}

Both URLs reach the same gateway and the same 1875+ 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

curl -X POST https://gateway.pipeworx.io/v1/tools/search_cipo_patents \
  -H 'Content-Type: application/json' \
  -d '{"name":"Shopify Inc.","role":"applicant","limit":5}'

Shortened. The full README is on GitHub.