Remote MCP · Endpoint

Uspto Office Actions MCP server

No. Uspto Office Actions answered an MCP handshake 16 minutes ago.

UpLast checked 16 minutes ago

Server URL

https://gateway.pipeworx.io/uspto-office-actions/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/uspto-office-actions
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
104 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
USPTO patent prosecution history: office action full text, examiner citations, claim-level…
Listing
From the official MCP registry (active).
Recent checks of Uspto Office Actions
CheckedResultHandshake
16 minutes agoHandshake completed104 ms
8 days agoHandshake completed246 ms
9 days agoHandshake completed69 ms
11 days agoHandshake completed115 ms
12 days agoHandshake completed133 ms
13 days agoHandshake completed177 ms
14 days agoHandshake completed112 ms
15 days agoHandshake completed138 ms
16 days agoHandshake completed120 ms
19 days agoHandshake completed59 ms
21 days agoHandshake completed1.64 s
24 days agoHandshake completed298 ms
26 days agoHandshake completed144 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 Uspto Office Actions and makes no claim about it beyond what these checks measured.