Remote MCP · Endpoint

Forever In Our Hearts MCP server

No. Forever In Our Hearts answered an MCP handshake 30 minutes ago.

UpLast checked 30 minutes ago

Server URL

https://mcp.foreverinourhearts.co/mcp

The last check completed an MCP handshake.

Registry name
co.foreverinourhearts/memorials
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
791 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only lookup of public memorials, funeral notices and partner funeral homes.
Listing
From the official MCP registry (active).
Recent checks of Forever In Our Hearts
CheckedResultHandshake
30 minutes agoHandshake completed791 ms
3 days agoHandshake completed679 ms
13 days agoHandshake completed630 ms
14 days agoHandshake completed678 ms
15 days agoHandshake completed636 ms
16 days agoHandshake completed634 ms
17 days agoHandshake completed671 ms
18 days agoHandshake completed642 ms
19 days agoHandshake completed624 ms
20 days agoHandshake completed662 ms
22 days agoHandshake completed644 ms
25 days agoHandshake completed669 ms
27 days agoHandshake completed636 ms

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

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