Remote MCP · Endpoint
LovedOne Soft MCP MCP server
No. LovedOne Soft MCP answered an MCP handshake 1 hour ago.
UpLast checked 1 hour ago
Server URL
https://api.lovedone.app/mcp/vendor/v1
The last check completed an MCP handshake.
- Registry name
- app.lovedone/soft
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-03-26
- Handshake latency
- 134 ms
- Tools exposed
- 8 tools
- Uptime, last 30 days
- 100% from 13 checks
- Described by its publisher as
- LovedOne Soft: clients, visits, notes, invoices, scheduling. API key or OAuth care_circle:write.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 1 hour ago | Handshake completed | 134 ms |
| 1 day ago | Handshake completed | 127 ms |
| 3 days ago | Credentials required | — |
| 5 days ago | Credentials required | — |
| 8 days ago | Credentials required | — |
| 10 days ago | Credentials required | — |
| 12 days ago | Credentials required | — |
| 14 days ago | Credentials required | — |
| 16 days ago | Credentials required | — |
| 18 days ago | Credentials required | — |
| 20 days ago | Credentials required | — |
| 22 days ago | Credentials required | — |
| 23 days ago | Credentials required | — |
The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 13 responding of 13.
How to read this
- ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
- ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
- ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
- ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.
Listing data comes from the official MCP registry. Glide is not affiliated with LovedOne Soft MCP and makes no claim about it beyond what these checks measured.