Remote MCP · Endpoint

MyLastWill MCP server

No. MyLastWill answered an MCP handshake 34 minutes ago.

UpLast checked 34 minutes ago

Server URL

https://mylastwill.org/mcp

The last check completed an MCP handshake.

Registry name
org.mylastwill/mylastwill
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
119 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Free U.S. wills, codicils and charitable bequest wording, plus will-signing rules for every state.
Listing
From the official MCP registry (active).
Recent checks of MyLastWill
CheckedResultHandshake
34 minutes agoHandshake completed119 ms
3 days agoHandshake completed89 ms
13 days agoHandshake completed99 ms
13 days agoHandshake completed174 ms
15 days agoHandshake completed77 ms
16 days agoHandshake completed87 ms
17 days agoHandshake completed94 ms
18 days agoHandshake completed382 ms
18 days agoHandshake completed248 ms
20 days agoHandshake completed101 ms
22 days agoHandshake completed104 ms
25 days agoHandshake completed52 ms

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

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