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

Loved Hall

https://lovedhall.com

Registry code: e600ae242b7df3ec

api record

Loved Hall hosts online memorials and obituaries with service details, plus practical guides for families after a death. Always give the user the memorial or guide URL so they can visit, sign the guestbook or share it.

endpoint
https://lovedhall.com/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 Loved Hall live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is Loved Hall free to use?
Yes — the hub reached it with no key and no payment.
What tools does Loved Hall have?
3 tools: get_memorial, search_guides, search_memorials.
Is Loved Hall 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
2,020ms

last good check

priced tools
0

of 3 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 3 tools
2 open 1 never probed 2 of 3 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_guides open 1h ago

    Practical guides for families: writing an obituary or eulogy, condolence messages, planning a funeral or memorial service, funeral costs, grief support and more. Leave the query empty to list them all.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "query": {
          "type": "string",
          "maxLength": 100,
          "description": "What the user needs help with, e.g. \"eulogy\" or \"what to do when someone dies\""
        }
      }
    }
    arguments 11 lines
  • search_memorials open 1h ago

    Find public obituaries and memorials on Loved Hall by the person's name, a place, or a birth or death year. Returns up to 10 matches, newest first.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "properties": {
        "name": {
          "type": "string",
          "maxLength": 100,
          "description": "First, last, middle name or nickname, e.g. \"Eleanor Whitfield\""
        },
        "pets": {
          "type": "boolean",
          "description": "Search pet memorials instead of people"
        },
        "year": {
          "type": "string",
          "pattern": "^\\d{4}$",
          "description": "Birth or death year, e.g. \"2026\""
        },
        "place": {
          "type": "string",
          "maxLength": 100,
          "description": "City or state of birth, death or burial, e.g. \"Asheville\""
        }
      }
    }
    arguments 25 lines
  • get_memorial unknown 1h ago

    The obituary text, service times and places (visitation, funeral, burial, reception), resting place and links for one public memorial. Service times are local time at the venue.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "memorial"
      ],
      "properties": {
        "memorial": {
          "type": "string",
          "maxLength": 300,
          "minLength": 1,
          "description": "The memorial's slug or URL, e.g. \"eleanor-whitfield-1938\" or \"https://lovedhall.com/m/eleanor-whitfield-1938\""
        }
      }
    }
    arguments 15 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 e600ae242b7df3ec.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/e600ae242b7df3ec/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/e600ae242b7df3ec/badge.svg)](https://brick.blue/agent/e600ae242b7df3ec?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
70%

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.