CareOpenly - Find Senior Living Communities
REMOTE · MCP.CAREOPENLY.COM
Find U.S. senior living communities, public prices, reviews and licensing records.
Available components
Last scanned (20 hours ago)
Scores higher than 69% of remote servers
Reachable. Last reached 4 Nov 2026.
Category Health and Science
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 556 tokens (~111/item across 5 items; 2 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage95
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 83% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (2026-07-28).Pass
- Supports UI / widget rendering.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 2 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 31 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 74
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Nov 2026 · Probed https://mcp.careopenly.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mcp.careopenly.com | CN=YR1,O=Let's Encrypt,C=US | 8 Oct 2026 | 6 Jan 2027 | RSA 2048 | SHA256-RSA | 55f286f9147bb74ed62e44e21b76623c30e |
| SANs: mcp.careopenly.com | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of mcp.careopenly.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| careopenly.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000; includeSubDomains |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.careopenly.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.careopenly.com/mcp | HTTPS enforced | 308 | https://mcp.careopenly.com/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_facility Get CareOpenly facility details ~217
Public, read-only details for a named senior living facility or its stable publicId, without a CareOpenly account. Relevant to questions about a specific community's care types, published starting and care-specific prices, floor plans, room types, reviews, amenities, services, coverage evidence, licensing, and inspections. Name lookup identifies the matched facility and reports unresolved ambiguity. Available records include sources and dates; missing fields remain unavailable. Prices are observations rather than quotes, and coverage records do not determine individual benefits. Results include a CareOpenly link for requesting information.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | – | City mentioned by the user, to improve name matching. |
| include | array | – | Extra structured sections relevant to the user's question. Core price, floor plan, and review summaries are always returned. |
| name | string | – | Facility name when its publicId is unavailable. |
| publicId | string | – | Stable facility ID from a search result. |
| stateCode | string | – | Two-letter state code mentioned by the user, to improve name matching. |
| Name | Type | Req | Description |
|---|---|---|---|
| candidates | array | – | – |
| detailUrl | string | – | – |
| message | string | – | – |
| name | string | – | – |
| publicId | string | – | – |
| requestInformationUrl | string | – | – |
| status | string | yes | – |
No examples provided.
search_facilities Search senior living communities ~243
Public, read-only search for senior living communities by city, ZIP code, hospital, neighborhood, landmark, or verified coordinates, without a CareOpenly account. Relevant to questions about assisted living, memory care, independent living, 55+ communities, and other care types in or near a place. An exact city or ZIP with no radius uses its city inventory; a landmark search defaults to 15 miles. Results include stable facility IDs, care types, links, and available published prices and reviews.
| Name | Type | Req | Description |
|---|---|---|---|
| careCategory | string | – | Senior living, assisted living, memory care, independent living, or 55+ community type. |
| destination | string | yes | City, ZIP code, neighborhood, hospital, landmark, or CareOpenly city ID. CareOpenly resolves the place. |
| latitude | number | – | Optional verified latitude for a nearby search. |
| longitude | number | – | Optional verified longitude for the same nearby search. |
| page | integer | – | – |
| pageSize | integer | – | – |
| radiusMiles | number | – | Nearby radius in miles. An omitted radius uses exact city inventory for cities and ZIPs, and 15 miles for other places. |
| Name | Type | Req | Description |
|---|---|---|---|
| center | object | – | – |
| choices | array | – | – |
| location | object | – | – |
| message | string | – | – |
| page | integer | – | – |
| placeLabel | string | – | – |
| radiusMiles | number | – | – |
| results | array | – | – |
| searchMode | string | – | – |
| searchUrl | string | – | – |
| status | string | yes | – |
| total | integer | – | – |
| totalPages | integer | – | – |
No examples provided.
How do I install the CareOpenly - Find Senior Living Communities MCP server?
CareOpenly - Find Senior Living Communities is a hosted endpoint at https://mcp.careopenly.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · mcp.careopenly.com
claude mcp add --transport http leo9-careopenly 'https://mcp.careopenly.com/mcp'
What is the CareOpenly - Find Senior Living Communities MCP server?
CareOpenly - Find Senior Living Communities is an MCP server listed in the public MCP registry as io.github.leo9/careopenly. Find U.S. senior living communities, public prices, reviews and licensing records. This page covers its hosted endpoint (https://mcp.careopenly.com/mcp).
Is the CareOpenly - Find Senior Living Communities MCP server safe to use?
CareOpenly - Find Senior Living Communities scores 77 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the CareOpenly - Find Senior Living Communities MCP server expose?
CareOpenly - Find Senior Living Communities exposes 2 tools: search_facilities, get_facility. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.
Does the CareOpenly - Find Senior Living Communities MCP server require authentication?
No. We connected to CareOpenly - Find Senior Living Communities without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the CareOpenly - Find Senior Living Communities MCP server still maintained?
CareOpenly - Find Senior Living Communities is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.