MCP.Market

Forever In Our Hearts MCP server

online · 100% uptime
by foreverinourhearts.co·co.foreverinourhearts/memorials·v1.0.0
No reviews yet

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

A91/100grade A
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
A91/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Forever In Our Hearts yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Forever In Our Hearts tools (5)

write = sends, deletes, buys or posts
  • get_memorialFree

    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.

  • get_noticeFree

    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.

  • search_funeral_directorsFree

    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.

  • search_memorialsFree

    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.

  • search_noticesFree

    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.

Public scan report

scanner v0.1.10 · 2026-10-25 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 1692ms20/20
  • Tool poisoning5 tool descriptions checked15/15
  • Auth qualityopen endpoint, read-only tools10/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityendpoint served from the registry-verified namespace domain8/10
Overall 91/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Forever In Our Hearts compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
91/100
higher than 85% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote server answers 100%
Response time
1,746 ms
faster than 5% of 30,031 servers

What its tools let an agent do: 5 read

Install Forever In Our Hearts in Claude Code, Cursor or VS Code

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

What the publisher says

From the Forever In Our Hearts repository's README, as published. We do not edit it. Read it on GitHub

Forever In Our Hearts MCP Server

A public, read-only MCP server for online memorials and funeral notices from Forever In Our Hearts. AI assistants can look up a memorial, the time and place of a funeral, or a partner funeral home, and link to the page.

  • Page: https://foreverinourhearts.co/mcp
  • Server: https://mcp.foreverinourhearts.co/mcp (Streamable HTTP)
  • Free, no account or API key, read-only. 60 requests a minute per IP address

Tools

Every tool takes an optional region: global (foreverinourhearts.co: US, UK, Canada, Ireland, New Zealand and elsewhere), au (foreverinourhearts.com.au, Australia), or leave it out for both. Search tools take limit (up to 25) and page.

Only pages that are already public and allowed in search engines are returned. Details a family shows only to QR code visitors, email addresses and private messages are never returned.

Connect

Claude (web and desktop): Settings, Connectors, Add custom connector, then paste the server address.

Claude Code:

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

Other clients (VS Code, Cursor and similar):

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

Claude Code plugin (adds the server for you):

/plugin install forever-in-our-hearts --marketplace Forever-In-Our-Hearts/memorials-mcp-server

This repo is also a plugin for Grok Build and other clients that read .mcp.json and .claude-plugin/plugin.json.

Test it with the MCP Inspector: npx @modelcontextprotocol/inspector, transport Streamable HTTP, the URL above.

About

Forever In Our Hearts makes online memorial websites families pay for once, and branded notice and memorial pages for funeral homes. See foreverinourhearts.co and the Funeral Director Network.

License

MIT. See LICENSE. This covers the files in this repo; the server itself is operated by Forever In Our Hearts.

Nothing above is checked by us. What we check is on the safety report.

Forever In Our Hearts: common questions

Is Forever In Our Hearts MCP server safe?
Yes, by our scan: it is graded A (91/100). Read the Forever In Our Hearts safety report
How do I install Forever In Our Hearts?
It runs remotely at mcp.foreverinourhearts.co. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Forever In Our Hearts need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Forever In Our Hearts maintained?
The last commit was 13 days ago (2026-10-22). The latest release is v1.0.0.
Is Forever In Our Hearts up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
How does Forever In Our Hearts compare with other MCP servers?
safety score 91/100 (higher than 85% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.