# LovedOne Family MCP (remote · api.lovedone.app)

Authenticated MCP for one family household: loved ones, members, and Family Inbox plaintext.

- Trust score: 82/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `api.lovedone.app`: 82/100 (this document), [markdown](https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1.md), [page](https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1)

## Channel facts

- Endpoint: `https://api.lovedone.app/mcp/v1`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.4.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 94/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - 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.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 86/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1410 tokens (~88/item across 16 items; 12 tools + 4 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.
  - An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 40/100
  - Spec-recency check failed: implements MCP spec 2025-03-26; the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http app-lovedone-family-inbox 'https://api.lovedone.app/mcp/v1'
```

### Cursor

```json
{
  "mcpServers": {
    "app-lovedone-family-inbox": {
      "url": "https://api.lovedone.app/mcp/v1"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "app-lovedone-family-inbox": {
      "type": "http",
      "url": "https://api.lovedone.app/mcp/v1"
    }
  }
}
```

### Codex

```toml
[mcp_servers.app-lovedone-family-inbox]
url = "https://api.lovedone.app/mcp/v1"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "app-lovedone-family-inbox": {
      "type": "remote",
      "url": "https://api.lovedone.app/mcp/v1",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add app-lovedone-family-inbox --url 'https://api.lovedone.app/mcp/v1' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  app-lovedone-family-inbox:
    url: "https://api.lovedone.app/mcp/v1"
```

### Netclaw

```json
{
  "McpServers": {
    "app-lovedone-family-inbox": {
      "Transport": "http",
      "Url": "https://api.lovedone.app/mcp/v1"
    }
  }
}
```

### Vellum

```bash
assistant mcp add app-lovedone-family-inbox -t streamable-http -u 'https://api.lovedone.app/mcp/v1'
```

### Other

```json
{
  "mcpServers": {
    "app-lovedone-family-inbox": {
      "type": "http",
      "url": "https://api.lovedone.app/mcp/v1"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 82, +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.

### 2026-11-01 (score 81, +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.

### 2026-10-30 (score 80, +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.

### 2026-10-29 (score 79, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 79, +43)

- [security improvement] Transport: unverified → pass
- [security improvement] Injection markers: unverified → pass
- [security improvement] Authorization: fail → pass
- [security] First check of Judged manipulation: pass
- [security] First check of Authorization: partial
- [functional regression] MCP protocol: unverified → fail
- [functional improvement] Schema quality: unverified → 100
- [functional improvement] 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

### 2026-10-09 (score 36)

First indexed and scored.

## MCP tools (12)

### `ping` (~34 tokens)

Ping MCP server

Smoke-test tool. Returns pong plus the authenticated caller's uid, tenant, and auth method. No PHI. No side effects.

### `get_user_profile` (~31 tokens)

Get User Profile

Returns the signed-in user's LovedOne profile: uid, email, tenant type, and any linked family workspace.

### `list_loved_ones` (~39 tokens)

List Loved Ones

Lists loved ones in the caller's family workspace: id, name, and Family Inbox address. Does not return date of birth or medications.

### `list_family_members` (~45 tokens)

List family members

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.

### `list_inbox_messages` (~86 tokens)

List family inbox messages

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.

Input parameters:

- `limit` (number): 1-50, default 20.
- `lovedOneId` (string, required): Loved one id from list_loved_ones.

### `get_inbox_message` (~82 tokens)

Get one family inbox message

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.

Input parameters:

- `lovedOneId` (string, required): Loved one id the message was listed under (ownership check).
- `messageId` (string, required): Inbox message id.

### `list_care_events` (~113 tokens)

List Care Events

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.

Input parameters:

- `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.

### `invite_family_member` (~131 tokens)

Invite a family member

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.

Input parameters:

- `displayName` (string, required): Invitee's name as it should appear in the family circle.
- `email` (string, required): Invitee's email address.
- `relationship` (string, required): 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.

### `create_provider_code` (~80 tokens)

Create a provider link code

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.

Input parameters:

- `lovedOneId` (string, required): Loved one id from list_loved_ones.

### `reply_to_inbox_message` (~172 tokens)

Reply to a family inbox message

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.

Input parameters:

- `bodyText` (string, required): Plaintext reply body.
- `lovedOneId` (string, required): Loved one id the message was listed under (ownership check).
- `messageId` (string, required): 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.

### `onboard_loved_one` (~401 tokens)

Onboard a loved one

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.

Input parameters:

- `attestAuthorized` (boolean, required): 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, required): First name of the care recipient (e.g. an aging parent).
- `lovedOneLastName` (string, required): Last name of the care recipient.
- `relationship` (string, required): Caller's relationship to the loved one (e.g. daughter, son, spouse, niece).

### `get_onboarding_status` (~70 tokens)

Check LovedOne setup status

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1#diagnostics

## Score history

- 2026-11-05: 82
- 2026-11-04: 82
- 2026-11-03: 81
- 2026-11-02: 81
- 2026-11-01: 81
- 2026-10-31: 80
- 2026-10-30: 80
- 2026-10-29: 79
- 2026-10-28: 79
- 2026-10-27: 36
- 2026-10-26: 36
- 2026-10-25: 36
- 2026-10-24: 36
- 2026-10-23: 36
- 2026-10-22: 36
- 2026-10-21: 36
- 2026-10-20: 36
- 2026-10-19: 36
- 2026-10-18: 36
- 2026-10-17: 36
- 2026-10-16: 36
- 2026-10-15: 36
- 2026-10-14: 36
- 2026-10-13: 36
- 2026-10-12: 36
- 2026-10-10: 36
- 2026-10-09: 36

## Common questions

### 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.

## Links

- Remote endpoint: https://api.lovedone.app/mcp/v1
- Authorisation metadata: https://api.lovedone.app/.well-known/oauth-protected-resource/mcp/v1
- Repository: https://github.com/Terahertz-Inc/lovedone-mcp
- Website: https://inbox.lovedone.app/agents
- Changelog RSS feed: https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1.json
- HTML version of this page: https://verifymcp.io/servers/app-lovedone-family-inbox/mcp-v1