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

LovedOne Soft: clients, visits, notes, invoices, scheduling. API key or OAuth care_circle:write.

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

## Components

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

## Channel facts

- Endpoint: `https://api.lovedone.app/mcp/vendor/v1`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.2.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**: 72/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 590 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 87/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 61% 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.
  - We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 8 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 Soft MCP server?

LovedOne Soft MCP is a hosted endpoint at https://api.lovedone.app/mcp/vendor/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-soft 'https://api.lovedone.app/mcp/vendor/v1'
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

```yaml
mcp_servers:
  app-lovedone-soft:
    url: "https://api.lovedone.app/mcp/vendor/v1"
```

### Netclaw

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

### Vellum

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

### Other

```json
{
  "mcpServers": {
    "app-lovedone-soft": {
      "type": "http",
      "url": "https://api.lovedone.app/mcp/vendor/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-03 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-30 (score 76, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-29 (score 75, +39)

- [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] Tool coverage: unverified → 100
- [functional] First check of Schema quality: fail
- [functional] First check of Destructive annotations: pass
- [functional] First check of Schema quality: pass
- [functional] First check of Tool coverage: 61
- [functional] First check of Schema quality: good

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

First indexed and scored.

## MCP tools (8)

### `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_agency_profile` (~59 tokens)

Get LovedOne Soft agency profile

Returns the authenticated provider's agency: id, name, slug, plan, and the caller's role. Use this first when building a vendor dashboard.

Input parameters:

- `agencyId` (string): Required only if the user belongs to more than one agency.

### `list_clients` (~66 tokens)

List agency clients

Lists this LovedOne Soft agency's clients (agency-context loved ones). Includes whether each client is linked to a LovedOne family inbox. Does not return other agencies' clients or family-member emails.

Input parameters:

- `agencyId` (string): Required only if the user belongs to more than one agency.

### `get_client` (~55 tokens)

Get one agency client

Returns one client owned by this agency, plus recent visits/notes. Rejected if the client belongs to another agency.

Input parameters:

- `agencyId` (string)
- `clientId` (string, required): Agency loved-one id from list_clients.

### `list_visits` (~66 tokens)

List visits and notes

Lists LovedOne Soft visit/note events for this agency, optionally for one client. Notes may contain health information logged by staff.

Input parameters:

- `agencyId` (string)
- `clientId` (string): Optional. Restrict to one agency client.
- `limit` (number)

### `add_visit_note` (~109 tokens)

Add a visit note

Logs a note on an agency client. If the client is linked to a LovedOne family inbox, a copy is posted there so siblings see it. This is a write. Notes may be health-related — only record what the family has asked you to share.

Input parameters:

- `agencyId` (string)
- `clientId` (string, required): Agency client id.
- `notes` (string): Note body, max 4000 chars.
- `title` (string, required): Short title, max 120 chars.

### `schedule_visit` (~138 tokens)

Schedule a visit

Creates a scheduled visit for an agency client (agency_events type scheduled, status scheduled). Pass scheduledFor as an ISO-8601 datetime or Unix milliseconds. The visit appears in list_visits. This is a write. Notes may be health-related.

Input parameters:

- `agencyId` (string)
- `clientId` (string, required): Agency client id from list_clients.
- `notes` (string): Optional visit notes, max 4000 chars.
- `scheduledFor` (required): When the visit should happen. ISO-8601 string or Unix milliseconds. Stored as scheduledAt on the visit.
- `title` (string, required): Short title, max 120 chars.

### `list_invoices` (~63 tokens)

List agency invoices

Lists invoices this agency issued to families (amounts, status, assignment). LovedOne does not move money — these are ledger records. Payment handles on the invoice are contact pointers, not credentials.

Input parameters:

- `agencyId` (string)
- `limit` (number)

## Diagnostics

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

## Score history

- 2026-11-05: 78
- 2026-11-04: 78
- 2026-11-03: 78
- 2026-11-02: 77
- 2026-11-01: 77
- 2026-10-31: 76
- 2026-10-30: 76
- 2026-10-29: 75
- 2026-10-28: 36
- 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 Soft MCP server?

LovedOne Soft MCP is listed in the public MCP registry as app.lovedone/soft. LovedOne Soft: clients, visits, notes, invoices, scheduling. API key or OAuth care_circle:write. This page covers its hosted endpoint (https://api.lovedone.app/mcp/vendor/v1).

### Is the LovedOne Soft MCP server safe to use?

LovedOne Soft MCP scores 78 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 Soft MCP server expose?

LovedOne Soft MCP exposes 8 tools: ping, get_agency_profile, list_clients, get_client, list_visits, and 3 more. Their descriptions and schemas cost roughly 590 tokens of context every time the server is loaded.

### Does the LovedOne Soft MCP server require authentication?

Yes. LovedOne Soft 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 Soft MCP server still maintained?

LovedOne Soft 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/vendor/v1
- Authorisation metadata: https://api.lovedone.app/.well-known/oauth-protected-resource/mcp/vendor/v1
- Repository: https://github.com/Terahertz-Inc/lovedone-mcp
- Website: https://soft.lovedone.app/agents
- Changelog RSS feed: https://verifymcp.io/servers/app-lovedone-soft/mcp-vendor-v1.xml
- Changelog JSON feed: https://verifymcp.io/servers/app-lovedone-soft/mcp-vendor-v1.json
- HTML version of this page: https://verifymcp.io/servers/app-lovedone-soft/mcp-vendor-v1