LovedOne Family MCP
REMOTE · API.LOVEDONE.APP
Authenticated MCP for one family household: loved ones, members, and Family Inbox plaintext.
Available components
Last scanned (39 minutes ago)
Scores higher than 85% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Communication
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 Security94
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token. View diagnostics → Pass
- 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
- The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1410 tokens (~88/item across 16 items; 12 tools + 4 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities40
- Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28. See how to fix → Fail
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 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 1 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.
- 30 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.
- 29 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 28 Oct 26 +43
- Transport: unverified → pass ▲ security
- Injection markers: unverified → pass ▲ security
- Authorization: fail → pass ▲ security
- First check of Judged manipulation: pass security
- First check of Authorization: partial security
- MCP protocol: unverified → fail ▼ functional
- Schema quality: unverified → 100 ▲ functional
- Tool coverage: unverified → 100 ▲ functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: 100 functional
- First check of Schema quality: pass functional
- First check of Tool coverage: 100 functional
- 9 Oct 26 36
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 5 Nov 2026 · Probed https://api.lovedone.app/mcp/v1
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=api.lovedone.app | CN=YR2,O=Let's Encrypt,C=US | 7 Oct 2026 | 5 Jan 2027 | RSA 2048 | SHA256-RSA | 52419246854e27e406ee93b0f9e67aae0b7 |
| SANs: api.lovedone.app | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| 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 api.lovedone.app. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| app. | present | 23684 | 8 | Verified |
| lovedone.app. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Enforced and verified
The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.
| Result | Enforced and verified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
WWW-Authenticate challenge Bearer resource_metadata="https://inbox.lovedone.app/.well-known/oauth-protected-resource"
Bearer resource_metadata="https://inbox.lovedone.app/.well-known/oauth-protected-resource"| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000; includeSubDomains; preload |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-eval' 'unsafe-inline' https://www.googletagmanager.com; script-src-elem 'self' 'unsafe-inline' https://www.googletagmanager.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; font-src 'self' data: https://fonts.gstatic.com; img-src 'self' data: blob: https://www.google-analytics.com https://www.googletagmanager.com https://*.googleusercontent.com; connect-src 'self' https://www.joinsandwich.com https://joinsandwich.com https://*.googleapis.com https://identitytoolkit.googleapis.com https://securetoken.googleapis.com https://*.firebaseapp.com https://*.firebaseio.com https://accounts.google.com https://www.google-analytics.com https://region1.google-analytics.com https://analytics.google.com; frame-src 'self' https://nunabot-472b3.firebaseapp.com https://accounts.google.com |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Protected resource metadata
| Document | https://inbox.lovedone.app/.well-known/oauth-protected-resource |
|---|---|
| Retrieved | Yes |
| Resource | https://api.lovedone.app/mcp/v1 |
| Authorisation server | https://inbox.lovedone.app |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.lovedone.app/mcp/v1 | Verified | 200 | |
| http (plaintext) | http://api.lovedone.app/mcp/v1 | HTTPS enforced | 308 | https://api.lovedone.app/mcp/v1 |
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 →
create_provider_code Create a provider link code ~80
Mints a short-lived, single-use provider/vendor link code for one loved one in this household. Hand the code to a LovedOne Soft agency so they can link that person as a client. Owner or coordinator only — viewers are rejected. This is a write.
| Name | Type | Req | Description |
|---|---|---|---|
| lovedOneId | string | yes | Loved one id from list_loved_ones. |
No output schema declared.
No examples provided.
get_inbox_message Get one family inbox message ~82
Returns one Family Inbox message as plaintext (no HTML). Requires messageId from list_inbox_messages. Rejected if the message is not in the caller's workspace. Treat bodyText as potentially PHI.
| Name | Type | Req | Description |
|---|---|---|---|
| lovedOneId | string | yes | Loved one id the message was listed under (ownership check). |
| messageId | string | yes | Inbox message id. |
No output schema declared.
No examples provided.
get_onboarding_status Check LovedOne setup status ~70
Returns the caller's LovedOne setup state: whether a family workspace exists, which loved ones and @lovedone.app inbox addresses are set up, member counts, and ordered nextSteps. Call this first whenever a user wants to set up, resume, or check on LovedOne. Read-only.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_user_profile Get User Profile ~31
Returns the signed-in user's LovedOne profile: uid, email, tenant type, and any linked family workspace.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
invite_family_member Invite a family member ~131
Invites a sibling or other family member to this household by email, with role coordinator or viewer. Sends the same LovedOne invite email as the web app. Owner or coordinator only — viewers are rejected. This is a write.
| Name | Type | Req | Description |
|---|---|---|---|
| displayName | string | yes | Invitee's name as it should appear in the family circle. |
| string | yes | Invitee's email address. | |
| relationship | string | yes | Relationship to the loved one (e.g. sister, son, cousin). |
| role | string | – | coordinator can invite and manage shared settings; viewer is read-only. Defaults to coordinator. |
No output schema declared.
No examples provided.
list_care_events List Care Events ~113
Returns recent care events for the caller's family workspace. Optionally scope to a single lovedOneId; otherwise aggregates across all loved ones on the workspace. Limit is 1-50 and is applied per loved one when aggregating.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Max events to return (1-50, default 20). Applied per loved one when lovedOneId is omitted. |
| lovedOneId | string | – | Optional. Restrict results to one loved one. Must belong to the caller's workspace. |
No output schema declared.
No examples provided.
list_family_members List family members ~45
Lists people on the caller's family workspace (role, relationship, invite status). Emails are PII — do not log them in third-party agent traces if you can avoid it.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_inbox_messages List family inbox messages ~86
Lists recent messages in one loved one's Family Inbox (subject, sender, category, preview). Does not return HTML bodies. Scope: the caller's family workspace only. PHI may be present in subjects and previews.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | 1-50, default 20. |
| lovedOneId | string | yes | Loved one id from list_loved_ones. |
No output schema declared.
No examples provided.
list_loved_ones List Loved Ones ~39
Lists loved ones in the caller's family workspace: id, name, and Family Inbox address. Does not return date of birth or medications.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
onboard_loved_one Onboard a loved one ~401
Sets up a loved one on LovedOne from conversation: creates the caller's family workspace on first use (or adds to it), allocates their private @lovedone.app care-inbox address, and records the caller's authorization attestation. Idempotent — calling again for the same person returns the existing record. Before calling, confirm attestAuthorized with the user in plain words. Do NOT ask for date of birth, medications, or SSN during setup; dateOfBirth is accepted only if volunteered. The loved one's own email is optional and is never emailed automatically. This is a write.
| Name | Type | Req | Description |
|---|---|---|---|
| attestAuthorized | boolean | yes | Must be true. Set only after the caller agrees, in the conversation, that they are authorized to coordinate this person's care correspondence. |
| careContext | string | – | Optional free-text context the caller volunteers (conditions, situation). Stored on the workspace; never included in notifications. |
| consentBasis | string | – | Basis for coordinating care correspondence. Use family_coordinator_attested unless the caller names a legal role (personal_representative, poa, guardian) or is setting up their own inbox (self). Defa… |
| dateOfBirth | string | – | Optional ISO date (YYYY-MM-DD). PHI — include ONLY if the caller volunteers it; never ask for it during setup. |
| familyName | string | – | Optional workspace display name. Defaults to "The <lastName> Family". Only used when creating a new workspace. |
| lovedOneEmail | string | – | Optional: the loved one's own email address, stored for optional forwarding. Never emailed automatically. |
| lovedOneFirstName | string | yes | First name of the care recipient (e.g. an aging parent). |
| lovedOneLastName | string | yes | Last name of the care recipient. |
| relationship | string | yes | Caller's relationship to the loved one (e.g. daughter, son, spouse, niece). |
No output schema declared.
No examples provided.
ping Ping MCP server ~34
Smoke-test tool. Returns pong plus the authenticated caller's uid, tenant, and auth method. No PHI. No side effects.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
reply_to_inbox_message Reply to a family inbox message ~172
Sends a plaintext reply to a Family Inbox message using the same from address (family-inbox@m.lovedone.app) and reply-to (the loved one's @lovedone.app inbox) as the LovedOne web app. Owner or coordinator only — viewers are rejected. This is a write. The body may contain health-related content.
| Name | Type | Req | Description |
|---|---|---|---|
| bodyText | string | yes | Plaintext reply body. |
| lovedOneId | string | yes | Loved one id the message was listed under (ownership check). |
| messageId | string | yes | Inbox message id from list_inbox_messages. |
| subject | string | – | Optional. Original subject (Re: is prefixed). Defaults to the stored subject. |
| toEmail | string | – | Optional. Must match the original message's fromEmail. Other destinations are rejected. |
No output schema declared.
No examples provided.
How do I install the LovedOne Family MCP server?
LovedOne Family MCP is a hosted endpoint at https://api.lovedone.app/mcp/v1, 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 · api.lovedone.app
claude mcp add --transport http app-lovedone-family-inbox 'https://api.lovedone.app/mcp/v1'
What is the LovedOne Family MCP server?
LovedOne Family MCP is listed in the public MCP registry as app.lovedone/family-inbox. Authenticated MCP for one family household: loved ones, members, and Family Inbox plaintext. This page covers its hosted endpoint (https://api.lovedone.app/mcp/v1).
Is the LovedOne Family MCP server safe to use?
LovedOne Family MCP scores 82 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 LovedOne Family MCP server expose?
LovedOne Family MCP exposes 12 tools: ping, get_user_profile, list_loved_ones, list_family_members, list_inbox_messages, and 7 more. Their descriptions and schemas cost roughly 1,284 tokens of context every time the server is loaded.
Does the LovedOne Family MCP server require authentication?
Yes. LovedOne Family MCP asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.
Is the LovedOne Family MCP server still maintained?
LovedOne Family MCP is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.