Remote MCP · Endpoint

Patent Search MCP server

No. Patent Search answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://patent.memoryapi.org/mcp

The last check completed an MCP handshake.

Registry name
org.memoryapi/patent
Transport
Streamable HTTP
Protocol negotiated
2024-11-05
Handshake latency
115 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Patent search and company IP portfolio data
Listing
From the official MCP registry (active).
Recent checks of Patent Search
CheckedResultHandshake
1 hour agoHandshake completed115 ms
1 day agoHandshake completed83 ms
3 days agoHandshake completed84 ms
3 days agoHandshake completed86 ms
4 days agoHandshake completed92 ms
5 days agoHandshake completed92 ms
7 days agoHandshake completed198 ms
10 days agoHandshake completed76 ms
12 days agoHandshake completed102 ms
15 days agoHandshake completed161 ms
17 days agoHandshake completed91 ms
19 days agoHandshake completed75 ms
21 days agoHandshake completed208 ms
23 days agoHandshake completed209 ms
25 days agoHandshake completed71 ms
26 days agoHandshake completed119 ms
28 days agoHandshake completed88 ms
29 days agoHandshake completed77 ms

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

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