Forever In Our Hearts logo

Forever In Our Hearts

Searches public memorials, funeral notices, services, and partner funeral homes through a read-only MCP connection.

Install Forever In Our Hearts

Pick your client, then add it in one click or paste the config.

Streamable HTTP (Remote)
Server URL
https://mcp.foreverinourhearts.co/mcp

Remote servers are added in the app, not the config file: Customize → Connectors → Add custom connector, then paste this URL.

Hosted endpointLive · under an hour agoLive Remote EndpointOur automated health check connected to this remote MCP endpoint successfully.Last checked under an hour ago · Nov 13, 2026, 23:45 UTC

Clients with native remote MCP support can connect directly to this URL.

Remote endpoint
https://mcp.foreverinourhearts.co/mcp

Overview

Forever In Our Hearts provides read-only MCP access to public memorials, funeral notices, and partner funeral homes. Its tools search notices and memorials, retrieve individual records, and locate participating funeral directors, returning service details and page links. The hosted endpoint uses Streamable HTTP and requires no account or API key. Use it when an assistant needs public bereavement information, funeral logistics, or funeral-home contact details.

Use cases

  • Find a published funeral notice by name or service location
  • Retrieve funeral times, venues, and livestream links
  • Look up a public memorial for a person or pet
  • Locate a partner funeral home and its contact details

Key features

  • Read-only access to public notices and memorials
  • Search by name, location, funeral home, or country
  • Individual notice and memorial lookups
  • Partner funeral-home directory search
  • Streamable HTTP endpoint with no API key
  • Regional search across global and Australian sites

Tools5

What Forever In Our Hearts lets your agent do. Expand a tool for its parameters.

Verified live~975 tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked

Recent health check succeeded.

5/5 checks healthy over the last 16d

What it can do

From the 5 tools this server returned when we ran it.

Read-only tools · 5

Observed 2026-10-28 in an isolated sandbox. A description of reach, not a security audit.

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

Last commit22d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Tools exposed5Callable tools this server registers over MCP.
Directory activity1 viewsConfig copies, upvotes, and views on AllMCPs.

How Forever In Our Hearts works

What Forever In Our Hearts does

Forever In Our Hearts exposes public content from Forever In Our Hearts through the Model Context Protocol. It covers published death and funeral notices, online memorials for people and pets, and funeral homes that participate in the Forever In Our Hearts network.

The service is read-only. It can return links to public pages, but it cannot create, edit, or remove notices, memorials, tributes, or funeral-home records. Results are limited to pages that are public and permitted to appear in search engines.

How it works

The hosted MCP endpoint is available at https://mcp.foreverinourhearts.co/mcp over Streamable HTTP. MCP-compatible clients send tool calls to that endpoint and receive structured search results or details for an individual record.

Search tools support pagination and a result limit of up to 25 items. An optional region value selects the global Forever In Our Hearts site, the Australian site, or both when omitted. Global coverage includes the United States, United Kingdom, Canada, Ireland, New Zealand, and other locations served by that site.

Requests are limited to 60 per minute for each IP address. The service is free to use and does not require an account or API key.

Setup and configuration

In Claude, add a custom connector in Settings and use the hosted server URL. Claude Code can register the endpoint with:

Terminal
claude mcp add --transport http forever-in-our-hearts https://mcp.foreverinourhearts.co/mcp

For clients such as VS Code or Cursor, add an HTTP MCP server entry similar to:

config.json
{
  "mcpServers": {
    "forever-in-our-hearts": {
      "type": "http",
      "url": "https://mcp.foreverinourhearts.co/mcp"
    }
  }
}

A Claude Code plugin is also available through the Forever-In-Our-Hearts/memorials-mcp-server marketplace. The endpoint can be tested with MCP Inspector by selecting Streamable HTTP and entering the server URL.

Tools and capabilities

  • search_notices finds published death and funeral notices by name, service location, or funeral home, ordered newest first.
  • get_notice retrieves one notice by ID or link, including services, locations, local times and time zones, livestream links, notes, the funeral home, and a related memorial page when available.
  • search_memorials searches published memorials for people and pets by name and returns dates, links, and associated funeral-home information when present.
  • get_memorial returns an individual memorial’s dates, life story, service information, tribute count, funeral home, and page link.
  • search_funeral_directors locates partner funeral homes by name, city or town, state, postcode, or country, with address, contact details, logo, and related notices and memorials site information.

Limitations and notes

The server returns public material only. Information intended solely for QR-code visitors is excluded from memorial results, as are email addresses and private messages. Long life stories may be shortened in get_memorial results.

Search and detail results can include livestream links and service times, with times presented in the relevant local time zone. Availability depends on the selected region and on whether the underlying page is publicly searchable. The repository is licensed under MIT, while the hosted server is operated by Forever In Our Hearts.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Forever In Our Hearts

Forever In Our Hearts is an MCP server that connects AI assistants to public memorials, funeral notices, and partner funeral homes through read-only search and detail tools. It supports notice and memorial searches, individual record lookups, and funeral-home discovery, returning links and relevant service information.

Add `https://mcp.foreverinourhearts.co/mcp` as a Streamable HTTP MCP server. Claude users can add it as a custom connector, while Claude Code can run `claude mcp add --transport http forever-in-our-hearts https://mcp.foreverinourhearts.co/mcp`. VS Code and Cursor can use an HTTP server entry.

No, Forever In Our Hearts requires neither an account nor an API key. The hosted read-only endpoint is free to use, with a limit of 60 requests per minute for each IP address.

Yes, Forever In Our Hearts works with Cursor through its Streamable HTTP endpoint. Add the server URL as an HTTP MCP server using the name `forever-in-our-hearts`.

It returns public notices, memorial details, funeral services, livestream links, page links, and partner funeral-home information. Private messages, email addresses, and details reserved for QR-code visitors are excluded.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewForever In Our Hearts AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/forever-in-our-hearts?style=directory)](https://allmcps.com/mcp/forever-in-our-hearts)
HTML Embed
<a href="https://allmcps.com/mcp/forever-in-our-hearts"><img src="https://allmcps.com/api/badge/forever-in-our-hearts?style=directory" alt="Forever In Our Hearts on AllMCPs" /></a>