Remote MCP · Endpoint

Impri MCP server

No. Impri answered an MCP handshake 57 minutes ago.

UpLast checked 57 minutes ago

Server URL

https://api.impri.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.sekera-radim/impri
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Impri MCP server — human-in-the-loop approval inbox for AI agents
Listing
From the official MCP registry (active).
Recent checks of Impri
CheckedResultHandshake
57 minutes agoHandshake completed224 ms
13 hours agoHandshake completed136 ms
1 day agoHandshake completed212 ms
2 days agoHandshake completed123 ms
4 days agoHandshake completed126 ms
7 days agoHandshake completed125 ms
9 days agoHandshake completed119 ms
12 days agoHandshake completed133 ms
14 days agoHandshake completed126 ms
16 days agoHandshake completed126 ms
18 days agoHandshake completed132 ms
20 days agoHandshake completed144 ms
22 days agoHandshake completed123 ms
23 days agoHandshake completed125 ms

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

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