Cipo
NPM · @PIPEWORX/MCP-CIPO · 2 COMPONENTS
CIPO MCP — Canadian Patents Database
Available components
Last scanned (6 hours ago)
Scores higher than 76% of npm servers
Category Education and Research
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-cipo). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 5 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- 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. 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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 +16
- Malware scan: unverified → pass ▲ security
- 31 Oct 26 0
- Security disclosure: unverified → fail ▼ functional
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.2.1 → 0.2.2 functional
- 30 Oct 26 65
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-cipo@0.2.2
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-cipo |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-cipo/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3606795691 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:898edc66b6587c61c319efc2f78370d3f66764ae58f0ff076712f0a27dda40760a26579f0fce9b264a2bc1a1353c578ba1276b9849786bdae2da852a6 |
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 →
get_cipo_patent ~125
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.
| Name | Type | Req | Description |
|---|---|---|---|
| number | string | yes | Canadian patent/application number, e.g. "2553707" or "CA 3265179". |
No output schema declared.
No examples provided.
search_cipo_patents ~217
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.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max results to return, 1-50. Default 10. |
| name | string | yes | 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". |
No output schema declared.
No examples provided.
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.
npm · @pipeworx/mcp-cipo
claude mcp add pipeworx-io-cipo -- npx -y @pipeworx/mcp-cipo
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.