Skip to content
MemoryCareHomes logo

MemoryCareHomes MCP server

Which MCP servers are MemoryCareHomes'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-27

← Back to MemoryCareHomes

Whose server it is
  • Registry namefyi.memorycarehomes/memorycarehomesverified in the MCP registry

The registry name sits under memorycarehomes.fyi. 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-27
  • Stateanswerschecked 2026-10-27
  • Tools6
  • Server calls itselfmemorycarehomes
  • Server version1
  • Protocol version2025-06-18

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

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

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: 8, the first on 2026-10-27
  • INITE MCP score100 of 100answers 100 · definitions 100 · context 100 · connects 100
  • Answered100% of days8 of 8 daily checks
  • Median first answer275 ms
  • Space in an agent's context≈ 865 tokensthe definitions of all its tools (9), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results0 of 9 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · check a care home's licence on the public register
  • not sure · compare memory care homes by location and licence type
  • cannot · read inspection records before visiting a home

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 offers6 tools · read 2026-10-27
  • search_listings

    Search published memory care homes by text, place and category.

  • get_listing

    Get one published memory care home by its slug.

  • list_places

    List countries, regions and cities that have memory care homes.

  • list_categories

    List categories with their memory care home counts.

  • get_stats

    Get the number of published memory care homes, places and categories, and when the data last changed.

  • list_sources

    List where the memory care home data comes from, with the license and refresh of each source.

How to connect

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

{
  "mcpServers": {
    "memorycarehomes": {
      "type": "http",
      "url": "https://memorycarehomes.fyi/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http memorycarehomes https://memorycarehomes.fyi/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://memorycarehomes.fyi/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.