_ registry / mcp streamable-http · checked 2h ago

forever-in-our-hearts

https://mcp.foreverinourhearts.co

Registry code: 13f97d6d3b3de2c1

api record

Public online memorials, death and funeral notices, and partner funeral homes from Forever In Our Hearts (foreverinourhearts.co for the US, UK, Canada, Ireland, New Zealand and other countries; foreverinourhearts.com.au for Australia). Read-only. Only pages the family or funeral home published and allowed in search engines are returned. Link people to the `url` of each result. Families create memorials at https://hub.foreverinourhearts.co.

endpoint
https://mcp.foreverinourhearts.co/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is forever-in-our-hearts live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is forever-in-our-hearts free to use?
Yes — the hub reached it with no key and no payment.
What tools does forever-in-our-hearts have?
5 tools: get_notice, get_memorial, search_memorials, search_funeral_directors, search_notices.
Is forever-in-our-hearts safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
894ms

last good check

priced tools
0

of 5 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 5 tools
3 open 2 never probed 3 of 5 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_memorials open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "description": "Name of the person (first name, last name or both)"
    },
    "page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page number, starting at 1"
    },
    "type": {
      "enum": [
        "person",
        "pet"
      ],
      "type": "string",
      "description": "Memorials for people or for pets. Omit for both"
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Results per page, 1 to 25 (default 10)"
    },
    "region": {
      "enum": [
        "au",
        "global"
      ],
      "type": "string",
      "description": "\"au\" for Australia (foreverinourhearts.com.au), \"global\" for every other country (foreverinourhearts.co). Omit to search both"
    }
  }
}
    arguments 39 lines
  • search_funeral_directors open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page number, starting at 1"
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Results per page, 1 to 25 (default 10)"
    },
    "query": {
      "type": "string",
      "maxLength": 100,
      "description": "Funeral home name, city, state or postcode"
    },
    "region": {
      "enum": [
        "au",
        "global"
      ],
      "type": "string",
      "description": "\"au\" for Australia (foreverinourhearts.com.au), \"global\" for every other country (foreverinourhearts.co). Omit to search both"
    },
    "country": {
      "type": "string",
      "pattern": "^[A-Za-z]{2}$",
      "description": "Two-letter country code, for example NZ, GB, US, CA, IE or AU"
    }
  }
}
    arguments 36 lines
  • search_notices open 2h ago

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "name": {
      "type": "string",
      "maxLength": 100,
      "description": "Name of the person (first name, last name or both)"
    },
    "page": {
      "type": "integer",
      "maximum": 100,
      "minimum": 1,
      "description": "Page number, starting at 1"
    },
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Results per page, 1 to 25 (default 10)"
    },
    "region": {
      "enum": [
        "au",
        "global"
      ],
      "type": "string",
      "description": "\"au\" for Australia (foreverinourhearts.com.au), \"global\" for every other country (foreverinourhearts.co). Omit to search both"
    },
    "location": {
      "type": "string",
      "maxLength": 100,
      "description": "Town, suburb, city or venue of the service"
    },
    "funeral_home": {
      "type": "string",
      "maxLength": 100,
      "description": "Name of the funeral home"
    }
  }
}
    arguments 41 lines
  • get_notice unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 300,
      "description": "Notice id from search_notices, or the notice's link"
    }
  }
}
    arguments 14 lines
  • get_memorial unknown never probed

    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.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "id"
  ],
  "properties": {
    "id": {
      "type": "string",
      "maxLength": 300,
      "description": "Memorial id from search_memorials, the memorial's link, or the last part of it (for example \"example\" in /memorials/example)"
    },
    "region": {
      "enum": [
        "au",
        "global"
      ],
      "type": "string",
      "description": "\"au\" for Australia (foreverinourhearts.com.au), \"global\" for every other country (foreverinourhearts.co). Omit to search both"
    }
  }
}
    arguments 22 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 13f97d6d3b3de2c1.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/13f97d6d3b3de2c1/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/13f97d6d3b3de2c1/badge.svg)](https://brick.blue/agent/13f97d6d3b3de2c1?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
90%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.