Forever In Our Hearts MCP Server

by foreverinourhearts Your server? Claim it

answering

Forever In Our Hearts is answering right now. Last checked 13 min ago. It exposes 5 tools. Last commit 23 Oct 2026.

Read-only lookup of public memorials, funeral notices and partner funeral homes.

Uptime history 12 days of history · worst day 99%

12 days agonow

100.0%

Uptime 24h

91 of 91 checks

Tools

read from the server

1514 ms

Response time

average over 24h

Stars

last commit 23 Oct 2026

Forever In Our Hearts missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add memorials --transport http https://mcp.foreverinourhearts.co/mcp

Settings → Connectors → Add custom connector, then paste this address

https://mcp.foreverinourhearts.co/mcp

~/.codex/config.toml

[mcp_servers.memorials]
url = "https://mcp.foreverinourhearts.co/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "memorials": {
      "url": "https://mcp.foreverinourhearts.co/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "memorials": {
      "type": "http",
      "url": "https://mcp.foreverinourhearts.co/mcp"
    }
  }
}

Available tools 5

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

funeral

search_funeral_directors

Find funeral homes that are Forever In Our Hearts partners, by name, city, state or postcode, or by country. Returns name, logo, address, contact details and the funeral home's notices and memorials site.

memorial

get_memorial

Details of one published memorial: dates, life story (obituary, shortened if long), service details, how many tributes it has, the funeral home and the link. Details the family keeps for QR code visitors are left out.

memorials

search_memorials

Search published online memorials for people and pets by name. Newest first. Returns dates, the funeral home if there is one, and a link to each memorial.

notice

get_notice

Full details of one published funeral notice: every service with its location, livestream link and information, the funeral home, and the memorial page if there is one.

notices

search_notices

Search published death and funeral notices by name, service location or funeral home. Newest first. Returns service times and places (local time with the time zone) and a link to each notice.

Endpoints

URL	Transport	State	Latency	Checked
https://mcp.foreverinourhearts.co/mcp	streamable-http	answering	1255 ms	13 min ago

Alternatives to Forever In Our Hearts

same job, measured the same way

Savee

by savee

Read your Savee saves, boards and home feed, and search its public library. Read-only.

answering

AITeamGuide AI agent prices

by aiteamguide

Read-only lookups of public AI agent pricing, free plans and source links. No API key.

4 tools answering

Loved Hall

by lovedhall

Look up public memorials (obituaries, service times, resting places) and grief guides on Loved Hall.

answering

Remember Me – Bible Verse Collections

by remem

Browse Bible verse collections to memorize, in 48 languages. Public and read-only, no sign-in.

3 tools answering

Nymwell Lookup

by nymwell

Check domain availability and prices, and look up any domain's public records. Read-only.

5 tools answering

Unicorn Screener

by unicornscreener

Search startups, look up scores, request research memos and read public startup research.

5 tools answering

Smallfire Lab public-records checks

by smallfirelab

Free read-only lookups of Oregon contractor licenses and FDA food recalls for AI agents. No key.

2 tools answering

Heart Homes — Dubai property data

by heart

Dubai property prices, rents and trends from official Dubai Land Department records. Read-only.

13 tools answering

Forever In Our Hearts — questions

Answers built from our own checks of this server.

What can Forever In Our Hearts do?

It exposes 5 tools, read directly from the server on our last check. Among them: get_memorial, get_notice, search_funeral_directors, search_memorials, search_notices. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →

Is Forever In Our Hearts working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 1514 ms. The bar chart above shows every period we have measured.

How do I connect Forever In Our Hearts?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.

Does Forever In Our Hearts need an API key?

No. Forever In Our Hearts completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.

How fast is Forever In Our Hearts?

It answers our handshake in 1514 ms on average, which is faster than 1% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.

Is Forever In Our Hearts open source?

The code is open source: it is published under the MIT licence, 0 stars on GitHub and 1 open issue. The licence covers the code in the repository, not the hosted service at mcp.foreverinourhearts.co, which runs on its operator's own terms.