Remote MCP · Endpoint

Wipo Ipc MCP server

No. Wipo Ipc answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://gateway.pipeworx.io/wipo-ipc/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/wipo-ipc
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
676 ms
Tools exposed
48 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
WIPO IPCPUB (International Patent Classification) MCP
Listing
From the official MCP registry (active).
Recent checks of Wipo Ipc
CheckedResultHandshake
16 minutes agoHandshake completed676 ms
8 days agoHandshake completed177 ms
9 days agoHandshake completed69 ms
11 days agoHandshake completed113 ms
12 days agoHandshake completed103 ms
13 days agoHandshake completed177 ms
14 days agoHandshake completed87 ms
15 days agoHandshake completed111 ms
16 days agoHandshake completed151 ms
19 days agoHandshake completed75 ms
21 days agoHandshake completed835 ms
24 days agoHandshake completed67 ms
26 days agoHandshake completed100 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 Wipo Ipc and makes no claim about it beyond what these checks measured.