Remote MCP · Endpoint
io.github.engrossa/ipnex MCP server
No. io.github.engrossa/ipnex answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.ipnex.ai/mcp
The last check completed an MCP handshake.
- Registry name
- io.github.engrossa/ipnex
- Transport
- Streamable HTTP
- Protocol negotiated
- 2024-11-05
- Handshake latency
- 294 ms
- Tools exposed
- 2 tools
- Uptime, last 30 days
- 100% from 18 checks
- Described by its publisher as
- Cited, confidence-stamped patent intelligence over US university tech-transfer out-licensing.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 294 ms |
| 1 day ago | Handshake completed | 142 ms |
| 2 days ago | Handshake completed | 161 ms |
| 3 days ago | Handshake completed | 334 ms |
| 4 days ago | Handshake completed | 129 ms |
| 5 days ago | Handshake completed | 137 ms |
| 6 days ago | Handshake completed | 328 ms |
| 9 days ago | Handshake completed | 291 ms |
| 12 days ago | Handshake completed | 131 ms |
| 14 days ago | Handshake completed | 162 ms |
| 16 days ago | Handshake completed | 305 ms |
| 18 days ago | Handshake completed | 219 ms |
| 20 days ago | Handshake completed | 477 ms |
| 22 days ago | Handshake completed | 156 ms |
| 24 days ago | Handshake completed | 121 ms |
| 26 days ago | Handshake completed | 145 ms |
| 27 days ago | Handshake completed | 144 ms |
| 29 days ago | Handshake completed | 133 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 io.github.engrossa/ipnex and makes no claim about it beyond what these checks measured.