All MCP Servers
AI & MemoryMCP Registryremote6 toolsD · 33

MemoryCareHomes MCP server

fyi.memorycarehomes · Updated

Licensed memory care homes in the UK and US.

At a glance

MemoryCareHomes is an MCP server in the AI & Memory category. It is hosted remotely and connects over HTTP, and declares no required credentials. It exposes 6 tools, including search_listings, get_listing and list_places. It scores D (33/100) on the MCP Skills Hub health score as of Oct 28, 2026.

Source

One-click install

Opens your editor and pre-fills the config. Your editor will ask before adding it.

How to install MemoryCareHomes in your AI client

Setup for Claude Code, Claude Desktop, Cursor, Codex, Windsurf, Cline and VS Code — copy-paste ready.

How to install MemoryCareHomes in Claude CodeAnthropic's agentic CLI

  1. Add the server

    bash
    claude mcp add --transport http memorycarehomes https://memorycarehomes.fyi/mcp
  2. Verify it's connected

    bash
    claude mcp list
  3. Sharing it with your team?

    Add `--scope project` to write it to .mcp.json in the repository root, which you can commit (with the secrets left as environment variables).

  4. Use it in a session

    Ask Claude to use the tools this server exposes (e.g. search_listings, get_listing, list_places). It discovers them automatically.

What tools does MemoryCareHomes expose? (6)

Read from the live server. Click any tool for its input schema.

  • search_listingsSearch published memory care homes by text, place and category.
  • get_listingGet one published memory care home by its slug.
  • list_placesList countries, regions and cities that have memory care homes.
  • list_categoriesList categories with their memory care home counts.
  • get_statsGet the number of published memory care homes, places and categories, and when the data last changed.
  • list_sourcesList where the memory care home data comes from, with the license and refresh of each source.

What the code can do

This is a remote server — nothing is installed or run on your machine, so there is no local code to analyze. What it can reach is described above: your requests go to the provider's host.

Before you install

Signals gathered from the source repo and package registry — not a safety verdict.

What it can reach

  • Third-party hosted service — Your requests and any data in them are sent to memorycarehomes.fyi.
  • No local execution — Nothing is installed or run on your machine.
  • No source repository — This registry entry does not link to a public repo, so its code cannot be reviewed before you install it.

Client compatibility

Claude Code: NativeClaude Desktop: Via mcp-remoteCursor: NativeCodex CLI: Via mcp-remoteWindsurf: NativeCline: NativeVS Code: Native

Health score

D · 33

Maintenance, adoption, transparency and packaging — not a safety audit. How this is calculated

  • Maintenance30%not measurable

    No commit history available.

  • Adoption20%not measurable

    No usage data available.

  • Transparency20%25%

    1/4: ✗ public source repo, ✗ declared license, ✗ documentation, ✓ discoverable tool list.

  • Provenance15%0%

    No source repository to trace the code back to.

  • Packaging15%75%

    Remote endpoint; authentication requirements not declared.

Maintain MemoryCareHomes? Add a badge to your README

Shows its health grade, and links readers to install steps for every client.

markdown
[![MemoryCareHomes on MCP Skills Hub](https://mcp-skills-hub.vercel.app/badge/fyi-memorycarehomes-memorycarehomes)](https://mcp-skills-hub.vercel.app/mcps/fyi-memorycarehomes-memorycarehomes)

Catalog data refreshed . Something wrong? Report it.