Remote MCP · Endpoint

Cipo MCP server

No. Cipo answered an MCP handshake 33 minutes ago.

UpLast checked 33 minutes ago

Server URL

https://gateway.pipeworx.io/cipo/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/cipo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
206 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
CIPO MCP — Canadian Patents Database
Listing
From the official MCP registry (active).
Recent checks of Cipo
CheckedResultHandshake
33 minutes agoHandshake completed206 ms
3 days agoHandshake completed1.08 s
13 days agoHandshake completed277 ms
13 days agoHandshake completed705 ms
15 days agoHandshake completed486 ms
16 days agoHandshake completed84 ms
17 days agoHandshake completed77 ms
18 days agoHandshake completed119 ms
18 days agoHandshake completed319 ms
20 days agoHandshake completed883 ms
23 days agoHandshake completed143 ms
25 days agoHandshake completed1.01 s
28 days agoHandshake completed972 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Cipo and makes no claim about it beyond what these checks measured.