Remote MCP · Endpoint

MemoryCareHomes MCP server

No. MemoryCareHomes answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://memorycarehomes.fyi/mcp

The last check completed an MCP handshake.

Registry name
fyi.memorycarehomes/memorycarehomes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
145 ms
Tools exposed
11 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Licensed memory care homes in the UK and US.
Listing
From the official MCP registry (active).
Recent checks of MemoryCareHomes
CheckedResultHandshake
2 hours agoHandshake completed145 ms
1 day agoHandshake completed505 ms
3 days agoHandshake completed2.36 s
3 days agoHandshake completed124 ms
4 days agoHandshake completed100 ms
5 days agoHandshake completed136 ms
7 days agoHandshake completed2.59 s
10 days agoHandshake completed1.72 s
12 days agoHandshake completed180 ms
15 days agoHandshake completed204 ms
17 days agoHandshake completed295 ms
19 days agoHandshake completed1.43 s
21 days agoHandshake completed1.05 s
23 days agoHandshake completed102 ms
25 days agoHandshake completed257 ms

The last 15 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 15.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with MemoryCareHomes and makes no claim about it beyond what these checks measured.