LovedOne Soft MCP
REMOTE · API.LOVEDONE.APP
LovedOne Soft: clients, visits, notes, invoices, scheduling. API key or OAuth care_circle:write.
Available components
Last scanned (2 hours ago)
Scores higher than 76% of remote servers
Reachable. Last reached 5 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 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 Usability72
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 590 tokens (~73/item across 8 items; 8 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage87
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 61% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 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.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +1
- Stability: unverified → 0.03 ▲ functional
- 29 Oct 26 +39
- 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
- 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 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/vendor/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/vendor/v1 | Verified | 200 | |
| http (plaintext) | http://api.lovedone.app/mcp/vendor/v1 | HTTPS enforced | 308 | https://api.lovedone.app/mcp/vendor/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 →
add_visit_note Add a visit note ~109
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | – |
| clientId | string | yes | Agency client id. |
| notes | string | – | Note body, max 4000 chars. |
| title | string | yes | Short title, max 120 chars. |
No output schema declared.
No examples provided.
get_agency_profile Get LovedOne Soft agency profile ~59
Returns the authenticated provider's agency: id, name, slug, plan, and the caller's role. Use this first when building a vendor dashboard.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | Required only if the user belongs to more than one agency. |
No output schema declared.
No examples provided.
get_client Get one agency client ~55
Returns one client owned by this agency, plus recent visits/notes. Rejected if the client belongs to another agency.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | – |
| clientId | string | yes | Agency loved-one id from list_clients. |
No output schema declared.
No examples provided.
list_clients List agency clients ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | Required only if the user belongs to more than one agency. |
No output schema declared.
No examples provided.
list_invoices List agency invoices ~63
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | – |
| limit | number | – | – |
No output schema declared.
No examples provided.
list_visits List visits and notes ~66
Lists LovedOne Soft visit/note events for this agency, optionally for one client. Notes may contain health information logged by staff.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | – |
| clientId | string | – | Optional. Restrict to one agency client. |
| limit | number | – | – |
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.
schedule_visit Schedule a visit ~138
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.
| Name | Type | Req | Description |
|---|---|---|---|
| agencyId | string | – | – |
| clientId | string | yes | Agency client id from list_clients. |
| notes | string | – | Optional visit notes, max 4000 chars. |
| scheduledFor | – | yes | When the visit should happen. ISO-8601 string or Unix milliseconds. Stored as scheduledAt on the visit. |
| title | string | yes | Short title, max 120 chars. |
No output schema declared.
No examples provided.
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.
remote · api.lovedone.app
claude mcp add --transport http app-lovedone-soft 'https://api.lovedone.app/mcp/vendor/v1'
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.