Best Alternatives to Forever In Our Hearts
Looking for an alternative to Forever In Our Hearts? Whether you need a different runtime environment, custom authentication support, or alternative API integrations in the Developer Tools ecosystem, we have cataloged and compared the top alternative MCP servers below.
Forever In Our Hearts Overview
Forever In Our Hearts provides read-only MCP access to public memorials, funeral notices, and partner funeral homes. Its tools search notices and memorials, retrieve individual records, and locate participating funeral directors, returning service details and page links. The hosted endpoint uses Streamable HTTP and requires no account or API key. Use it when an assistant needs public bereavement information, funeral logistics, or funeral-home contact details.
- Find a published funeral notice by name or service location
- Retrieve funeral times, venues, and livestream links
- Look up a public memorial for a person or pet
- Locate a partner funeral home and its contact details
Specification Matrix: Forever In Our Hearts vs Alternatives
Direct comparison of key metrics, runtimes, authentication methods, and community popularity.
| Server Name | Runtime | Auth | Pricing | GitHub Stars | Downloads | Action |
|---|---|---|---|---|---|---|
| Streamable HTTP (Remote) | No auth required | Free | β | β | Current | |
| npx | No auth required | Free | 836 | β | ||
| npx | β | β | 1,987 | β | ||
A Azure DevOps (ADO) | npx | β | Free | 2,086 | β | |
| npx | OAuth | β | 329 | β | ||
| npx | API key | Bring your own API key (usage-based cost) | 36,928 | 3 | ||
| npx | β | β | 29,259 | β | ||
| npx | No auth required | Free | 4,693 | β | ||
| npx | OAuth | β | 197 | β | ||
| npx | No auth required | Free | 225 | β | ||
| npx | API key | Bring your own API key (usage-based cost) | 28,359 | β | ||
| npx | API key | Free | 94 | β | ||
| npx | No auth required | β | 118 | β |