Remote MCP · Endpoint

Insuro MCP server

No. Insuro answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://mcp.insuro.com.au/

The last check completed an MCP handshake.

Registry name
au.com.insuro/insuro
Transport
Streamable HTTP
Protocol negotiated
2025-11-25
Handshake latency
457 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Free insurance vault MCP: OAuth policies, renewals, coverage Q&A, file PDFs. Global; not advice.
Listing
From the official MCP registry (active).
Recent checks of Insuro
CheckedResultHandshake
9 hours agoHandshake completed457 ms
2 days agoHandshake completed264 ms
4 days agoHandshake completed210 ms
5 days agoHandshake completed235 ms
7 days agoHandshake completed191 ms
8 days agoHandshake completed246 ms
9 days agoHandshake completed372 ms
12 days agoHandshake completed252 ms
14 days agoHandshake completed184 ms
15 days agoHandshake completed321 ms
16 days agoHandshake completed245 ms
18 days agoHandshake completed167 ms
19 days agoHandshake completed204 ms
19 days agoHandshake completed143 ms
20 days agoHandshake completed257 ms
21 days agoHandshake completed292 ms
23 days agoHandshake completed227 ms

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

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