Remote MCP · Endpoint

Jpo Patent Info MCP server

No. Jpo Patent Info answered an MCP handshake 7 hours ago.

UpLast checked 7 hours ago

Server URL

https://gateway.pipeworx.io/jpo-patent-info/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/jpo-patent-info
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
36 ms
Tools exposed
46 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
JPO patent information: Japanese patent, utility model and trademark status from the Japan Patent…
Listing
From the official MCP registry (active).
Recent checks of Jpo Patent Info
CheckedResultHandshake
7 hours agoHandshake completed36 ms
4 days agoHandshake completed47 ms
14 days agoHandshake completed123 ms
15 days agoHandshake completed199 ms
16 days agoHandshake completed120 ms
17 days agoHandshake completed243 ms
19 days agoHandshake completed95 ms
19 days agoHandshake completed150 ms
20 days agoHandshake completed120 ms
21 days agoHandshake completed67 ms
23 days agoHandshake completed742 ms
26 days agoHandshake completed849 ms
28 days agoHandshake completed1.66 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 Jpo Patent Info and makes no claim about it beyond what these checks measured.