Skip to content
Forever In Our Hearts logo

Forever In Our Hearts MCP server

Which MCP servers are Forever In Our Hearts's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-29

← Back to Forever In Our Hearts

Whose server it is
  • Registry nameco.foreverinourhearts/memorialsverified in the MCP registry

The registry name sits under foreverinourhearts.co. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-29
  • Stateanswerschecked 2026-10-29
  • Tools5
  • Server calls itselfforever-in-our-hearts
  • Server version1.0.0
  • Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 475 ms.

Should an agent connect itSkip it
  • Its tools do none of the product's use cases we checked: write a life story and build a timeline of milestones; collect photos and messages from relatives and friends; share a memorial link or QR code on a headstone or plaque.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 7, the first on 2026-10-29
  • INITE MCP score65 of 100answers 100 · does the job 0 · definitions 100 · context 100 · use 0 · connects 100
  • What an agent can do with it0 of 3 use cases
  • Answered100% of days7 of 7 daily checks
  • Median first answer502 ms
  • Space in an agent's context≈ 1,032 tokensthe definitions of all its tools (5), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 5 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • cannot · write a life story and build a timeline of milestones
  • cannot · collect photos and messages from relatives and friends
  • cannot · share a memorial link or QR code on a headstone or plaque

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers5 tools · read 2026-10-29
  • 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.

  • 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.

  • 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.

  • 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.

  • 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.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

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

Add it

Claude Code, in a terminal

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

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.foreverinourhearts.co/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.