Remote MCP · Endpoint

Euipo MCP server

No. Euipo answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

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

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/euipo
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
51 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
EUIPO MCP — EU trademarks, registered Community designs, and the shared reference registers the…
Listing
From the official MCP registry (active).
Recent checks of Euipo
CheckedResultHandshake
42 minutes agoHandshake completed74 ms
8 days agoHandshake completed169 ms
9 days agoHandshake completed74 ms
11 days agoHandshake completed118 ms
12 days agoHandshake completed114 ms
13 days agoHandshake completed75 ms
14 days agoHandshake completed76 ms
15 days agoHandshake completed143 ms
16 days agoHandshake completed306 ms
19 days agoHandshake completed50 ms
22 days agoHandshake completed75 ms
24 days agoHandshake completed914 ms
26 days agoHandshake completed1.19 s

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 Euipo and makes no claim about it beyond what these checks measured.