# Cipo (npm · @pipeworx/mcp-cipo)

CIPO MCP — Canadian Patents Database

- Trust score: 83/100 (high trust)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-cipo/cipo-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-cipo/cipo-mcp)
- npm · `@pipeworx/mcp-cipo`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo.md), [page](https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-cipo`
- Version: `0.2.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-cipo).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 5 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 394 tokens (~197/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Cipo MCP server?

Cipo runs locally as an npm package, launched with npx -y @pipeworx/mcp-cipo. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add pipeworx-io-cipo -- npx -y @pipeworx/mcp-cipo
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-cipo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cipo"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-cipo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cipo"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-cipo -- npx -y @pipeworx/mcp-cipo
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-cipo": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-cipo"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-cipo --command npx --arg -y --arg @pipeworx/mcp-cipo
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-cipo:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-cipo"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-cipo": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-cipo"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-cipo -t stdio -c npx -a -y @pipeworx/mcp-cipo
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-cipo": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-cipo"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 83, +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.

### 2026-11-03 (score 82, +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.

### 2026-11-01 (score 81, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-10-31 (score 65, 0)

- [functional regression] Security disclosure: unverified → fail
- [functional improvement] Stability: unverified → 0.03
- [functional] Package version: 0.2.1 → 0.2.2

### 2026-10-30 (score 65)

First indexed and scored.

## MCP tools (2)

### `search_cipo_patents` (~217 tokens)

Search the Canadian Patents Database (CIPO) by owner or applicant name and get back matching Canadian patents/applications — number, title, relevance. Covers every patent and application in CIPO's database, Canadian and foreign-origin alike, as long as it was filed or granted in Canada. Use "role":"applicant" to search the party that filed the application, or "role":"owner" to search the current owner of record (these can differ after an assignment). Follow up with get_patent for status, filing date and issue date on any hit.

Input parameters:

- `limit` (number): Max results to return, 1-50. Default 10.
- `name` (string, required): Company or individual name to search for, e.g. "Shopify Inc." or "Royal Bank of Canada". Multi-word names are matched as a phrase.
- `role` (string): Which party field to search: "owner" (current owner of record) or "applicant" (party that filed). Default "owner".

### `get_cipo_patent` (~125 tokens)

Look up one Canadian patent or application by number in the Canadian Patents Database (CIPO) and get its full bibliographic record: title (English/French), current status, filing date, issue/grant date (blank if not yet granted), owners, applicants, inventors and IPC classification. Accepts the number with or without a "CA" prefix, spaces or dashes — digits only, up to 7 digits.

Input parameters:

- `number` (string, required): Canadian patent/application number, e.g. "2553707" or "CA 3265179".

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 82
- 2026-11-03: 82
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 65
- 2026-10-30: 65

## Common questions

### What is the Cipo MCP server?

Cipo is an MCP server listed in the public MCP registry as io.github.pipeworx-io/cipo. CIPO MCP, Canadian Patents Database. This page covers its npm package (@pipeworx/mcp-cipo).

### Is the Cipo MCP server safe to use?

Cipo scores 83 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 Cipo MCP server expose?

Cipo exposes 2 tools: search_cipo_patents, get_cipo_patent. Their descriptions and schemas cost roughly 342 tokens of context every time the server is loaded.

### Is the Cipo MCP server still maintained?

Cipo 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 Cipo MCP server under?

Cipo 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 Cipo MCP server?

VerifyMCP ran 16 checks on Cipo, 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.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-cipo
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-cipo
- Repository: https://github.com/pipeworx-io/mcp-cipo
- Website: https://pipeworx.io/packs/cipo
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-cipo/pipeworx-mcp-cipo