Remote MCP · Endpoint

Menlo MCP server

No. Menlo answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.menloinsurance.com/mcp

The last check completed an MCP handshake.

Registry name
com.menloinsurance/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
177 ms
Tools exposed
12 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Complete a Menlo application, authorize carrier quote requests and answer quote follow-ups.
Listing
From the official MCP registry (active).
Recent checks of Menlo
CheckedResultHandshake
1 hour agoHandshake completed177 ms
2 days agoHandshake completed334 ms
4 days agoHandshake completed194 ms
6 days agoHandshake completed220 ms
8 days agoHandshake completed168 ms
10 days agoHandshake completed164 ms
12 days agoHandshake completed317 ms
14 days agoHandshake completed2.63 s
15 days agoHandshake completed175 ms
17 days agoHandshake completed181 ms
18 days agoHandshake completed216 ms
20 days agoHandshake completed234 ms
22 days agoHandshake completed502 ms
24 days agoHandshake completed1.63 s

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